RELICS & REGALIAWIKI / 0.2.1Installation
Requirements
| Component | Requirement |
|---|---|
| Minecraft Java Edition | 1.21.1 |
| Loader | NeoForge 21.1.250 or newer compatible 21.1.x build |
| Java | 21 |
| Curios API | NeoForge 9.5.1+1.21.1 or compatible newer build |
| Relics & Regalia | 0.2.1 for the power settings documented here |
The declared dependency ranges are minimums, not proof that every newer release is compatible. Fabric and Forge builds are not provided by this project.
Install on a client
- Create or choose a Minecraft 1.21.1 NeoForge instance.
- Put the matching Curios API and Relics & Regalia JARs in that instance’s
modsfolder. - Remove an older Relics & Regalia JAR from the same folder after backing it up; do not load two versions together.
- Launch the game. Confirm both mods appear in the loaded mod list.
- Open a disposable world first. Use the Combat creative tab to find the equipment and test equipping it.
Install on a server
Install the same Relics & Regalia build and compatible required dependencies on the server and every connecting client. This is not a server-only mod. Version 0.2.1 changes the relic network protocol; older builds should not be mixed with it.
Start and stop the server once to generate its config files. Edit the settings with the server stopped, then restart. Keep acquisition settings consistent in the pack’s client configs as well as on the server. New power settings are server-controlled and synchronized to clients.
Optional mods
- Create 6.0.10 was the integration baseline. Enables the Master Mechanic gear in recipes, random loot and the creative tab, plus its powers.
- Ars Nouveau 5.13.1 was the compilation baseline for Leyline Pendant support.
- Iron’s Spellbooks 3.16.3 was the compilation baseline for its Leyline support.
These are project baselines rather than a claim of a fresh gameplay test against every combination. See compatibility.
Existing worlds
The 0.1.0 to 0.2.x transition replaces eight old relic IDs with twelve different relics. There is no migration mapping in the current code. Keep a full world and profile backup and test the upgrade on a copy. Stay on 0.1.0 if you need to preserve the old relics until a migration strategy is supplied.
The 0.2.1 config update preserves the 0.2.0 equipment registry IDs. Existing recorded cooldowns retain their end times; changing a cooldown value controls future triggers. Quest rewards referencing removed 0.1.0 IDs must be revised separately.