Links
Tags
Creators
Details
v2.2
Compatibility
Changes
Infinite Card 2.2 Changelog
Date: 2026-10-03 Status: released
Major Updates
- Card Mode now has isolated protected inventories, hotbars, deck state, and battle state. Mode transitions, save/reload recovery, and board teardown no longer leak state into other modes.
- Added a complete Ladder Adventure route with themed nodes, consecutive battles, and a final Boss. Players start at rating 1000; rating affects encounter-value multipliers and battle pressure.
- Ladder and ordinary Adventure share the deck entry, but Ladder uses an 8-16 card rule and allows Chaos cards. Added a left-to-right mileage track with ordinary card-pack claims.
- Added two-sided player trading with offer management, ready state, final confirmation, cancellation rollback, and a visible trade-status item. Card tooltips are localized per player.
- Added PvE and PvP spectator support with six board seats, mounted seating, Shift-to-exit, read-only card-pool access, and read-only creature-codex access.
- Rebuilt card visuals, including card faces, borders, information panels, and layered models. Standard, Iron, Gold, and Diamond finishes now have distinct presentations.
Minor Fixes And Improvements
-
Chaos transformations now refresh the active deck automatically, replace the old instance, and remove consumed sacrifice cards.
-
Advancement synchronization now preserves the selected Ladder view instead of falling back to the ordinary Adventure route during screen initialization.
-
Ladder wax seals reuse the normal wax-seal data path while showing the Ladder rating as the difficulty label.
-
Adventure and Ladder entry flows share the protected inventory and hotbar refresh path.
-
Fixed inventory synchronization, disconnect recovery, board cleanup, route events, enemy pacing, and additional localized UI details.
-
Fixed empty or incorrect Ladder advancement pages.
-
Fixed stale Chaos card references causing archive validation errors after transformation.
-
Fixed client advancement-screen initialization and several mode-transition inventory refresh issues.
-
Fixed board teardown leaves after battle completion or mode changes.
-
Fixed card visual overlap, stale Sigil persistence, recovery placement, disconnect camera state, and related battle/event edge cases.
Validation
- Passed
compileJava,compileClientJava,compileTestJava, and the complete Gradle JVM test suite.
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:NZPkvnYL:5Lro5yjA"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:NZPkvnYL:5Lro5yjA"
}

