Tags
Creators
Details
1.5.5
Compatibility
Changes
OlEncounters 1.5.5
Version 1.5.5 expands the automatic encounter system with weighted schematic variants, an in-game category editor, and stronger per-schematic setup isolation.
Weighted schematic pools
Automatic events now select a meteor type first, then choose one enabled structure from that type's variant pool. Small, Medium, Large, Epic, and Legendary can each contain multiple schematics with independent weights.
If a pool is empty, the existing meteor-types.<type>.schematic value remains the fallback.
Category Meteors GUI
Open /olencounters auto and select Category Meteors.
- Left click enables or disables a schematic.
- Right click increases its weight by 10.
- Shift+right click decreases its weight by 10.
- Large schematic collections use additional inventory pages automatically.
- Changes are saved immediately.
Saving the main automatic settings no longer removes configured categories or variants.
Per-schematic setup data
Selected variants now use their own saved:
- Mob spawn points
- Loot and vault locations
- Hologram positions
- Schematic root offset
Explicitly empty setup lists remain empty instead of inheriting positions from an unrelated meteor type.
Fixes and hardening
- Fixed automatic GUI saves wiping variant configuration.
- Fixed variants loading mob, loot, or hologram points from the wrong setup.
- Fixed empty per-schematic lists inheriting unrelated type-level points.
- Invalid or missing variants are excluded safely from automatic selection.
- Schematic file resolution is restricted to the OlEncounters schematic directory.
- Unsafe traversal paths and unsupported schematic names are rejected.
- Automatic startup logs now include the selected schematic.
- Repaired corrupted UTF-8 files in the Modrinth media kit.
- Existing configurations remain compatible and require no manual migration.
Requirements
- Paper or Folia 1.21.1+
- Java 21
- CommandAPI
WorldEdit or FastAsyncWorldEdit is required for schematic-based encounters.
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:k3YDgIH0:Nss2ljd1"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:k3YDgIH0:Nss2ljd1"
}

