Skilled Illusionist
- Joined
- Feb 3, 2007
- Messages
- 321
- Reaction score
- 67
Hi, I've decided to release my ServerManager along with source that I made for the official servers during working with and hosting flyff.
Brief information of what it is and what it does
In a nutshell, it controls and restarts servers in appropriate order in case they have crashed.
It has a remote command interface that was lately added due to testing purposes on a local subnet (as such, it does NOT provide security for being openly available on a server, it uses basic username/password authentication and unencrypted packets).
It also provides an inter-process communication system with each server, which allows ServerManager to have full control of them. You can for example enable or disable servers and channels on AccountServer from within ServerManager live as it runs. It also lets you add custom commands in each flyff server and then execute them from ServerManager (or Remote client for server manager with a few modifications).
Each flyff server has to connect to ServerManager and authenticate themself, they do this on startup with custom arguments in the startup parameters.
All servers but WorldServer are also hidden on startup to keep desktop clean. The reason why WorldServer is not hidden is because I had made it a console application instead of a actual form. You can show and hide each individual server as they run from ServerManager.
ServerManager will show status, memory usage with peak and run time.
Known issues or bugs
There are only two issues that I know of at the moment.
Note
I have stopped developing on this and I am not going to fix bugs or improve on it, you have the source and the ability to work on it.
How you set up this application in terms of using the compiled binary should be pretty straightforward, you should be able to just open configuration file and figure out its settings.
Why am I releasing this?
Well, on reason is that I'm not developing for flyff anymore.
Another reason is that I like to see more custom programs being made, more open source than closed down binaries.
Technical notes
The source of ServerManager and RemoteManager are made using C#.
There is an implementation that has to go into each server in order for them to work and communicate with ServerManager, I will only provide a short guide on how to implement that.
Questions
If you have any related questions, post a reply as I will perodically read when I have time and try my best to answer.
Downloads
The download contains source code for ServerManager, RemoteManager and the implementation part for each flyff server.
The download also contains the guide on how to implement it into each individual server as it would be too long to type it here.
Read before downloading
A last minute fix has been made that will prevent ServerManager from crashing upon startup while RemoteManagement is disabled.
It was occasionally still polling the remote management code, which was polling the socket (which is null).
Open up RemoteManagement.cs and find function Update().
At the very beginning add the following.
Mirrors
Happy coding!
Brief information of what it is and what it does
In a nutshell, it controls and restarts servers in appropriate order in case they have crashed.
It has a remote command interface that was lately added due to testing purposes on a local subnet (as such, it does NOT provide security for being openly available on a server, it uses basic username/password authentication and unencrypted packets).
It also provides an inter-process communication system with each server, which allows ServerManager to have full control of them. You can for example enable or disable servers and channels on AccountServer from within ServerManager live as it runs. It also lets you add custom commands in each flyff server and then execute them from ServerManager (or Remote client for server manager with a few modifications).
Each flyff server has to connect to ServerManager and authenticate themself, they do this on startup with custom arguments in the startup parameters.
All servers but WorldServer are also hidden on startup to keep desktop clean. The reason why WorldServer is not hidden is because I had made it a console application instead of a actual form. You can show and hide each individual server as they run from ServerManager.
ServerManager will show status, memory usage with peak and run time.
Known issues or bugs
There are only two issues that I know of at the moment.
- The memory usage graph is not entirely correct. I have not looked into it after creating it.
- The server selecting listbox is occasionally flickering, especially when you move mouse over them. This can be fixed by correctly utilizing double buffered rendering.
Note
I have stopped developing on this and I am not going to fix bugs or improve on it, you have the source and the ability to work on it.
How you set up this application in terms of using the compiled binary should be pretty straightforward, you should be able to just open configuration file and figure out its settings.
Why am I releasing this?
Well, on reason is that I'm not developing for flyff anymore.
Another reason is that I like to see more custom programs being made, more open source than closed down binaries.
Technical notes
The source of ServerManager and RemoteManager are made using C#.
There is an implementation that has to go into each server in order for them to work and communicate with ServerManager, I will only provide a short guide on how to implement that.
Questions
If you have any related questions, post a reply as I will perodically read when I have time and try my best to answer.
Downloads
The download contains source code for ServerManager, RemoteManager and the implementation part for each flyff server.
The download also contains the guide on how to implement it into each individual server as it would be too long to type it here.
Read before downloading
A last minute fix has been made that will prevent ServerManager from crashing upon startup while RemoteManagement is disabled.
It was occasionally still polling the remote management code, which was polling the socket (which is null).
Open up RemoteManagement.cs and find function Update().
At the very beginning add the following.
Code:
if (!Configuration.EnableRemoteManagement)
return;Mirrors
Happy coding!
Last edited by a moderator:
