Kurhhan on 15/2/2016 at 16:18
So you will not show your beta-tester final release version ? That`s bad.
Iceblade on 15/2/2016 at 16:34
First, it is standard procedure for all contests.
It's the job of the beta-testers to provide comments to the author so the mission is as clean and polished as can be. I'm just giving it a final runthrough to make sure the author didn't include a last minute change to the final package that broke something or resulted in a missing texture. Am I'm expecting any issues? No. That still doesn't mean there won't be any, and this is provided to the contestants as a curtsey to avoid embarrassments. Also a weekend is customary and I need to play through the whole mission. The weekend is generally also used to check for disqualifying features, but that isn't really an issue for this contest.
Unna Oertdottir on 15/2/2016 at 16:38
Quote Posted by Kurhhan
So you will not show your beta-tester final release version ? That`s bad.
It's already tested and fine. You didn't get the point of that discussion.
Kurhhan on 15/2/2016 at 16:52
Good, that you get the point from questions not directed to you.
Quote Posted by Iceblade
First, it is standard procedure for all contests.
That is not true.
Avoid our embarrassments ? I think you will be more ashamed if you disqualify mission in "my first mission contest" because it's too big.
Iceblade on 15/2/2016 at 17:52
The primary purpose of the contest is the encourage new authors to get their first missions out the door, which is why the size limits were put in the place. There is no possessiveness associated with the contest either.
Unna Oertdottir on 15/2/2016 at 18:07
Quote Posted by Kurhhan
That is not true.
Of course, it's a standard procedure for contests
You could look at older contest threads.
(
http://www.ttlg.com/forums/showthread.php?t=79826&p=979648&viewfull=1#post979648)
Quote:
Remember, there is a week interim wherein I'll be inspecting/testing the missions and getting everything set up for the big public release
Wow, 7 days, not just a weekend :laff:
Kurhhan on 15/2/2016 at 19:05
You have "OldDark" thinking. There is no such thing like "standard procedure for contests" in this matter. Iceblade just want to pose for someone who is not. Btw, I do not write to you, why you answer for someone all the time ?
Summarizing, this is a wasting time, checking something already done by me and my great betatesters (also the publisher of many missions), especially that you are not dromed/betatester master Iceblade. I can't find any of your mission or your activity at the shalebridgecradle. That's all I want to write on this topic.
Tannar on 15/2/2016 at 19:18
Okay, let's all calm down a little. A few points:
First, Iceblade, as the contest organizer, is correct in making sure missions are functional and meet requirements, regardless of what has or hasn't been done in the past. I don't believe it is necessary to play through the entire mission to do so, but that's his choice.
Second, New Dark vs. Old Dark has nothing whatsoever to do with whether or not a mission needs testing, or the likelihood that a problem might be overlooked. All missions need testing, and even with thorough testing by experienced testers, some things can get missed.
And lastly, it's never a good idea to release a mission your testers haven't seen. The general rule of thumb in testing is that when you finally have your mission all complete and ready for release, you send it to your testers first so they can check it. I suspect some of you new authors may think this unnecessary, but I speak from vast experience. I can remember numerous occasions when an author didn't do this, and problems appeared which would have been caught if the release version had been tested. I'm sure the more experienced authors here will verify this.
