@wc_sumpton & @beelee , cut it out with the insults. To fully respond would require quite an essay, which I'm not going to do. Suffice it to say, a number of things you said are wrong, I don't think maliciously so, just a misunderstanding of unrelated things feeling related.

Why was the game not showing the proper amount of PUs for the AI player? No one can answer this question. So instead of trying to figure out the real problem, the message caused by this problem is remove.

I'll respond to this. The reason seems to be because the AI-only trigger that grants PUs to the AI player is bugged and is not working. Why that is so, is not known. If it were, it would likely be fixed. I spent 4 hours on a Saturday looking at that issue instead of doing anything else in my life. It's heartening to now be told that clearly IDGF.

there were many errors, but all these errors could be traced back to the failure of the xml not loading correctly.

@wc_sumpton please clearly communicate your evidence for this. I suspect the XML was loaded correctly, but the conditions for firing the bugged trigger were not evaluated correctly. I believe it would be much more helpful to present why you think that was the case, in a clear and simple manner, compared to spending effort venting.

@wc_sumpton

Yeah, the 2.7 version has a lot of visual issues.

I just opened the 2.5 version, it's great.

On the roadmap is to change how TripleA represents the state of the game to be a plain text file instead of a binary encoding. Once that is done, it'll be a lot easier to interoperate different TripleA game clients (ie: a mobile version that interoperates with a desktop version).

The level of effort to reach that goal is pretty high though. It's been an uphill battle to tackle our current goals... I do agree it would be pretty sweet to be able to play a turn of TripleA during coffee breaks.