Links
Tags
Creators
Details
Licensed ARR
Published last week
Updated 6 days ago
All versions
0.3.9
Release
Everforge Mod 0.3.92 months ago 6
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
Changelog
All notable changes to the Everforge Mod are documented in this file.
0.3.7
Added
- Client-side Map Survey mode for continuously revealing large Xaero map areas while flying in Spectator or Creative mode.
- Snake-pattern survey traversal with configurable bounds, altitude, lane spacing and flight speed.
- Map Survey client commands:
/mapsurvey start,/mapsurvey pause,/mapsurvey resume,/mapsurvey stop,/mapsurvey status,/mapsurvey reload,/mapsurvey speed <blocksPerSecond>,/mapsurvey spacing <blocks>,/mapsurvey altitude <y>and/mapsurvey bounds <xMin> <zMin> <xMax> <zMax>. - Persistent client survey configuration in
config/everforge-map-survey.properties.
Changed
- Default Map Survey area set to X
-16000..20000, Z-10000..20000with lane spacing272. - Default Map Survey altitude set to Y
550for terrain generated by Lithosphere.
0.3.8
Added
/mapsurvey start weststarts the survey from the player's current position and scans the first lane westbound./mapsurvey start eaststarts the survey from the player's current position and scans the first lane eastbound.
Changed
- Current-position starts use the player's current Z coordinate as the first survey lane and continue the snake pattern toward the configured southern Z bound.
0.3.9
Added
- Local JSONL audit log for commands submitted in-game by privileged players. Console and RCON commands are excluded.
- OpenPAC AutoMode for Everforge server claims. When enabled, players with effective build access are switched to Creative while inside eligible server claims and restored to their previous game mode afterwards.
- Admin commands:
/everforge automode on,/everforge automode off,/everforge automode status. - Persistent server setting
config/everforge-server.propertieswithautoMode=falseby default.
Changed
Fixed
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:k0mJvuex:bmRFChWm"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:k0mJvuex:bmRFChWm"
}

