Spring RTS Engine

You are vastly overestimating my level of engagement.

Idk, but at rough guess you haven't yet convinced anyone that it exists and probably that's related.

Done. You may need to log out/in to take effect.

It's good to see that most of the 104.0.1+xyz host have already moved to 105! I can see that some more will move too & after waiting some time for that I'll look into what's going on with the last few. With maintainance frozen & the transition branch likely to be not used by many for a while...

+1 on releasing this and finally calling time on maintainance. Re github release, I've never actually tested it but Github claims to block pushes with >100Mb content https://docs.github.com/en/free-pro-team@latest/github/managing-large-files/conditions-for-large-files. The debug symbols are 150Mb fo...

@abma, you are the last person out of active spring developers not using Discord.

To be fair, he is on Springs matrix, which is bridged. I think I might be the most "active" person with the honour of (since ~6 month ago) being on neither.

ivand wrote: Please split.

Done.

You simply won't find any better candidate to release as 105/stable.

+1 from me, and GL update gets renamed 106.

Nice work. I guess PepeAmpere means if the max unit/player/smth number limits will change - and afaik no.

Not really - the engine devs made their decision, made a small number of civil posts explaining it, and had nothing more to say then or since. Afaics for them what matters is the future of 104->105 and the need to either (1) use more modern openGL or (2) call time on the whole engine project. Unlike...

zeroK used outdated engines in the past, did I miss the big outcry Seems you didn't realize that engine developers were very unhappy with that situation, for years, and at times reduced the amount of cooperation they gave to ZK. Kudos to all those who eventually got out of that mess, using hard wor...

3) springlobby does some pop-up about no user-agreement existing on server

Joke by mando towards the Spring devs draconian overreach

Lol no, its just the default message when no user agreement exists.

Enough blathering, there is no major issue here e.g. in the last 24h, 20 accounts were created, 19 successfully verified, the remaining 1 seems to have used a fake email address. On uberserver side: I'll look at bug reports via github when they have proper logfiles etc attached, but I'm not offering...

That used to happen fairly often...

The gadget can set the unit on/off property (in fact, iirc, that's how this gadget works). An AI can see this.

I guess what may not be made "public info" by the gadget is the ratio/efficiency of the conversion.

I suggest less thought about warning notifications and more thought about bus factors - which imo are dangerously low for the engine & its supporting infra. Sadly it's unreasonable to expect abma to "find" a successor for himself & also unlikely that any single person could manage ...

- restart services and see which one broke:
- lobby server

Seems OK, systemctl restart worked. (Also, lobbyserver uptime was 112 days, longest for a long while.)