Issue with ATM10

[ArmonicPvP]

Describe the problem

ATM10 is getting an error when starting:

SmithingTemplateViewer (smithingtemplateviewer) has failed to load correctly

Their devs say issue is related to the docker and how it is pulling files: AllTheMods/ATM-10#2722

Container definition

Paste run command or compose file here

Container logs

Paste logs here

[itzg]

It's not about how files are pulled -- the image downloads the mods listed by the modpack or not based on exclusions either by the mod metadata or by the image/user exclusion list. They're refusing to be supportive even when it was pointed out that mod is clearly client-only.

Server pack files can be used with https://docker-minecraft-server.readthedocs.io/en/latest/types-and-platforms/mod-platforms/curseforge/ but I no longer answer issues or questions about those. Modpack authors are too inconsistent with server modpack structure.

[itzg]

With the latest image this server started up fine for me:

services:
  mc:
    image: itzg/minecraft-server
    tty: true
    stdin_open: true
    ports:
      - "25565:25565"
    environment:
      EULA: true
      MOD_PLATFORM: AUTO_CURSEFORGE
      # Allocate API key from https://console.curseforge.com/
      # and set in .env file making sure to double up dollar signs, such as
      # CF_API_KEY=$$2a$$10$$....
      # Refer to https://docker-minecraft-server.readthedocs.io/en/latest/types-and-platforms/mod-platforms/auto-curseforge/#api-key
      CF_API_KEY: ${CF_API_KEY}
#      CF_SLUG: all-the-mods-10
      # 2.47
      CF_PAGE_URL: https://www.curseforge.com/minecraft/modpacks/all-the-mods-10/files/6502777
      # Optional: select a specific version/file
      # CF_FILENAME_MATCHER: "1.17"
      MEMORY: 4G
      CF_OVERRIDES_EXCLUSIONS: |
        shaderpacks/**
    volumes:
      # Use managed volume by default, but can change to a relative path like
      # ./data:/data
      # to use a host directory
      - mc-data:/data
volumes:
  mc-data:

[ArronaxKP]

Thanks itzg, I can't imagine how painful it is to get constant issues raised for server pack specific issues.

If other find this, I had this issue, and I fixed it by adding CF_EXCLUDE_MODS with the value smithing-template-viewer (originally I had the id excluded 1133580). Worked without issues after that. Not tried the latest docker image though or if they have updated the server pack in Curse.

Edit - correct fix: see note from itzg further down. Copied to make it clear on my comment

Setting CF_FORCE_SYNCHRONIZE to true would cause the mods to be redownloaded, otherwise you need to do manual mod file removals instead.

[ArmonicPvP]

Thanks itzg, I can't imagine how painful it is to get constant issues raised for server pack specific issues.

If other find this, I had this issue, and I fixed it by adding CF_EXCLUDE_MODS with the value 1133580. Worked without issues after that. Not tried the latest docker image though or if they have updated the server pack in Curse.

For anyone else trying this, this method also worked for me. However, I had to first delete the mod from my mods folder. Then, it worked like a charm.

[itzg]

Referring to this section setting CF_FORCE_SYNCHRONIZE to "true" would have avoided needing to manually remove the mod.

[itzg]

Can also use the slug smithing-template-viewer instead of the ID

Since the latest image already excludes that, probably setting CF_FORCE_SYNCHRONIZE was the original fix.

[ArronaxKP]

Ah that's it. I have force on true due to a previous issue that I forgot about. Thanks