Tags
Creators
Details
1.21.x-1.1.1
Compatibility
Changes
[1.1.1] - 2025-11-14
🎯 Stable Release
This is the stable release following 1.1.0-beta, with cleaned configuration and comprehensive documentation updates.
Changed
-
Configuration Cleanup: Removed non-functional config options that were limited by Minecraft engine behavior:
- Removed
allow_mob_attacks- mob attacks always blocked (mobs don't target players withmayfly=true) - Removed
allow_block_breaking- always blocked in ADVENTURE mode (GameMode restriction) - Removed
allow_block_placing- always blocked in ADVENTURE mode (GameMode restriction) - Removed
auto_hide_hud- behavior hard-coded to always hide (can toggle with F1) - Removed
allow_f1_hud_toggle- F1 toggle always enabled - Removed
auto_start_flying- players must double-tap spacebar (ADVENTURE mode limitation)
- Removed
-
Documentation Overhaul: Complete update of all documentation to reflect actual behavior:
- Clarified that
enable_invulnerabilitydoes NOT prevent fall damage (Minecraft engine always prevents it withmayfly=true) - Updated
enable_invulnerabilitydescription to specify it protects against mobs, lava, fire, cacti, drowning, etc. - Documented HUD behavior as hard-coded (always hides, F1 toggles)
- Documented that players must double-tap spacebar to fly (ADVENTURE mode behavior)
- Renamed "Known Issues" sections to "Known Limitations" with proper explanations
- Clarified that
Fixed
- Configuration file now generates cleanly without obsolete options
- All wiki documentation updated (Configuration-Guide, For-Server-Admins, Beta-Features, Features, Commands, FAQ)
- Updated README.md, CHANGELOG.md, Version-Comparison.md, CONTRIBUTING.md
- Removed confusing config options that appeared functional but weren't due to Minecraft limitations
Technical
- Cleaned up
ModConfig.java- removed unused config variables and cached values - Updated
SpectatorMod.java- hard-coded HUD hide behavior - Updated
ClientEventHandler.java- simplified HUD management (removed config checks) - Generated config file (
limitedspectator-common.toml) now accurate and contains only functional options
Migration Notes
If upgrading from 1.1.0-beta, your existing config will continue to work. The removed options will be ignored. No action required - the mod will use correct behavior regardless of old config values.
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:1h1Nfg72:VLanExPH"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:1h1Nfg72:VLanExPH"
}

