Spring RTS Engine

Sorry for posting on an old thread, but I'd like to add to this:

Can confirm that I cannot download "spring 104.0.1-1333-gce618bd maintenance"
Currently an autohost bot is using said engine
Attempted to search for this engine manually via https://springrts.com/dl/buildbot/default/ | unable to find

This is actually something that warrants a addition to lobby protocol. Forced surrender of server option controls by majority vote in a reasonable delayed time frame.

some options:
- temporarily banning the autohost accounts until the issue is fixed
- restoring the engine versions so people can download them again

The obvies solution make a autohost callable build bot that produces engines on demand

If the problem is engines taking up too much space on the server, then it can be solved without download issues by having the server act as an LRU reverse proxy cache for some other server that sits at someone's home.

Imo opinion a sane solution to this would be (1) uberserver writing a file somewhere specifying which engines recently (~within 1 week, say) were hosted on the server and (2) the disk cleanup scripts checking this file and not deleting stuff that is in use. Should be easy to do without filling the disk. Ofc (1) is dead easy and prs welcome, I don't even know where (2) lives/runs but iirc its just a python script?

The server (now) already has in-built tools for specifying when spring versions are to be forcibly discontinued.

Fyi this is low priorty for now, there are not many hosts involved and almost no one trying to use them.

Is someone even saving engine builds?

Around 130 maintenance engines from 104.0.1-236-g23c7945 to 104.0.1-1455-g39f8fbd are stored on the Zero-K server. I copy them across manually with a web UI for testing and applying to the server. I don't know where they are stored, but they could surely be retrieved if required.

There are now 9 hosts operating on non-downloadable engines, which represents 17% of all hosts.

Hi there all

While testing Battlelist's Battlerooms, I found that trying to access "BA10.24 - Metal Server" battleroom not only fails to download the engine, but also stop my Lobby ability to download maps (Using SpringLobby 0.269).

Said that, if there is no willing on banning the unusable Battleroom's hosters, at least implementing a Warning about the inability to play on that room in the battlelist would be thankful.

Thanks for your time and effort, XenonF.

Hello everyone,

Situation is happening again: half of [ACE] autohosts are not downloadable

It so frustrating that there are 4 users playing and I can't join :/
We really need to figure something about this!

Maybe making a archive server to download old versions of spring engine?
Maybe a section on ACE website to let people download and add it manuallly in the right path and a link for it (in the "motd" ?) when connecting to the autohost...
What do you think about this solution?

Hi lasl,

Thank you for information.
[ACE]Autohosts has been updated to engine «spring_{maintenance}104.0.1-1466-g9ee29da».

Maybe in some months, it will be the same, and I'll update same way. Just let me know about it.

All the best,
Fabrice

How many gigabytes of downloads are there per year? Cloud object storage seems cheap enough for this, 100GB storage+download would be about $2 / mo

Silentwings wrote: ↑28 Dec 2019, 11:04 Imo opinion a sane solution to this would be (1) uberserver writing a file somewhere specifying which engines recently (~within 1 week, say) were hosted on the server and (2) the disk cleanup scripts checking this file and not deleting stuff that is in use. Should be easy to do without filling the disk. Ofc (1) is dead easy and prs welcome, I don't even know where (2) lives/runs but iirc its just a python script?

The server (now) already has in-built tools for specifying when spring versions are to be forcibly discontinued.

Fyi this is low priorty for now, there are not many hosts involved and almost no one trying to use them.

Could the auto-delete be stopped until an adequate solution is implemented?

I am now hosting a mirror at https://think.nsupdate.info/mirror/spri ... intenance/ that will include everything that is actually used. Namely, it will not include the 120MB debug symbol packages or linux32 versions. Some windows versions may also get trimmed once I figure out which ones are actually used.

There is no SLA. Apart from the above exclusions, I will treat missing stuff as a bug and re-upload it from (cheap and near infinite) home storage.

Google_Frog wrote: ↑21 Jan 2020, 14:25 Around 130 maintenance engines from 104.0.1-236-g23c7945 to 104.0.1-1455-g39f8fbd are stored on the Zero-K server. I copy them across manually with a web UI for testing and applying to the server. I don't know where they are stored, but they could surely be retrieved if required.

How do you access these? I'd like to backup them.

On https://springrts.com/dl/buildbot/default/maintenance/ I see only one version: 104.0.1-1560-g50390f6
Does this mean all other versions are not downloadable?

saturnV wrote: ↑06 Dec 2020, 15:32 On https://springrts.com/dl/buildbot/default/maintenance/ I see only one version: 104.0.1-1560-g50390f6
Does this mean all other versions are not downloadable?

Correct. And even that one includes only win32 because the linux and win64 buildbots aren't working.

We should really switch to Github Actions.

hosts using test versions of spring with no download:
6x BAV10.24
4x BA test-10864
6x evolutionRTS
1x journeywar
3x Metal Factions
4x Phoenix Annhilation
1x Spring 1944 test
4x Tech Annhilation
2x TA Prime
-----
8 games on 31 hosts


hosts using potentially downloadable versions:
1x imperial winter on spring 104
1x Steam Spring 1944 on spring 103
3x NOTA on spring 103
------
3 games on 5 hosts.

5 functional hosts of total 36 hosts = 14% use downloadable spring. 86% fail.

No host is using the current test version.
There is only one (1) host using current stable spring 104.0
Other games (Cursed, XTA, Kernel Panic, zeroK, BAR) have no hosts anymore.

In this thread there have been suggestions like:
- stop deleting test versions
- reupload test versions
Who has access to do such things? Why have they not replied yet?

That is strong contrast to the discussions about putting restrictions on autohosts using old engine versions. (Which in the end only affected BA9)
So many people had an opinion on that: engine developers, server operators, mod developers, players, including developers and players of games that do not use spring server (zeroK and BAR)... and now?
You can not just ban all popular hosts without offering alternatives. (If you want players.)

Now, that there is an actual problem with hosts and engine version: Silence.

Personally I think restoring the test versions is not a fix but only a bandaid.
Why are those hosts broken? The script that deletes testversions is only half the answer. The perhaps bigger problem is that those games and hosts were abandoned.

Very nice.