Links
Tags
Creators
Details
Licensed LGPL-3.0-only
Published 3 years ago
Updated 8 hours ago
All versions
1.4.0-beta
Beta
Star Wars: Blood & Beskar 1.4.0-beta6 days ago 41
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
Added:
- Podracer Front upgrade for all 74-Z and T85 bikes, compatible with either booster.
- Podracer driving: forward applies thrust, releasing it coasts and recharges, and backward brakes before reversing slowly.
- Podracer Front grants 25% more boost capacity and uses 35% less charge while thrusting.
- Animated exhaust flames for boosters and Podracer Fronts, including workshop previews.
- Podracer control hints and an empty-reserve warning.
- Watto races now feature three to five opponents, with a 25% chance of two laps for 1.5× prize value.
- Race HUD now shows the current lap and actual racer count.
- Live search timer while Watto finds a course.
Changed:
- Increased standard bike cruising speeds to 27 blocks/s for the 74-Z and 32.4 for the T85, with faster sprint speeds.
- Smoothed bike acceleration, coasting and the transition from sprinting to cruising.
- Race opponents can use Podracer Fronts, manage thrust and recharge, and take clear inside lines through corners.
- Expanded course searches to try tighter loops, wider loops and connected detours; safe shorter circuits and sloped starting grids are now allowed.
- Completed race courses remain cached longer for repeat visits.
- Only last place or failure forfeits your bike; other finishers outside the top three keep it without a prize.
- Enlarged workshop previews and added speed and charge-capacity tooltips; upgrade options appear only when a bike is inserted.
Fixed:
- Vehicle Workshop interactions failing when clicking certain sections.
- NPC settlement protections incorrectly blocking Vehicle Workshop use.
- Race searches timing out while terrain was still arriving.
- Race routes using incorrect heights across dune crests.
- Reapplying forward input after coasting unnecessarily slowing the bike.
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:QBIRprUu:DdRUFPgO"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:QBIRprUu:DdRUFPgO"
}

