Reminder: SPADS upgrade instructions for new Spring releases are available here.

Note for Windows users:
EDIT: THIS MUST ONLY BE PERFORMED WHEN SWITCHING FROM SPRING 0.79.* TO 0.80.*
In this Spring release, unitsync.dll behaviour has changed a bit concerning the way it gets the Spring data directory, so I had to change the way SPADS uses it. SPADS no longer installs/updates/uses its own unitsync library. It uses the unitsync library installed with your main Spring installation instead. Due to this change, if you are currently upgrading a SPADS installation on Windows, you need to perform following actions:

- shutdown SPADS
- delete the unitsync.dll and updateInfo.txt files from your SPADS installation directory
- update your updater: (replace <release> by your actual realease: stable/testing/unstable/contrib)- update your SPADS packages:
Then you should be able to launch SPADS normally.

Is it possible that SPADS 0.8.1f doesn't tell the lobby the value of the "Max units" setting?

All the other mod/engine options seem fine but while SpringLobby tells me Max units is set to its default value (500) on [knb]autohost1, the script.txt I get from the host says 32000.

Also: The modopion "mo_noowner" (FFA Mode) in BA was not set at all in that script.txt. While that is fine, it's a little weird since all the other options are in there even if they are set to their default values.

edit: SPADS 0.8.2e as user Spads3 seems to report the value for Max units just fine.

I just tested with SpringLobby and TASClient. Indeed SpringLobby shows the default maxunits value (500) when joining the battle. However TASClient shows the correct maxunits value (32000).
And when TASClient debug mode is enabled, one can see the maxunit tag is correctly sent by the server: Maybe SpringLobby has an internal high limit for this setting

Indeed this is weird (actually the "mo_noowner" tag isn't even sent in the lobby). Maybe this is due to a specific SPADS configuration ? (other SPADS autohosts don't lack this setting in startscript).

edit: yeah, checked with andre, this was due to an inconsistent modoption configuration.

Been having a chat with BrainDamage. It's actually wrong behavior in SPADS and TASClient since EngineOptions.lua clearly states that the max value for Max units is 10000.

EngineOptions.lua is out of date, the engine's global unit limit is 32000 now (so for a two-player game without Gaia, the real engine-enforced team limit would actually be 16000, not 10000). Lobbies should interpret the EO value as a recommendation, rather than a strict upper bound.

Why is that? Max value is a max value. If the engine supports more now, just update the EngineOptions.lua definition.

SPADS(stable/Win32) is generating a lot of the following error-messages lately:



...but seems to run stable anyway(since the last change to dedicated 0.80.2). Should I worry about it or can I ignore this

These errors mean spring-dedicated sent PLAYER_DEFEATED messages to SPADS for players who didn't even join the game.
I've got these errors too since quite a long time, and I think it is due to a bug in spring-dedicated that makes it send such messages for spectators who didn't connect when a player dies.
You can safely ignore them.

Hi,

Recently SPADS refused to start a 16+16/32-Game because the spring-engine does only support 31 clients... As far as I know the spring-engine supports now 250 clients? :D

Maybe you should change this ^^

greetz
Ataman

Yep indeed. Will be fixed in next update.

did the update correct, tried to start and it gives me this:

C:\spadsInstaller>perl spads.pl C:\spadsInstaller\etc\spads.conf
ERROR - [SPADS] [SimpleLog] No log file configured, redirecting to standard o
utput
ERROR - [SPADS] Incomplete SPADS configuration (missing global parameters: mi
nLevelForIpAddr,kickBanDuration,userDataRetention)
ERROR - [SPADS] Unable to load main configuration parameters
CRITICAL - [SPADS] Unable to load SPADS configuration at startup

Some SPADS updates require manual modifications in configuration files. When this happens, SPADS does NOT auto-update because it wouldn't be able to restart without these modifications. Instead, it logs an alert and continues running normally.

It seems you launched the manual update but you didn't perform the manual modifications in the configuration files for the new SPADS version.

How did you update SPADS ? Which command did you run and where did you find it ? Normally SPADS should have provided you with the link to the update help in the same place where it warned you about the manual update availability (var/log/spads.log).

Maybe you followed the procedure described here to update SPADS, whereas this procedure was just a specific procedure to upgrade from Spring 0.79.* to 0.80.* ? In this case, it just forced the manual update and you can follow the last section of the update help to fix your config files.

yeah i updated like this..

i just did a reinstall and everything works again :)

since i do not have anything configured in spads it is easier to just reinstall instead of trying to figure out what went wrong with the update xD

reinstall to new folder 3 times, that worked for me

Are the servers with >16 player limits running Spads? We had some issues where it was forcing players into a coop because it wouldn't give ids larger than 16...is this a lobby issue or an engine issue or a spads issue?

Lobbyserver issue. You could make Spads assign unique numbers to each player, but there is no way to show these ids in the lobby (you are limited their to 16).

Springlobby has a hack implemented that exactly does that, but its confusing.

can you make !status command send current running game elapsed time in the battle window? would be much more convenient than sending useless information about players etc in PM window every time...

how to disable !lock command from everyone else except me?

how to manually change each player team number?

how i can add autokick for people who suggest DSD as map?