Sup guys,
not sure what everyone is using to start their server, but i've written an launcher to manage that problem the smooth way (and get rid of those annoying windows).
The launcher is controlled with 4 hotkeys (keycombinations are: CTRL + SHIFT + <Key>):
You can manage the components which should be launched with an simple .txt file where the executable names / paths (relative or absolute) are given.
If there is no services.txt file in the launchers directory, the following default paths are used (executable in the launchers directory):
The components are launched in the same order as they are placed in the .txt file, and stopped in the reverse order.
Additionally the following parameters can be passed to the launcher at startup:
If the launcher is closed while any component is running, all the windows are shown again.
Virustotal:
Source, the executable file and an example for the services.txt are in the attachments.
appologiez for mah bad english! tt1:
not sure what everyone is using to start their server, but i've written an launcher to manage that problem the smooth way (and get rid of those annoying windows).
The launcher is controlled with 4 hotkeys (keycombinations are: CTRL + SHIFT + <Key>):
Code:
[R] -> start alle server components
[K] -> stops all server components
[D] -> displays all windows of each component
[H] -> hides all windows of each component
You can manage the components which should be launched with an simple .txt file where the executable names / paths (relative or absolute) are given.
If there is no services.txt file in the launchers directory, the following default paths are used (executable in the launchers directory):
Code:
AccountServer.exe
DatabaseServer.exe
CoreServer.exe
Certifier.exe
LoginServer.exe
CacheServer.exe
WorldServer.exe
The components are launched in the same order as they are placed in the .txt file, and stopped in the reverse order.
Additionally the following parameters can be passed to the launcher at startup:
Code:
-log (write log-entries to the console about miscellaneous thing going on at launchers runtime)
-logmax:XXX (limits the log-entries in console to XXX lines)
-nohide (disables the auto-hide function at startup)
-interval:XXX (delay between the startup of each component)
If the launcher is closed while any component is running, all the windows are shown again.
Virustotal:
You must be registered to see links
Source, the executable file and an example for the services.txt are in the attachments.
appologiez for mah bad english! tt1:
Attachments
You must be registered for see attachments list