Tags
Creators
Details
2.3.0
Compatibility
Changes
Lootrun Reward Statistics Tracker
- Tracks reward statistics from lootrun end reward chest
- View statistics via /wynnmod statistics → Lootrun Rewards
- Reward rolls, pulls, raw emeralds accepted, and major rewards of each camp
- Recent major reward offers and accepts
- Graph overview

- An overlay that display lootrun reward statistics while near a lootrun camp, toggle under feature Lootrun Reward Statistics Tracker

Lootrun Rewards Telemetry
Share your lootrun data to help power community loot pool tracking and future reward statistics.
Enabled by default, disable anytime in Config → Wynnmod User Configuration.
What gets sent
- The loot pool when you preview it in a lootrun reward chest
- Your pulls, major reward items, and reward context when you receive a pull offer
Why we collect it
We aim to use this data to analyze lootrun rewards and help predict reward chances for a given loot pool in the future.
Those analyses need the loot pool as context, which is why we also crowdsource pool data (official Wynn API does not expose shiny type, and can be unreliable after unscheduled resets).
Loot pool menu integration
- Replace major rewards with wynnmod data (Correct shiny type will be displayed, more accurate data if an unscheduled reset happens)
- Shows popular lootrun camps
- Shows statistics for major rewards

Changed & Fixes
- Fixed gathering XP being "synced down"
- Fixed party ping working on non-party messages
- Added fixed emojis
- Added basic wynnmod screen to /wynnmod
- Improved loot pool menu loading time
Notes
We planned to include several QoL features for The Nameless Anomaly in this release, but we're still waiting on moderator approval to confirm they're allowed on Wynncraft.
They'll ship in a patch release as soon as we get the green light.
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:5HxdoOjv:iSTcxHce"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:5HxdoOjv:iSTcxHce"
}

