0.3.3
Compatibility
Required content
Changes
Minecraft Wrapped 0.3.3 (26.1.x)
Combines the unreleased 0.3.2 fixes with the new 0.3.3 fixes. Users on 0.3.0 / 0.3.1 get all of them in one update.
Bug fixes
- Removed all server-side control over consent. Earlier 0.3.x jars polled
minecraftwrapped.com/api/consent/<uuid>every 30 minutes and overwrote local tier flags from the response. Moderation correctly flagged this as remote control over the user's consent. Consent is now strictly local on the client. The mod reports its current consent on each ingest batch so the dashboard can mirror per-install state, but the backend never pushes values back. The/api/consent/<uuid>endpoint has been removed entirely. - Fixed: pre-mod single-player playtime not being imported on Minecraft 26.1. Vanilla 26.1 moved per-world stats from
<world>/stats/<uuid>.jsonto<world>/players/stats/<uuid>.json(alongsideplayers/data/,players/advancements/). 0.3.0 and 0.3.1 still read the old path, found nothing, and silently stamped "import done." The mod now checks the new 26.1 path first and falls back to the legacy path. - Auto-recovery for users on 0.3.0 / 0.3.1: the historical import re-runs once on upgrade so anyone whose history was silently skipped gets it back. No manual reset needed.
- Fixed: historical playtime no longer doubles on
/wrapped link. The post-link trigger used to clear the "import done" stamp and re-emit every world's stats, doubling lifetime counters. The trigger is now idempotent — if the warmup thread already ran, linking is a safe no-op.
What you need to do
Drop the new jar in your mods/ folder and launch. If you were affected by the 26.1 path bug, your single-player history will appear on the dashboard within a few minutes of the next sync.
Tier toggles
Tier capture flags (Tier 1 / Tier 2 / Tier 3) live in your local config at ~/.minecraft/config/minecraftwrapped.json. Edit and restart the game to change them. The dashboard's "What's captured" view is read-only — it shows what your installs have most recently reported, but cannot push values to the mod. This is by design.
Supported versions
Minecraft 26.1, 26.1.1, 26.1.2 · Fabric Loader 0.18+ · Fabric API 0.146+
The mod will refuse to load on any version outside >=26.1 <26.2 with a clear error from Fabric Loader.
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:AnMdGbAH:WJ5dQQ3n"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:AnMdGbAH:WJ5dQQ3n"
}

