1.0.16
Compatibility
Changes
Contur 1.0.16
This release prepares Contur for public testing and improves the installation experience for server administrators.
Highlights
- Instanced dungeon worlds with safe reservation, cleanup and restart recovery
- Frameless entry and exit portals
- Keys, locked doors and progression chains
- Custom mobs, bosses, spawners and multi-stage waves
- Controlled natural spawning with world, biome, block, height, light and population conditions
- Visual event system with triggers, conditions and ordered actions
- Console and player command execution for compatible cross-plugin integrations
- Reusable loot presets, generated containers and boss rewards
- Artifacts, the Obelisk and unlockable reward chambers
- Relics, custom items and custom recipes
- PostgreSQL persistence, audit, backups, history and anti-duplication protection
- English and Russian server-wide localization
Documentation
The administrator manual now includes beginner-friendly PostgreSQL setup instructions for:
- game hosting and managed PostgreSQL
- Windows without Docker
- Linux VPS
- Docker and Docker Compose
- remote databases, SSL, firewall and
pg_hba.conf - connection troubleshooting
CONTUR_DB_PASSWORD- first startup and Flyway migration checks
Fixes
- Fixed anomaly cleanup recovery using the correct PostgreSQL V54 field
- Fixed damaged English manual text related to Controlled Natural Spawning
- Added automated documentation quality checks
- Updated README, upgrade guide and machine context for version 1.0.16
Tested environment
- Minecraft Java Edition
26.2 - Purpur
26.2 build 2614 stable - Java
25 - PostgreSQL
17.10
PostgreSQL 14+ is supported.
Testing notice
This version has passed automated tests and runtime smoke testing, but it is still published for public testing.
Test it on a separate server or staging copy first. Keep backups of your worlds, plugin files and PostgreSQL database before enabling it on an existing production server.
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:AwAyLf0v:gQaVhQTT"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:AwAyLf0v:gQaVhQTT"
}

