Startup Issue with Minecraft - FTB Direwolf20 1.20 starts vanilla server

[Stefan_Nitu]

System Information

Field	Value
Operating System	Linux - Debian GNU/Linux 12 on x86_64
Product	AMP ‘Callisto’ v2.5.0.14 (Mainline)
Virtualization	Docker
Application	Minecraft
Module	MinecraftModule
Running in Container	Yes
Current State	Failed

Problem Description

Issue

The server runner seems to not find the jar in “libraries/net/neoforged/forge/[…].jar”. It starts a vanilla server and when trying to scan for other jars, it doesn’t find the correct one (“libraries/net/neoforged/forge/[…].jar”).

Reproduction Steps

• Create new Minecraft Instance
• Select FTB (new) and the “FTB Presents Direwolf20 1.20” modpack
• Start server

[ThePotatoKing]

You need to select the NeoForge server type and NeoForge version for it to start properly, since there isn’t a proper Jar.
Guide here for the full list of steps:

Forge Frequently Asked Questions

Forge Frequently Asked Questions How do I run Forge using: start.sh/start.bat? No need! AMP handles all that for you. Just select the version of Forge you’ll need, hit update, and start your server. Where do I put custom start up arguments? You can find this options under: Configuration → Java and Memory → Additional java options I installed a modpack using AMP’s FTB downloader, why did it start in Vanilla? or The update manager reported a successful update, but ./Minecraft/minecraft_server.j…

[Stefan_Nitu]

This worked! Thanks a lot!