Specify config parameters in msh exec string

[PadowYT2]

On startup it creates a config.json. Can I somehow prevent generating it and startup with the variables in the startup? Also is #gekware/minecraft-server-hibernation/122 a thing in the egg. Because the limit is stuck to 100% (if 100% allocated)

[idlenode]

yes

[BolverBlitz]

The config.json isn´t generated on startup, its made when a server gets installed the first time (Or you clicked "Reinstall Server").
Its only generated on startup when it was deleted, but then the port, memory and other settings will be wrong and will lead to a crash.

Thats why i generate the config on installation and there are no variables, exept server jar name you can edit in the startup tab.
Just click reinstall after to generate the config.

[PadowYT2]

Not about talking about about how it works/generates (not the point). I'm trying to say that is there a way to startup without it. And about second question?

[BolverBlitz]

Yes, you can remove the generation.
Remove Line 59 of the install skript:

curl -o config.json -X GET "https://api.ebg.pw/api/v1/MSH-ConfigGenerator/2-4-1?FileName=${SERVER_JARFILE}&ServerType=${VENDOR}&Version=${MINECRAFT_VERSION}&RAM=${SERVER_MEMORY}&Port=${SERVER_PORT}&StopTime=${TBSES}&StopServerAllowKill=${KILL_TIME}"

But your egg wont work without manual settings then (Exept it randomly runs on default minecraft port)

[PadowYT2]

Yes, you can remove the generation. Remove Line 59 of the install skript:

curl -o config.json -X GET "https://api.ebg.pw/api/v1/MSH-ConfigGenerator/2-4-1?FileName=${SERVER_JARFILE}&ServerType=${VENDOR}&Version=${MINECRAFT_VERSION}&RAM=${SERVER_MEMORY}&Port=${SERVER_PORT}&StopTime=${TBSES}&StopServerAllowKill=${KILL_TIME}"

Well I meant remove it and make functional in startup or somewhere else

[BolverBlitz]

@gekigek99 If MSH supports the stuff as start parameters, then yes.
Like: ./msh -port 4000 -ram 1024 ... etc

As far as i know, it dosn´t.

[PadowYT2]

@gekigek99 If MSH supports the stuff as start parameters, then yes. Like: ./msh -port 4000 -ram 1024 ... etc

As far as i know, it dosn´t.

How about the second question?

[gekigek99]

@BolverBlitz @PadowYT2

port and ram can be set in the start parameters (in the dev branch), as you can see here

this is relative to the msh executable tho, in the egg I know that there might be some restrictions to prevent server resources abuse.

[BolverBlitz]

Ok, great. Then only the minecraft protocol version will be wrong on first startup but that dosn´t mean it wont work.

[PadowYT2]

@BolverBlitz @PadowYT2

port and ram can be set in the start parameters (in the dev branch), as you can see here

this is relative to the msh executable tho, in the egg I know that there might be some restrictions to prevent server resources abuse.

That's great, I know how to add it in the egg, the catch is, is there an example how to use them?

[BolverBlitz]

Once the next MSH Version gets released i´ll update the egg to use start parameters as you sugested, currently some reqired parameters aren´t supported so cant do it right now.

[gekigek99]

@PadowYT2 Now i'm not from pc so I can't test it but an example could be this (write this string in the egg command to start the server):

.\msh.exe -p 4000 -P "-Xmx1024 -Xms1024"

@BolverBlitz correct me if i'm wrong

[PadowYT2]

@PadowYT2 Now i'm not from pc so I can't test it but an example could be this (write this string in the egg command to start the server):

.\msh.exe -p 4000 -P "-Xmx1024 -Xms1024"

@BolverBlitz correct me if i'm wrong

correction theres no .exe in ptero xD, but I'll try that too, thanks