Tags
Creators
Details
All versions
1.1.3
Release
BoatRacing 1.1.37 months ago 109
Compatibility
Minecraft: Java Edition
1.21.x
1.20.x
1.19.x
Platforms
Bukkit
Folia
Paper
Purpur
Spigot
Changes
Changelog
1.1.3 — 2026-03-30
Added
- Parallel race sessions by track: race lifecycle commands now operate per track session, allowing multiple tracks to run registration/races at the same time.
- Map vote commands: added
/boatracing race voteopen <track1> <track2> [seconds],/boatracing race vote <track>,/boatracing race voteui,/boatracing race votestatus, and/boatracing race voteclose. - Track-scoped race placeholders:
%boatracing_track_race_running_<track>%,%boatracing_track_race_registering_<track>%, and%boatracing_track_race_status_<track>%now resolve against the requested track session.
Fixed
- Selected boat variant persistence on spawn: race boats now re-apply the selected boat/raft variant right after spawn and on delayed retries, fixing cases where a chosen variant (for example
DARK_OAK) appeared as defaultOAK. - No dismount during countdown/race: racers can no longer manually exit boats/rafts during the 5-light countdown or while the race is running.
- Vote-open UX prompt: map-vote start now includes a clickable chat action to open vote UI (
/boatracing race voteui) instead of only a typed command hint. - Reward command parsing compatibility: reward distribution now supports both
commands(list) and legacycommand(single string), with safer fallback behavior for missing per-position keys (including position1).
Docs
- Track placeholder docs: README now documents track-scoped placeholders, compatibility aliases, and per-track session evaluation behavior.
- Race/map-vote docs: README now includes the new map vote commands (including
voteui) and multi-track race behavior notes. - QA additions for 1.1.3: CHECKLIST now includes explicit validation steps for track-scoped placeholders and selected boat variant spawn reliability.
- Rewards schema guidance: README/CHECKLIST now document reward command compatibility and recommend explicit
commands: []in each position block.
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:Vb0gvIIJ:eoC2qvJz"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Vb0gvIIJ:eoC2qvJz"
}

