Maniaplanet Forum

Here is the first Canyon compatible version of ServerMania dedicated server controller

Last Update : 26/10/11 : ServerMania 1.00 [ManiaPlanet]
Here is the main changes :

• Updated : Canyon compatibility.
• Updated : Cache for challenge infos is now saved at application exit and reloaded at application start.

This version is mainly for Canyon compatibility and supports only Canyon.
So do not install it over your current installation.

Very nice, Cyrlaur - thank you!

Thank you Cyrlaur - very nice! I like having the ability to sort/ add/ remove/ skip maps; manage matchsettings 'on the fly'; chat without joining server/s; and check network stats - very clever!

I have a couple of issues/ questions with the TM2 version when connected to my remote servers:

1. Although the 'Stop' button works well, the moment the server shuts down I get a disconnect error message (which I understand of course) but then the 'Start' button doesn't work. Are these buttons/ functions only designed to work on a local (pc) server or am I ale to set them to control a remote server?

2. Assuming the above setting allows for remote start-up, would it also be possible to include a 'Restart' button in a later release?

Many thanks

"Stop" button puts the server in "Waiting" state but you should not loose connection with the server.
When server is stopped you should be able to restart it.

"Quit" button will tell the server to really shutdown (server process will end on remote computer) and controller should close and the launcher appears. At this state you won't be able to restart the server remotely.

Thanks Cyrlaur. My remote servers are on a dedicated linux (Centos5) server which I rent and control fully. The xmlrpc ports I use for ManiaPlanet servers are:
5000, 5001, and 5075 - ServerMania 1.00 connects to all of these ok and remains connected as long as I need it.

I also found that I can connect to and control SOME of my TM2 servers with ServerMania 1.00, which use these ports:
5020, 5070 and 5570!

I see the same issues on all servers when connected with ServerMania:
** The 'Quit' button shuts server down & the 'lost connection' message pops up - need to restart manually;
** The 'Start' & 'Quit' buttons are dimmed (not available);

* I can change server settings(options), game settings, shuffle (randomize) tracks/ maps, chat, control players etc;
* New tracks/ maps can be added from local collection;
* I can restart or skip maps and load/ save matchsettings; and
* When using the 'Exit' button, the main page closes and returns to the launcher (which is normal).

All other RPC functions work on this remote server, e.g. ManiaRecords to web page, tmos viewer, xaseco-stats and RemoteCP, so that doesn't seem to be the issue. Do you have any suggestions?

Cheers

I may fix (not sure) the disconnect pop-up, but at the end it's normal that you lose connection with the server and have to restart manually with "Quit" button.
If you don't want that just use "Stop" button.

No big deal but both 'Stop' and 'Quit' buttons do the same thing for me - shuts server down & disconnects. Maybe just a bug with linux but doesn't bother me, as the other functions in your programme are VERY useful.

Cheers

nighthawk4571 wrote:No big deal but both 'Stop' and 'Quit' buttons do the same thing for me - shuts server down & disconnects. Maybe just a bug with linux but doesn't bother me, as the other functions in your programme are VERY useful.

I guess that stop and quit are related to the dedicated methods :

QuitGame
boolean QuitGame()
Quit the application.

StopServer
boolean StopServer()
Stop the server.

It seems/feels the same for the players on the server, but there is a huge difference :
- the first will close dedicated program.
- the second make it stop its game service, but without closing the program (so a script can still communicate with it and start again the game service).

If you use servermania remotely (ie your dediated is hosted somewhere else), with stop you will be able to start it again from servermania, with quit you will have to connect on the remote host to start again the dedicated program.