Spring RTS Engine

If you have local versions of Lock Camera, Ally Cursors, Initial Queue or AdvPlayerList in your local widget folder(s) then you should remove them before using BA 7.81.

These are all maintained and shipped within BA. They have been recently updated and the updated versions are in 7.79+. If you store old local versions then Spring will load your old local version, instead of the latest version, and you will have some compatibility problems.

The reason is that BA 7.79+ contains gadgetry that will notice when a player is afk (e.g. at gamestart or for >90 secs), and mark them as takeable. This should hopefully reduce pauses and stops, but it looks for input from Initial Queue and it uses AdvPlayerList to give take reminders. Also Lock Camera and Ally Cursors became gadgets; if you keep out-dated local widget versions they will probably no longer work at all.

In general, if you keep out-dated or modified local copies of widgets that BA maintains then its at your own risk and we can't guess if they'll work for you when we update. The complete list & current versions of widgets that BA maintains is here: http://imolarpg.dyndns.org/trac/balates ... ui/widgets. Your infolog.txt can also tell you if you've downloaded duplicates.

why not make a BA_advplayer list version to avoid conflicts? and then look for the advplayerlist and autoclose it

Because we'd end up with too many names! People would still tinker with widgets & sometimes publish their own versions without renaming - I don't want to stop that, but we can't help to maintain them.

What about maintaining a list in each BA release with the versions of the contained widgets, and alarm a player if they load a widget with a different version?
(use svn-rev-tag rto auto-gen the widget-version into the release and the list?)

What kind of 'alarm' would you suggest? There is already an infolog message.

Something more prominent than in the infolog (which is totally cluttered by players joining the match). Maybe like the big letters "starting in 3,2,1" or like the ready-button?

I don't want to do anything that could discourage people learning to develop widgets; potential future devs are valuable.

People who make/use non-BA widgets should be the ones who care about and maintain their own stuff.