Startup Issue with Minecraft - Minecraft Can't Find "ForgeMod.jar"

Technical Support
, , ,
1

System Information

Field Value
Operating System Windows - Windows 11 Pro on x86_64
Product AMP ‘Decadeus’ v2.4.6.4 (Mainline)
Virtualization None
Application Minecraft
Module MinecraftModule
Running in Container No
Current State Failed

Problem Description

Issue

I need help, as this is an issue preventing my server from starting normally!

This is because it does not exist, and will not because the version I am running is 1.20.1. I don’t know how to fix this, as there is no such thing as a “ForgeMod.jar” for 1.20.1, and I don’t want to go “Googling” for a random jar from the internet as a crutch of a fix…

I can include logs, etc. but this should be a pretty obvious issue and hopefully a pretty obvious fix… (change the AMP launch panel to run the “run.bat” instead of the ForgeMod.jar on certain MC versions).

I look forward to a reply,
//TheModdersDen

Reproduction Steps

  • Create a Minecraft server in the AMP Instance Manager
  • Set the server type to Forge
  • Change the server Forge version to 47.2.0 and update it.
  • Try to start the server. Issue presents itself here…
2

Weird issue that sometimes shows up with newer Forge since they don’t have a proper Jar anymore.

  • Make sure the server Jar is set to [Autoselect]
  • Double check that you hit Download/Update under Server Settings

If that fails, go to the main AMP screen and Stop/Start the MC instance, see if that kicks it over.

3

Testing that now. Thanks for the quick reply! :slight_smile:

EDIT: Server is set to [Autoselect] and I did update through the Server Settings menu. No luck starting the server. I’m going to try building the server from scratch and see if that fixes it…

EDIT 2: Quick update: looks like I may have had success starting the server, but it crashed multiple times. For some reason, it presented both errors, the one about ForgeMod and the one about multiple crashes and I mis-read it… Looking into it now…

EDIT 3: Yup. A slight bug in AMP’s UI (likely due to the MANY browser extensions I have), but now that I know what caused it, I fixed it… Thank you for the really quick help! :slight_smile:

4

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.