I know there's more important stuff to work on atm so i don't expect this to be fixed "right away".
But i also know that Devolpers (I'm one myself..) need to know about issues to track them down and fix them.
Currently it is (seemingly) not possible to start the dedicated linux server with systemd.
I'm running Ubuntu 16.04.3 LTS
It almost takes off but then hangs at
BattalionServer: Setting breakpad minidump AppID = ....
Funny enough it actually starts running once you call systemctl stop <battalion-service-name>:
BattalionServer: Setting breakpad minidump AppID = .... #this is where it enters "stale" state after starting it with systemd
systemd: Stopping Battalion 1944 Server...
BattalionServer: 4.17.2-0+++UE4+Release-4.17 513 0
BattalionServer: Disabling core dumps.
BattalionServer: eac_server.so [x64] :: OnLoad()
BattalionServer: CWorkThreadPool::~CWorkThreadPool: work processing queue not empty: 1 items discarded.
systemd: battalion-server.service: Main process exited, code=exited, status=143/n/a
Here's the systemd service I used in my experiments (i have removed some sensible data) on Ubuntu
Description=Battalion 1944 Server
ExecStart=/opt/Battalion/Battalion/Binaries/Linux/BattalionServer /Game/Maps/Final_Maps/Derailed?Game=/Script/ShooterGame.BombGameMode?listen -broadcastip="<ip>" -PORT=<server-port> -QueryPort=<query-port> -log -defgameini="../../../DefaultGame.ini"
gdb and/or strace haven't given much of a hint about what's wrong, which I somewhat expected due to missing debug symbols and possibly some built-in some debugging/hack protection stuff.
All of this is no major issue, one can start the server fine using screen and handle it from there.
If you need any further information I'm glad to help you out.