If you are reading this. Is it most likely because you are one of our many awesome mission makers - I would like to thank you for all the hard work you are doing
Now.... I sadly don't have an accurate count on how many missions we are rejecting because of errors that could have been easily fixed if the mission maker had just tested his mission. but i would guesstimate that its more than 50%...
For the love of all that is holy, When you are creating missions, ADD THIS TO YOUR STARTUP PARAMETERS!
There is NO way that you can miss a script error if you have this on. (well, you have to be pretty creative )
Check the RPT file.
For my system it located in: C:\Users\Perfk\AppData\Local\Arma 3 - its the files that end with .rpt
I suggest that you move all the files that end with .RPT into a backup folder. and then test your mission. The file will be filled with a lot of information.
We have a lot of mods in our modpack at the moment, and some of them are sadly throwing random errors. This makes it a little harder to test your mission. But in general, search for ERROR and see if whats there make any sense. if not, ask someone
You are checking a box that says that your mission does not contain any scripterrors when you upload the mission, Now you know where to find them
This is just a rant from me (just had to reject 3 missions on the new island that i would have loved to play, but they would have broke on first playthough. so i had to reject them)
What is your best tip when testing a mission? write it here
Edited by Perfk, 2016-06-14 @ 22:38.