Tags
Creators
Details
Licensed MIT
Published 6 months ago
Updated last week
All versions
1.2.2
Release
InvSee 1.2.2last week 64
Compatibility
Minecraft: Java Edition
1.21.11
Platform
Forge
Supported environments
Server-side
Singleplayer
Changes
Released for NeoForge, Forge and Fabric, and for the Paper and Spigot plugins.
Fixed
- The mod did not load on Forge 1.20.1 to 1.21.11 or NeoForge 1.20.2 to 1.20.4. Mistakes in its metadata made Forge reject it and NeoForge ignore it. It now loads on these versions.
- Items lost from old saves (mods). Opening an offline player who last played on an older Minecraft version could show their items wrongly: on 1.20.5 and newer, a save from before 1.20.5 showed a stack of 64 as a single item with no enchantments, and any edit made that permanent. Old saves now go through the game's own upgrade first, the same as when the player logs in.
/invseeon yourself duplicated items (mods). A shift-click doubled the stack. Opening your own inventory this way is now refused.- Items duplicated or lost when the player logged in with the menu open. Anything taken out was duplicated, and anything put in disappeared. Changes now save as you make them instead of when the menu closes, so the player logs in with exactly what the menu showed.
- Two moderators could take the same items from an offline player. Each had a private copy, and the later save could undo the earlier one. Everyone viewing the same offline player now shares one copy and sees each other's changes straight away.
Changed
- Saves from a newer Minecraft version (mods): a player file written by a newer version than the server is running no longer opens, because this version can't read what's in it.
- Failed saves (mods): these used to be ignored. The moderator now gets an error in chat, the reason goes in the server log, and the save keeps retrying while the menu is open.
- Menus only write what you changed (plugins): just looking at an offline player no longer rewrites their file, and closing a menu no longer overwrites what an online player picked up since it last refreshed.
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:javU3y9N:ZEOaTQHH"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:javU3y9N:ZEOaTQHH"
}

