Description

Recent versions of forge have switched to using java headful library loading rather than jar files.
The container bulldozes the startup command line rendering users unable to change the default command to:
java @user_jvm_args.txt @libraries/net/minecraftforge/forge/1.18.2-40.2.9/unix_args.txt nogui
which is how forge expects to be invoked for MC Versions higher than 1.17.1

Steps to Reproduce

sudo docker run -p 25565:25565 -e SERVER_PROVIDER=forge -e MC_VERSION=1.18.2 -e SERVER_BUILD=1.18.2-40.2.9 okazakee/mcserver-lazymc-docker

Behavior

The container tries to start the server, but it fails due to no headful library support

Forge Logs:
forge-1.18.2-1.18.2-40.2.9.jar.log

Your Environment

• Docker okazakee/mcserver-lazymc-docker:latest

Discussed in #20

Description

the server script makes a number of calls to serverjars.com, however, this site has been down for a couple of months. Maybe it is possible to point it to archive.org as a workaround?

Steps to Reproduce

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected Behavior

Please describe what you expected to happen.

Screenshots

If applicable, add screenshots to help explain your problem.

Your Environment

• OS: [e.g. Windows, MacOS, Linux]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Additional context

Add any other context about the problem here.

Description

Starting a new server results in lazymc being disabled due to incorrect CPU Architecture (reporting as x64 when it should be x86_64 or vice versa?)

Server starts up fine otherwise

Error shown

Warning! Your CPU architecture (x64) is not supported by Lazymc. Disabling it...

Docker Compose

services:
  mcserver-lazymc-docker:
    image: okazakee/mcserver-lazymc-docker:latest
    ports:
      - "24565:25565" # change port for multiple instances
    container_name: minecraft-server
    restart: on-failure
    environment:
      SERVER_PROVIDER: fabric
      LAZYMC_VERSION: latest
      MC_VERSION: latest
      SERVER_BUILD: latest
      MC_RAM: 4G
      JAVA_OPTS: "-XX:+UseG1GC -XX:+ParallelRefProcEnabled -XX:MaxGCPauseMillis=200 -XX:+UnlockExperimentalVMOptions -XX:+DisableExplicitGC -XX:+AlwaysPreTouch -XX:G1NewSizePercent=30 -XX:G1MaxNewSizePercent=40 -XX:G1HeapRegionSize=8M -XX:G1ReservePercent=20 -XX:G1HeapWastePercent=5 -XX:G1MixedGCCountTarget=4 -XX:InitiatingHeapOccupancyPercent=15 -XX:G1MixedGCLiveThresholdPercent=90 -XX:G1RSetUpdatingPauseTimePercent=5 -XX:SurvivorRatio=32 -XX:+PerfDisableSharedMem -XX:MaxTenuringThreshold=1"
    volumes:
      - "./fabric-001:/mcserver"

On the very first startup of the container (empty volume dir) the "lazymc.toml" is generated but not updated/modified afterwards.

This happens because the logic in "mcserver.sh" to modify the "lazymc.toml" file is only executed if the "lazymc.toml" file already exists.

Workaround: Restart the container. On the second startup "lazymc.toml" will be modified correctly.

Proposed fix: Move the lines after line 212 ("Add new values to lazymc.toml") out of the else-block so they will be always executed when the script runs.