I am extremely happy to be working on this project as a tester. However, I do sometimes wish that we had a bit more coordination with testing duties. There's been more than one instance where I've had a map receive major updates as I'm in the process of testing it, effectively nullifying my work, since I'm now testing an out-of-date version.
I sometimes wonder if it would be better if each tester were assigned a certain amount of map slots that they were dedicated to, like one tester would focus exclusively on MAP01-05, and then another would only test MAP06-10, and so on. Or perhaps they would be rotated: tester #1 would test MAP01-05, then alterations would be made based on their suggestions, and the updated MAP01-05 would then go to tester #2. Meanwhile, tester #1 would receive a new batch of maps to work on that tester #3 had just finished critiquing. Just seems like it'd be more efficient that way, though I admit that it runs the risk of slowing the process down if one of the testers is taking too long, or if one of the mappers can't apply the alterations in a timely fashion.
Heck, maybe even testing deadlines would help: the testers have however many days to complete testing before work begins on the next update.
Just seems like there could be a better way to do this, but maybe this is just how testing works with all MegaWADs.
EDIT: It's no big deal, though. So I have to retest a level or two. So what? It's my job.
All you testers have simply done an amazing job. This is partly my fault, and partly the fault of the testing system where we have all the mappers send their maps individually to all the testers. When I get results from a tester, I go and make those changes and then send the updated maps out to the testers again, figuring it might save them some time if they have an improved version of the map to work with if the haven't already tested it.
The limitation to doing it like this is, of course, sending them an improved version would undermine their testing if they have already tested an earlier version, which is what has obviously happened in this case.
Possibly we need to have one person in charge of coordinating all the testing, rather than have maps going everywhere from every mapper to every tester. I'll see what whoo thinks of this idea.
Dear god, Map 29, Brown Map, took me all goddamn day to complete, and I kind of want to slap Kyka for some of the things I had to suffer through. Some of the fights are completely unfair and need a bit of tuning, I dont enjoy being trapped in one fight for an hour or more :/
Which fight was that, btw?
The map itself looks really good, it really fits its map slot now. I would like a bit of "fusion" though, the name of the level was decided to be Veridian Twilight...but it doesnt feel right anymore. I'll have to IDDQD + IDCLIP the original green version for a full comparison.
...Because 'brown twilight' doesn't have a very good ring to it. lolllololllol
If anyone is feeling creative, see what names you guys can come up with. I am curious. Something relating to 'brown' and 'final'.
Total killcount btw: 1153. I swear 1/5th of those are Revenants >_>
Actually there are 82 revenants (on UV out of a total of 994,) so about 8%. Though given their high damage, and the fact that said damage can follow you around like some weird pet, it probably does seem that there are revenants around every corner.
As usual, a screenshot laden report will be sent later, including stuff from the new version of Map 2
I look forward to your feedback, my man.
And now, for no good reason, a mass of screenies from various levels.
Last edited by KiiiYiiiKiiiA on 02-07-13 at 14:30