Links
Tags
Creators
Details
All versions
1.0.24.1
Release
Abdik's Mod 1.0.24.1last month 8
Compatibility
Minecraft: Java Edition
26.1.2
Platform
Fabric
Supported environments
Client-side
Changes
v1.0.24.1
Fixes:
- Party Requirements now looks everywhere you actually keep gear - the wardrobe most of all. It only ever read what someone was wearing or carrying, which on a real account came to 22 items out of 149: a wardrobe full of armour, storage backpacks, the ender chest and the personal vault may as well not have existed. That's the whole Terror Boots complaint - the set was sitting in a wardrobe slot, so the mod said they didn't own it. All of it is read now.
- Kuudra armour stars are counted properly. Stars past the fifth were being read as dungeon master stars, so a fully starred Infernal piece came back as a five-star one and a requirement for more than five could never pass. Kuudra armour takes ten stars a tier and fifteen at Infernal, and the star box accepts that now.
Security:
- The relay was pen-tested end to end and four real holes were closed. An identity string now has to be a real uuid - a padded one signed exactly like the genuine article, which meant one valid account could pose as unlimited different players on the presence and player-size rosters. The shared key's daily allowance is now counted against the connection it came from, not against a name the caller types, so it can't be reset by relabelling the request or handed the owner's exemption by simply claiming the owner's uuid. Oversized chat frames and absurd Auction House searches are refused instead of being relayed or scanned. And rows that were supposed to clear themselves never did - they're cleaned up for real now.
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:jIGENrL5:pCVPG89z"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:jIGENrL5:pCVPG89z"
}

