Links
Tags
Creators
Details
26.0.3-neoforge
Compatibility
Changes
Minecraft 26.3
Updated for Minecraft 26.3. This build targets 26.3 only — use 26.0.2 for 26.1.2 and 26.2.
Particles
Enforcement is now visible. In damage mode a beacon fires a tracer up at
the player and throws flak around them; the other modes get a quieter puff
when flight is refused. All of it is spawned server-side, so everyone nearby
sees it and vanilla clients need no mod.
Every layer is configurable — on/off, particle type, count, spacing, jitter — and can be turned off entirely.
Configuration in game
/noflyzone config— list every setting, read one, or change one, with tab-completion on both names and values./noflyzone reload— re-read the config file without restarting the server.
Changes made either way take effect immediately and are written back to
config/noflyzone.properties.
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:LNSVGQqy:848zqQDQ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:LNSVGQqy:848zqQDQ"
}

