From: Neuching, Bavaria, Germany
I'm with you.
What I am trying to say is that the difference between "facts", "assumptions", "opinions" and "guesses" should be observed, to avoid confusing people looking for advice and help.
Then again, I'm the first one to agree that AE is very hard to handle when it comes to testing. So many variables, so many rules (a lot not documented for a variety of reasons).
What it all comes down to is probably some matter of style.
Writing "CAP is BROKEN! Fix it!" is not what devs need, and does not help people looking for advice (I think we all can agree to this).
What I suggest is - at least in the Technical Forum (which is sort of mail box for the devs) to make sure a post about something "weird" has
1. all technical info (version, setup etc),
2. concise and precise description of case in question - possibly with an attached screenshot
3. most often an attached save (or better yet, save before and after event).
And finally - if needed - a sort of explonation why the poster thinks the case stated is "out of order".
With that level of info we all can make life for devs so much easier. Giving us players in return a chance to see an improved version sooner or later.
PS: JeffK, Sardaukar - my statement above has no relation to your valuable and appreciated posts. It is intended to be a sort of "call to the community".
Data base changes by Andy Mac October 16, 2012
Scen #1 Allied vs AI Level Hard Daily Turns
Art Mods by TomLabel and Reg
Topo Map by chemkid
WitW / Torch
1.01.37 - 1.01.44 beta