Minecraft Mods

A collection of small Minecraft compatibility mods and their release artifacts. Each mod is versioned independently and has a stable documentation page with its compatibility contract, installation instructions, and implementation notes.

Mods

Mod	Version	Platform	Summary	Files
Dragonfyre Boss Damage Cap Scaling	1.0.0	Minecraft 1.20.1, Forge 47.4.13	Scales fixed boss damage and DPS caps by the health multiplier already applied by L2 Hostility.	Documentation · Source · JAR

The current JAR is the exact build tested in the Dragonfyre modpack. Its SHA-256 checksum is recorded in SHA256SUMS.

Repository layout

.
├── mods/
│   └── <mod-name>/
│       ├── README.md              Detailed documentation
│       ├── <mod>-<version>.jar    Ready-to-install artifact
│       └── project/               Source, tests, and build files
├── AGENTS.md                      Repository instructions for coding agents
├── SHA256SUMS                     Release artifact checksums
└── LICENSE                        Repository license

Each mod is self-contained under mods/<mod-name>/. Keeping the projects independent avoids coupling mods that may target different Minecraft, Forge, Java, or dependency versions. The Dragonfyre source is the unchanged gameplay-tested project; its original PowerShell build is preserved for provenance but is not yet a portable repository build.

Installing a mod

Read the mod's documentation first. In general:

1. Confirm that the Minecraft, mod loader, and dependency versions match.
2. Copy the selected JAR from its repository mod directory into the Minecraft instance's mods directory.
3. Install it on both the server and clients when its documentation requires that.
4. Fully restart Minecraft. Adding or replacing a mixin mod while the game is running is not supported.

Do not install every artifact in this repository blindly. Compatibility mods are deliberately narrow and may fail to load against unsupported upstream versions.

Adding or updating a mod

• Create one stable kebab-case mods/<mod-name>/ directory containing its README.md, release JARs, and project/ source directory.
• Include the mod version in every release JAR filename; never overwrite an existing released version in place.
• Update the table above, the detailed document, and SHA256SUMS together.
• Keep upstream mod JARs, decompiled upstream sources, local game instances, worlds, logs, and machine-specific paths out of this repository.
• Do not describe a build as runtime-tested unless it was launched and tested in the target Minecraft environment.

License

Repository-authored material is provided under the MIT License. Third-party names and trademarks are used only to describe compatibility and remain the property of their respective owners.

The preserved Dragonfyre 1.0.0 JAR still contains license = "All Rights Reserved" in its Forge metadata. It has not been modified because preserving the gameplay-tested binary takes priority. That embedded declaration should be aligned with the repository license when the source build is modernized and a new version is rebuilt.