1.3.4
Compatibility
Required content
Changes
ironically, i am at my most burnt out when I have the most time to work on the mod.
Changes
-
Fixed a bug where the stored chestplate would be lost on death if keepInventory was enabled in the current world
-
Fixed a bug where using the Consecrator on Bloody Ice would generate infection points for free
- This is presumeably an SRP bug that wormed its way over
-
Fixed a bug where the Undying enchantment would cause massive amounts of lag due to client item spawning
-
Leer can no longer be used on armor stands, no fun allowed
-
Remodeled/retextured the Vagrant, at the moment only Tier 0 is finished.
- As time goes by, I will add each tier individually
- The goal is for them to all look very different by the end
- Ironically, this update actually reduced the tier variance, they all look the same now! Nothing I can do for now besides continue working.
- Then again, the original model barely changed anyway, not much was lost here
-
Since the remodel is a WIP, an option is provided in the client settings to use the old one.
-
New Item: Ghastly Bandage
- Intended for the early game, crafted from Rupter Viscera and a Blood Lotus
- Heals a parasite for 5 HP on use. Also works on other vagrants!
-
The /toggleparasite command now supports forcing the target into the hidden state when used via the shouldConceal optional argument.
- This only works if you are using the command with a name provided (or %s to refer to yourself)
-
Fixed the /toggleparasite command not giving back the player's stored chestplate, provided one exists
-
The /dendritus command now works similarly to the /srpcbounty command, allowing removal and placement.
-
Replaced /setbiomass with /biomass <set|add|subtract>, also works as /biomass <player(s)> <set|add|subtract> for bulk operations.
-
Replaced /setkills with /parasitekills <set|add|subtract>, also works as /parasitekills <player(s)> <set|add|subtract> for bulk operations.
Config Changes
- Parasite Player Old Model - Whether Parasite Players use the old model as opposed to the new one introduced in 1.3.4.
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:JeRs1qZv:5g9MZddU"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:JeRs1qZv:5g9MZddU"
}

