dude11235: you managed to miss the first reason for a new Trem release: fixing bugs!
... race conditions when using some in-game menu
... forgetting settings once in a while
... no responsiveness during map loading
... mouse disappears when game can't find the required map
And I guess I have already got used to the many other major and minor annoyances :-/
how exactly are there race conditions in an engine that refuses to use more than 1 thread?
The races are between client and server... Like this: go to armory, press q, quickly buy some gear that you already have. If you buy quick enough, you get the "you can't buy that stuff twice" message _after_ buying something else. This message can't be clicked away then and remains in the foreground till you die (in the game of course :-D ) You can still use the "buy" dialog in the background, though.
Looks like the server sends a reply after buying, and if you click faster than the server ping (ie. 50 to 100 ms) the race condition comes up. Happens fairly often to me in a heated game or slow server. And there are other similar client-server races in Trem.
(Btw. I think it's a WTF for itself to display this "you can't buy this item twice" message at all... If really necessary, play some "negative sounding" sound, but don't annoy the user with a message that he has to confirm).