bugs in beta 2.5.1 dedi server

[DemosDemon]

I run Soldat Server 2.5.1 on my dedicated server, and at times it keeps crashing.

Logs give me an error:
Server Encountered an error:
Access violation at address 080957C8, accessing address 00000000
Server Shutdown
Shutting server...
Exception EAccessViolation in module soldatserver at 08059035.
Access violation at address 0807F248, accessing address 00000000.

While playing the game before a crash, the server starts to show noteable bugs, Infinante Health, Infinante Ammo, and Infinante Jets.

This could be because of a cheat or hack, but if it is, it's also pretty "lethal" to the server itself.

[gulak]

i have the same problem 

my machine:
Soldat Server 2.5.1
Debian 3.1
AMD Opteron 148
port 23073 opened

last used dedicated v2.3.5 runs fine

:/server/soldat$ ./soldatserver 23073 12 soldat.ini mapslist.txt

             -= Soldat Dedicated Server 1.3.1 - BETA 2.5.1 =-

----------------------------------------------------------------
       Caution! This software is still in BETA phase.
         Soldat Dedicated Server initializing...
----------------------------------------------------------------

   Additional parameters:
   ./soldatserver port maxplayers config maplist
   Example: ./soldatserver 23073 16 soldat.ini mapslist.txt


Server Encountered an error:
'' is not a valid integer value
Server Shutdown
Exception EAccessViolation in module soldatserver at 08059035.
Access violation at address 080B9827, accessing address 00000000.
Speicherzugriffsfehler

[EnEsCe]

gulak, your problem is you have fucked up your Soldat.ini/server.ini files and configured them incorrectly.

DemosDemon: When does this error occur? Right when you start the server, after 1 minute, unless you can tell me how to cause this bug to appear I will not be able to replicate+fix it.

[chrisgbk]

gulak, your problem is you have ****ed up your Soldat.ini/server.ini files and configured them incorrectly.

DemosDemon: When does this error occur? Right when you start the server, after 1 minute, unless you can tell me how to cause this bug to appear I will not be able to replicate+fix it.

That looks like that one bug that I helped track down that should be fixed in 2.5.2, but you never know.