[Crash]: Server crash on startup

[stevenmodl]

Possible Fixes

Yes

Modpack Version

2.46

What happened?

I updated my ATM 10 server to the latest version and now it crashes on startup.

Crash Log

https://gist.github.com/stevenmodl/a0c8cf5e0de04169ba9de9137970132c

Latest.Log

https://gist.github.com/stevenmodl/0dfd4d711b5620934a0df246e513060a

[pietro-lopes]

Yes, some client file got in the server files, we are reuploading.
You can remove the mod: smithingtemplateviewer from the mods folder and you are fine.

[pietro-lopes]

File is already updated on CF

[Centinjs]

File is already updated on CF

well i updated it on cf and i updated it my server hosting and it runs with the files that ari in cf and it is not leting the server to start up

[Ghosty-chan]

Just wanted to update my 2nd client, noticed 2.46 is suddenly unpublished on CurseForge...
(server + 1st Client seems to run fine)

[pietro-lopes]

There was a crash at world rejoin on smithing template viewer, we had to remove it.
2.47 should be ready in ~20 minutes

[pietro-lopes]

Up on CF

[Inkertus]

I just updated my Docker container to 2.47 and ran into this issue. What file do I have to edit to remove the smithing template mod?
It auto-downloads it upon execute and download of the pack.

[AerikAwesome]

I just updated my Docker container to 2.47 and ran into this issue. What file do I have to edit to remove the smithing template mod? It auto-downloads it upon execute and download of the pack.

Assuming you are using the itzg/minecraft-server image, you can add environment variable "CF_EXCLUDE_MODS" with value "1133580" (the Curseforge project id for Smithing Template Viewer). You might also have to manually delete the offending mod from the mods folder before starting your new container.

[Inkertus]

I just updated my Docker container to 2.47 and ran into this issue. What file do I have to edit to remove the smithing template mod? It auto-downloads it upon execute and download of the pack.

Assuming you are using the itzg/minecraft-server image, you can add environment variable "CF_EXCLUDE_MODS" with value "1133580" (the Curseforge project id for Smithing Template Viewer). You might also have to manually delete the offending mod from the mods folder before starting your new container.

So far this has enabled my server to load. I am still new to the myriad flags docker-compose has so this escaped me.
Much appreciated!

[cebarks]

I just updated my server to the most recent version on CurseForge and still ran into this issue. Even after deleting everything and redownloading it still pulled the broken mod. removing the smithingtemplateviewer mod seems to have worked.