Tags
Creators
Details
All versions
1.0.4
Release
BoatRacing 1.0.4last year 43
Compatibility
Minecraft: Java Edition
1.21–1.21.8
Platforms
Paper
Purpur
Changes
What’s new (1.0.4)
- Team-specific pit areas: new unified command
/boatracing setup setpit [team]sets the default pit when no team is provided, or the pit for a specific team when a team name is given. Tab‑completion suggests team names. - Mandatory pitstops: new
racing.mandatory-pitstopsconfig (default 0). When > 0, racers must complete at least that many pit exits before they are allowed to finish; pitstops are counted on exiting the pit area and persist for the whole race. - Wizard: Pit step updated to mention default pit vs per‑team pits and to guide the flow with clickable tips.
- Config updates: on plugin updates/reloads, new
config.ymlkeys are merged into your existing file without overwriting your changes. - Boat type: racers are mounted in their selected boat/raft wood variant (including chest variants) instead of always OAK; works across API versions with a safe fallback.
- Permissions: players can use
join,leave, andstatusby default; onlyopen|start|force|stopremain admin‑only. Removed extra runtime checks that could block players with permissive defaults. - Boats: spawned boats now respect the player’s selected wood type robustly across API versions; falls back to OAK if the enum value is not available.
- Per‑player start slots and grid ordering: new setup commands
/boatracing setup setpos <player> <slot|auto>and/boatracing setup clearpos <player>. On race start, players bound to a slot are placed there first; remaining racers are ordered by their best recorded race time on that track (fastest first), and racers without a time are placed last. - Setup show: now also displays the presence of team‑specific pits and the number of custom start positions configured.
- Wizard (Starts): shows optional buttons for per‑player custom slots — setpos/clearpos/auto — and displays the number of custom slots configured.
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:VvAVupZs"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Vb0gvIIJ:VvAVupZs"
}

