the server runs in a CMD box, you can just click the little x up in the right top corner to close it, if for some reason you cant, then push ( Ctrl Alt Delete ) keys all at once and click Task Manager look for the CMD running application right click for options and click ( END TASK ) this will force your server to close
No this doesnt work. I close it either way and I can still easily connect to the server.
what sort of setup do you have, is your server with steam or did you download the server files from this website and use them ? also is the server running on your own computer, please give us more info to work with.
Are you re starting the server when you restart your PC before you load the game and goto and connect to it oO
Also setup your local ip to always use the same local ip for your computer as this can cause the address to change every time you start your PC
its highly unlikely the server dies because you turn your pc off more like some settings have changed since last time
when running a server its almost always best to have a dedicated computer, one that's on 24/7 days a week with all static ip address's
this way friends can connect anytime and its less likely settings will change.
you could look to see if your virus protection is blocking it
do you have an error report or can you show us the logs,
In the server folder (as you run it yourself, you should be able to access it easily) there are:
A) a screenlog.0 file (also text file), which also contains logging information
B) a Logs folder with logs(text files), look within the latest for error messages.
C) there might be files with rather funny names (sorry they are different from platform to platform, but they contain "err" in the name) with specific error reporting.
And, above all, how do you start the server? Do not start it by simply double clicking the server.jar or passing directly to Java; use the win_startscript.bat file instead.
1) Open a terminal (or console or command prompt, however it is called under Windows) in the folder where you placed the dedicated server and type: win_startscript.bat
Hoping this helps...
If you're running the server on your local machine, make sure that port port forwarding is still active. As @yahgiggle mentioned, depending on your ISP, you may get a new IP after a given amount of time (usually 24 hours), so if your forwarded ports only take a specific IP into account, it may no longer be valid. Here you can find out if your ports are still forwarded: http://www.yougetsignal.com/tools/open-ports/
Also make sure that you always run the server by executing the win_startscript.bat, never execute the server.jar file directly (unless you run it from a command prompt).
About the saving behaviour: The world will be saved every 10 seconds, and it will also be saved when the server shuts down gracefully.
If you're running the server on your local machine, make sure that port port forwarding is still active. As @yahgiggle mentioned, depending on your ISP, you may get a new IP after a given amount of time (usually 24 hours), so if your forwarded ports only take a specific IP into account, it may no longer be valid. Here you can find out if your ports are still forwarded: http://www.yougetsignal.com/tools/open-ports/
Also make sure that you always run the server by executing the win_startscript.bat, never execute the server.jar file directly (unless you run it from a command prompt).
About the saving behaviour: The world will be saved every 10 seconds, and it will also be saved when the server shuts down gracefully.
Red,
I know nothing about Windows the Linux script appears much more advanced and incorporates start and stop modes. The windows script just seems like a wrapper for running the jar. Nothing fancy. Windows has start/stop/restart modes for services just as Linux does. Would it be possible to have a new Windows script added that can be used as a Windows service?
@zfoxfire: The win_startscript just grabs the memory parameter from the server.properties file and executes the server.jar with this argument. But the main reason to run the bat instead of the server.jar directly is to have a console available (many people just double click on the server.jar, which causes the server to run in the background - only way to close it would be to kill the process in the task manager).
We want to keep the start scripts as basic as possible, it's really just to cover the basic behaviour. I'm sure some people won't be happy if the server sets up new services in Windows^^
Don’t have an account yet? Create a new account now and be part of our community!
