Tags
Creators
Details
1.0.3
Compatibility
Required content
Changes
🚀 Anti-Invisibility v1.0.3
Anti-Invisibility gives you the ultimate quality-of-life upgrade for dealing with invisibility potions on multiplayer servers by making invisible players visible as configurable translucent ghosts.
✨ Features
-
Translucent ghost rendering: Invisible players no longer vanish completely. They are rendered as translucent ghosts so you can still track their movements.
-
Nametag restoration: Restores nametags for invisible players, fixing the vanilla mechanic that hides them.
-
Invisibility icon: Automatically adds the classic invisibility potion icon next to the nametags of invisible players for quick visual identification.
-
Complete ModMenu integration: Configure everything in-game through the ModMenu settings screen.
- Master toggle: Instantly enable or disable the mod.
- Opacity slider: Adjust how visible invisible players are, from 0% to 100% (default: 50%).
- Nametag toggle: Choose whether invisible players have their nametags restored.
- Nametag icon toggle: Choose whether the invisibility icon appears next to restored nametags.
-
Improved settings behavior: When the master toggle is disabled, all other options are automatically grayed out, making it clear that the mod is inactive.
🆕 What’s new in v1.0.3
-
Massively expanded version compatibility
- Minecraft 1.21.x
- Minecraft 26.1.x
- Minecraft 26.2
-
Better configuration UX: Settings are now disabled and grayed out whenever the mod is turned off.
-
⚠️ Crash issues - Will be fixed in 1.0.4 ⚠️
⚙️ Technical details
- Supported versions: Fabric 1.21.x, 26.1.x, and 26.2.
- Client-side only: No server installation required. Works on vanilla multiplayer servers, Realms, and custom servers.
Requires Fabric API. ModMenu is highly recommended for the in-game configuration screen.
Optional dependencies
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:2KaxJZJT:S9mojoRs"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:2KaxJZJT:S9mojoRs"
}

