Whereas it doesn't take me 15 minutes to restart the server and i get that this is alpha with probably no optimization, this is still quite ridiculous:

That is during startup only however.
Average usage once it's started is like maybe 2-5% of a single core. The ram does suffer, but that's nothing unusual for these games:

Bandwith-wise it uses nect to nothing. This makes me very happy.
I've got an avarage of 4KB/s per active connection. Very VERY nice. =D

I will keep monitoring these stats and tomorow i will start testing with multiple cores and see how that affects startup, etc.
I'll keep you posted.

"btw i move this to Ideas and feedback since its not a bug report =)"

Yes please do. I clicked new post under bug reports and wasn't sure it would post there, or my current directory. Hint: It's not the current directory :P

Another good reason for a commandline tool! I do run my servers as a service, and make my own tools and interfaces based on the commandline.
I'll look into FireDeamon, looks usefull.

If a CLI is released i'm making a powershell module and probably some type of remote management WebGUI.

From a server admin viewpoint, a commandline option for ECO would be nice.
Commandline interfaces give some very nice advantages over GUI
When running Servers I like being able to run them on a Core Mode Server, because:

• It is less overhead
• Allows for scripting
• Can be run on a core Server/Server without GUI (Much more stable and less resources used, OS-Wise)

Is this a planned feature?

Also the minor following features would be nice:

• The ability to bind the listeners to specific IP's/ports
• Make ServerWatcher.exe and Server.exe background processes and optionally show them
• Exporting/Importing settings from a .txt file or something like that

(I'm running the server exe on Windows Server 2012 R2, no issues so far! ~2H uptime)