1.0.1
Compatibility
Required content
Changes
Moonlit Broker v1.0.1 — Major Bounty & Mark Experience Overhaul + Behavior Fixes
✅ Key changes (you’ll feel them immediately)
Bounty Contracts now feel more “natural”
Common hostile mobs can now drop Bounty Contracts at a low rate (no longer skewed only toward elite/high-tier mobs).
Contracts are generated in common / elite / rare tiers.
No more keeping a Mark in your inventory just to trigger bounties
The system now uses “historical registration”: once you’ve interacted with the Moonlit Broker and registered, you can trigger Bounty Contract drops.
Your Mark can stay in a chest / backpack expansion—no more wasted inventory slot.
If you’re not registered, you’ll get a hint—but it won’t spam
If you haven’t registered yet, killing eligible mobs may occasionally remind you to visit the Moonlit Broker to register (30s limit per player).
After you successfully register for the first time, you’ll also get a one-time confirmation message:
You can now receive Bounty Contracts as drops from eligible mobs.
🧾 Contracts are safer (updates won’t screw you over)
Expired contracts can be recycled for a refund
If a contract’s target becomes invalid in a new version (e.g., removed from the target pool), turning it in will show “Contract expired”, then:
the contract is reclaimed, and
you get a small Silver Note refund (default x1).
🔇 Fixes & QoL
Removed leftover Wandering Trader milk/potion drinking behavior + subtitles
You will no longer see things like: “Wandering Trader drinks milk”.
“Contract not established …” message is now unambiguous
That message is actually related to the Katana Contract (not the Bounty Contract).
The text now explicitly says it’s about the Katana Contract, and it has a 30s rate limit—no more combat spam, and no more confusion that bounties are broken.
🛠 Player / Server Admin Commands
/moonlit status: Check whether you are registered (Mark bound)
/moonlit check_mark <player> (admin): Check a player’s registration status
/moonlit reset_mark <player> (admin): Reset a player’s registration (and clear bounty drop cooldown)
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| xqanzd_moonlit_broker-1.0.1.jar | Unknown | 1.67 MiB |
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:B1JqUi9x:wTw2oyhV"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:B1JqUi9x:wTw2oyhV"
}

