Links
Tags
Creators
Details
Licensed LGPL-3.0-only
Published 3 years ago
Updated 8 hours ago
All versions
1.4.8-beta
Beta
Star Wars: Blood & Beskar 1.4.8-beta2 days ago 42
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
Added:
- Craftable K79-S80 Imperial Troop Transport with six seats, 400 hull health, separate driver and gunner controls, and a rotating twin-blaster turret.
- Walkable transport interior with animated side doors and rear hatch. Press H while seated to toggle doors; Sneak to stand up and crouch through exits.
- K79-S80 wrench repairs and packing that preserves hull damage and weapon heat.
- Imperial Tank Pilots and Tank Commanders, with spawn eggs, craftable Pilot armor and a Commander chestplate variant.
- Three-second Hoth, Nevarro and Tatooine startup cinematic with a custom Blood & Beskar title screen, atmospheric effects and flyby audio.
- Escape-to-skip and a client option to disable the startup presentation. Zero Panorama Scroll Speed provides a still background and immediate menu.
Changed:
- Imperial raid waves now arrive aboard a K79-S80 with six troops. Four infantry deploy in two pairs before the driver and gunner continue fighting.
- Imperial raids can now attack non-Imperial Tatooine outposts.
- NPC transport and AT-RT crews prioritize visible hostile occupied vehicles and aim at their hulls.
- Raid infantry advance closer to defenders before settling into ranged combat.
- Updated Imperial Army fatigues and Sergeant armor textures.
Fixed:
- Invisible collision barriers around angled vehicle surfaces, affecting movement, turning, placement and walking around or inside vehicles.
- False vehicle impacts and pushing in empty spaces around their models.
- Raid infantry getting stuck behind vehicles or attempting to shoot through obstructing hulls.
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:Zc2XjaZY"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:QBIRprUu:Zc2XjaZY"
}

