Spads closes battle on start

[Polar]

Hello, I am trying to setup some nota hosts in the states on an AWS server. I have run in to an issue where only one or two seconds after start the spads hosts will close their battles. Obviously this is not ideal and I would like have these working.
Also these accounts need to be tagged as bots: notAhost01NA notAhost02NA notAhost03NA notAhost04NA notAhost05NA

Thanks,
-Polar[NOTA]

[Silentwings]

I guess you'll need to include spads.log before anyone can help.

[bibim]

IIRC NOTA doesn't use current stable Spring engine version, so I guess your problem is due to the default value of SPADS' onBadSpringVersion setting, which was "closeBattle" until today. This makes SPADS auto-close the battle when it detects it is currently hosting a different engine version than the default one indicated by the lobby server.

This was the default behavior in SPADS because the multi-engine lobby protocol extension used to be experimental, but this is no longer the case so I just changed the default onBadSpringVersion value to "<null>", which means SPADS no longer auto-closes the battle in this case. However, it will only impact newly installed SPADS instances, and only the "unstable" SPADS release for now.

In short, to fix your problem I think you just need to edit your spads.conf file and set the onBadSpringVersion setting to an empty value. If it doesn't fix your problem, please follow Silentwings' advice and provide us with your spads.log content.

[Polar]

THANK YOU, that worked perfectly. now all I need is bot tags on those five accounts.
Thanks for the great help,
-Polar[NOTA]