Open LordWartog opened 6 years ago
Can't tell much without logs, but if I were to guess blind, you run that from invalid location like onedrive or inside of archive.
Can't tell much without logs, but if I were to guess blind, you run that from invalid location like onedrive or inside of archive.
Not to be an idiot but, how do I get logs for this kind of crash? and I am trying to boot it from the desktop. Is that not a valid location for this script?
There should exist logs
directory and inside it serverstart.log
Now that I have the logs, I was comparing it to the "Max Ram" issue already posted but it appears either it was patched and no longer a problem, or went unresolved. my logs are extremely similar if not identical to theirs. @Yoosk
ERROR: Error flagged, reason is: "Settings.cfg_Error:MAX_RAM" WARN: Server startup script is exiting. Dumping current vars: DEBUG: MC_SERVER_MAX_RAM= DEBUG: MC_SERVER_FORGE_JAR= DEBUG: MC_SERVER_SPONGE_BOOT= DEBUG: MC_SERVER_JVM_ARGS= DEBUG: MC_SERVER_MAX_CRASH= DEBUG: MC_SERVER_CRASH_TIMER= DEBUG: MC_SERVER_IGNORE_OFFLINE= DEBUG: MC_SERVER_RUN_FROM_BAD_FOLDER= DEBUG: MC_SERVER_MCVER= DEBUG: MC_SERVER_FORGEVER= DEBUG: MC_SERVER_FORGESHORT= DEBUG: MC_SERVER_FORGEURL= DEBUG: MC_SERVER_HIGH_PRIORITY= DEBUG: MC_SERVER_SPONGE= DEBUG: MC_SERVER_PACKNAME= DEBUG: MC_SERVER_SPONGEURL= DEBUG: MC_SERVER_SPONGEBOOTSTRAPURL= DEBUG: MC_SERVER_ERROR_REASON=Settings.cfg_Error:MAX_RAM DEBUG: MC_SERVER_TMP_FLAG=0 DEBUG: MC_SERVER_CRASH_COUNTER=1 DEBUG: MC_SERVER_CRASH_YYYYMMDD=20180927 DEBUG: MC_SERVER_CRASH_HHMMSS=103302 DEBUG: Current directory file listing: Volume in drive C has no label. Volume Serial Number is C61B-194F
Directory of C:\Users\Main\Desktop\New folder
09/27/2018 10:33 AM
BITSADMIN version 3.0 BITS administration utility. (C) Copyright Microsoft Corp.
0 out of 0 jobs canceled.
Would it be better for me to try and bypass the serverstart.bat by manually adding and running a Forge file and MC server 12.2?
Forge installer should be included in pack, script doesn't check for mc server AFAIK.
Is it in the open? or hidden in a folder somewhere?
should look like that
That is probably the issue. All of my installs have been void of the forge installer
Are you installing to a host? Where ever you are installing to may be access restricted and thus not allowing you to run serverstart. Try running it as administrator(if this is on your pc)?
I'm installing from the Curse website, it installs to my downloads, I then use winrar to unpack it to my desktop into it's own folder. It's all my personal computer and running as admin doesn't change anything. Are there any places specifically I should check access? My computer in the past has locked certain areas giving access to no one (not sure why). @Yamza
So i found a possible solution (Currently testing), a solution to this problem is downloading the CORRECT/current forge, installing it in that file, and running it all from that jar instead of using the server start. The biggest issue is that it doesn't set RAM allocation as far as I can tell. Will update when I know more!
EDIT: This does work. There are a few errors that seem to be created this way, but as far as I can tell, if you don't have a Forge file, Get it, install it manually, then launch through the universal forge exe
Whenever I click "Serverstart" the batch file, it opens for a second with http://prntscr.com/kz7kov then closes and nothing happens. I've tried re downloading and changing the max ram value to the "5G" as the example and it still has the same issue. Any ideas?