mordoten wrote:
So, while you guys are arguing on the internet I've done 2 battle reports so far testing out the new changes.
Mordoten, seriously, you need to quit being dismissive of criticism and address some issues with your system before it is even worth participating in this.
You have approximately 90 proposed changes spanning almost every list in NetEA. Considering some changes touch multiple lists and need testing in each list, I think conservatively it's more like 150 separate changes. That is an extremely large number.
To be even remotely useful, a single battle report can probably only incorporate a few of those changes at a time in a test list against an unchanged opponent as a control. If you want any kind of useful data, you probably need to test each change 3-5 or so times (and even that is worthless statistically).
So if battle reports are the magic solution, how do you propose organizing, tracking, and cataloging the hundreds and hundreds of battle reports you now require to move forward?
What you brush off as "sniping" is legitimate concern that your process is utter chaos and hasn't solved anything. What you call "arguing on the internet" would be reasonable debate if you would bother to engage.
With some actual public discussion on these proposals, we could prioritize a smaller number of changes per army list as worth considering. From those we could probably work through which ones can be accepted with zero/minimal play testing and which ones require rigorous tests.
You have to face the fact that you can't suddenly dump 90+ changes on us with no discussion and then flog us to churn out battle reports mindlessly. You need to organize this effort, structure it, and provide some way for us to triage what of this mess is even worth trying on the table.