Modpack Version

1.23.0

Describe your issue.

Not sure if this was intended, but here's a poke about it. Server seems to grab latest versions of mods on first install but runs them with Neoforge 21.1.176.

Here's the list of mods that need a newer version of Neoforge, or have their versions forced to a select version.
`
[20:08:58] [main/ERROR] [minecraft/Main]: Failed to start the minecraft server
net.neoforged.fml.ModLoadingException: Loading errors encountered:
- Mod wstweaks requires neoforge 21.1.187 or above
Currently, neoforge is 21.1.176

    - Mod gateways requires neoforge 21.1.187 or above
      Currently, neoforge is 21.1.176

    - Mod toastcontrol requires neoforge 21.1.187 or above
      Currently, neoforge is 21.1.176

    - Mod apothic_attributes requires neoforge 21.1.187 or above
      Currently, neoforge is 21.1.176

    - Mod apothic_spawners requires neoforge 21.1.187 or above
      Currently, neoforge is 21.1.176

    - Mod placebo requires neoforge 21.1.187 or above
      Currently, neoforge is 21.1.176

    - Mod hostilenetworks requires neoforge 21.1.187 or above
      Currently, neoforge is 21.1.176

    - Mod apothic_enchanting requires neoforge 21.1.187 or above
      Currently, neoforge is 21.1.176

    - Mod fastbench requires neoforge 21.1.187 or above
      Currently, neoforge is 21.1.176

    - Mod advancedperipherals requires neoforge 21.1.186 or above
      Currently, neoforge is 21.1.176

`

Crash Report

No response

Latest Log

No response

Have you modified the modpack?

No

User Modifications

No response

Did the issue happen in singleplayer or on a server?

Server

Discord Username

No response

serverstarter should install the version of neoforge listed in the provided yaml file.

are you using the official server pack with the provided startserver scripts?
is this a new install or an update to an existing install?

this is using the latest release provided on this Github, as curseforge isn't an option for where the server is being deployed.
yes, it is a fresh install.

edited on my end the .yaml file to use 21.1.197 and it's preparing spawn area now. honestly didn't see the yaml file until you mentioned it, but worth updating that file so others that are updating don't get caught out.

yeah. looks like it was an early oversight. it was fixed Jul 21 (almost 3 weeks ago). glad you got it worked out.