Mod Exclusions

Last modified: 22 September 2024

Clientside-only modslist

Updating

If you wish to use the latest and greatest hits of clientside-only mods ServerPackCreator has to offer, you need to update it via Menu Bar -> Edit -> Update Fallback Clientside Modslist and then either

  • In the GUI, head to the Advanced Section of your server pack config, to the clientside- and whitelist, and click the reset-button (cog with two red arrows)

OR

  • Clear your clientside-only mods list in your config, save it, then load it again (either via the menu or by restarting SPC)

OR

  • Generate a new configuration and migrate your old config to it

OR

  • Generate a new configuration and copy the list to your old config manually

OR

  • Empty the clientside-mods field, save the configuration, load the configuration. This will fill it with the default clientside-mods list

If you added custom mods to this list, you must make sure you migrate them over to the new setting yourself.

Filter methods (3.12.x and up)

You can change the behaviour with which ServerPackCreator filters the mods with the list of clientside-only modslist you specify. By default, ServerPackCreator will check each entry in that list against the name of every mod-JAR in your modpacks mods-directory and see whether said JAR starts with said entry.

Example:

  • JAR: BetterPingDisplay-1.16.5-1.0.jar

  • Entry: BetterPingDisplay-

The mod will be excluded, because its name starts with BetterPingDisplay-.

This behaviour can be changed by editing de.griefed.serverpackcreator.serverpack.autodiscovery.filter=START in serverpackcreator.properties.

There are five possible settings which affect the way these filters happen:

  1. START

    • Default setting. Checks whether the name of a mod starts with a given entry.

  2. END

    • Checks whether the name of a mod ends with a given entry.

  3. CONTAIN

    • Checks whether the name of a mod contains a given entry.

  4. REGEX

    • Performs a regex-match of the name of a mod against a given entry.

  5. EITHER

    • Not recommended unless you know exactly what you are doing. If used carelessly, this can result in all mods or unwanted mods being excluded. Checks whether any of the above result in a positive match.

Automatic detection of clientside-only mods

ServerPackCreator can try and automatically determine whether a mod is clientside-only or not. This feature is enabled by default. In order to deactive/activate it manually, set de.griefed.serverpackcreator.serverpack.autodiscoverenabled to true (enable) or false ( disable).

Keep in mind: This feature is not 100% foolproof. It can not and will not detect every clientside-only mod due to the diverse nature of Minecraft mods and the way their creators declare sideness or dependencies.

If you encounter a mod that did not get caught by the autodetection and is not yet present in the fallback-list, please create an improvement request on GitHub with the title being similar to

tip

In the What's the feature you would like to be improved?-section, something along the lines of

tip

I would like the following mods to be added to the fallback-modslist

  • mod-x (Link to CurseForge project)

  • mod-y (Link to CurseForge project)

  • mod-z (Link to CurseForge project)