Player's Choice

This modification offers modpack developers the capability to include additional mods and modules with default disabled status in their builds. The functionality resembles classic modpack launchers like the legendary Yogbox from previous game versions.

Important Technical Feature

Accelerated loading of Player's Choice may cause conflicts with core modifications. This is a technical limitation related to the specific workings of coremods.

This issue is successfully resolved by adding the identifiers of conflicting modifications to the special "crashing_mods" list within the playerschoice.json configuration file.

Working with the Modification

Upon first launch, modpack users see a specialized selection menu. In this interface, they can activate the desired additional mods. All parameters of optional content - names, descriptions, links, and categories - are set by the build author.

Configuration requires the playerschoice.json file in the configuration directory. Information about selected mods is saved to the fmlModState.properties file located in the same directory. Essentially, the mod serves as a convenient wrapper for an underutilized Forge platform feature.

Advanced Configuration

Each entry in the JSON file supports two parameters:

• category - creates visual grouping of elements in the interface
• group - creates mutually exclusive groups where activating one element blocks others

It is recommended to add categories for all mandatory functional groups for user convenience. The ! prefix before a group name makes it mandatory for activation.

Additional technical capabilities:

• extraMods - automatic enabling of related dependent mods
• copyFiles - copying additional files when an element is activated

Files for copying are placed in the /config/playerschoice_files directory. For example, the hardmode.zs script will be located at /config/playerschoice_files/scripts/hardmode.zs and referenced in copied files as scripts/hardmode.zs.

Important Note for Developers

When preparing a modpack for publication, it is strictly necessary to remove the playerschoice.marker file from the instance root folder. For debugging purposes, simply delete it manually.