Tags
Creators
Details
1.2.6
Compatibility
Changes
Illage and Spillage: Respillaged 1.2.6 Changelog
General Changes:
- Igniter's flamethrower glows more and more red the closer it is to overheating
- Igniter's flamethrower now emits smoke when close to overheating
- Igniter's torch now uses an emissive texture
- Igniter's fireballs and snowballs now actually look like they shoot out of the dispenser
- Added camera shake to Twittollager explosion
- Ragno can no longer take damage while Freakager is using anticheese attack
- Mobs not attacking bosses while their forcefields are up is now achieved using canAttack mixin (mobs won't target and untarget them constantly and is overall cleaner)
- Added Japanese localization
- Updated Chinese localization
- Updated Korean localization
- Whether or not an illager is a boss is now determined by an entity tag
- This means you can override it and add any other entities to the tag with a datapack like you would with a vanilla tag (the path is data/illageandspillage/tags/entity_types/illager_bosses.json)
- Entities that are considered bosses will be ignored by other bosses' forcefields and will have their name displayed on the raid bossbar (if the bossbar display is set to 3 in the config)
Bug Fixes:
- Fixed Igniters not being able to shoot fireballs at crazy Ragnos
- Fixed Hinder heal sound sometimes not working
- Fixed hay armor visual disappearing if the player dies or closes the world
- Fixed weird things with raiders attacking engineer machines and each other sometimes
- Fixed bossbars not disappearing if boss bar mode is set to 1 and the boss joins a raid
- Fixed Old Freakager and Old Magispeller being able to regain their forcefields after their fights have begun
NOTE: Due to the Igniter changes, any resource packs that change igniter's texture likely won't work anymore without some modifications
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:kLoMCc4b:ZSOHyVar"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:kLoMCc4b:ZSOHyVar"
}

