Tags
Creators
Details
Licensed GPL-3.0-only
Published 3 years ago
Updated 10 months ago
All versions
1.10.0
Release
Konquest 1.10.0last year 156
Compatibility
Minecraft: Java Edition
1.21–1.21.8
1.20.x
1.19.x
1.18.x
1.17.x
1.16.x
Platforms
Paper
Purpur
Spigot
Changes
For complete history, Click Here.
- Added support for Minecraft 1.21.6, 1.21.7, 1.21.8. Updated Spigot API to 1.21.8.
- Added permissions (true by default) to control town raid alerts.
konquest.raid.entry- Enables raid alerts upon entering enemy territorykonquest.raid.first- Enables raid alerts on first critical block break in town monumentskonquest.raid.half- Enables raid alerts on half of total critical block break in town monumentskonquest.raid.last- Enables raid alerts on second to last critical block break in town monuments
- Added
core.ymlsettings for kingdom and player score attribute weights. - Added
SPECIALIZEadmin property flag for towns and capitals. When the flag is false, town lords cannot change town trade specializations, when the feature is enabled. Admins can always change it. - Added Town Option
KINGDOM_RESIDENTS, to make new kingdom members automatically join towns as residents. Default setting is true for capitals, and false for all towns. - Added settings to override Town Options, both globally and per-town/capital, in
town-options.ymlconfig file. - Added global events with server-wide effects and schedules.
- Added Konquest API events
KonquestGlobalEventEndEvent,KonquestGlobalEventStartEvent, which can be used with DiscordSRV alerts to show when events start and end. - Added placeholders
%konquest_events%,%konquest_event_effects%to show currently active event details. - Added commands
/k event,/k admin event. - Added GUI menu for global events,
/k event menu. - Added
core.ymlconfig settingcore.event_intervalto control how often the server checks for events to start, or to disable all events when 0.
- Added Konquest API events
- Bug Fixes
- Fixed integration with DiscordSRV where Konquest would sometimes not detect that DiscordSRV was ready on server startup.
- Fixed monument template creation problem where clicking on region corners would sometimes cancel the creation process.
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:uM8CLEbn:5AaA2vKu"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:uM8CLEbn:5AaA2vKu"
}

