Links
Tags
Creators
Details
1.10.0
Compatibility
Changes
- Bot i-frames (biggest new feature) Bots now get proper invincibility frames after they take a hit, like real players.
New system: ProtectionBotIframeSystems Detects VexBot fake players (vexbot.fakeplayer.bot.BotPlayer) Uses the existing combat.iframesTicks setting After a bot is hit, extra hits during that short window do not go through Works for both normal players and VexBot players via new mixins: ServerPlayerIframeMixin VexBotPlayerIframeMixin (optional, only if VexBot is installed) LivingEntityDamageAccessor (helps track last damage)
This is mainly so Farlands/Mafia bots don’t get shredded by fast hits. 2. New Practice config section A new config block called practice was added. It stores settings for:
Duels (on/off, default rounds, request timeout) Kits (editor, custom kits, enchant/attribute/trim/stack editing, totem stack limit) Parties Ranks Bot duels Map auto-size
Important: this version only adds the config. There is no new duel/kit/party system inside this JAR. It looks like setup for another plugin or a future update. 3. Small /pupg improvements The player-upgrade system was tweaked again:
New pending mainhand boost (MAINHAND_PENDING) Boosts can now apply when you attack an entity, not only from the command Messages and numbers were cleaned up a bit (damage %, armor reduction, durability save)
Behavior is still: mainhand boost + armor boost, owner-bound, armor boost turns off when you get hit. 4. Other small stuff
Version is now 1.10.0 Extra mixin file: protection-vexbot.mixins.json (loads only if VexBot exists) Config system grew so the new practice keys can be get/set Commands class barely changed
Short version:
1.10.0 is mostly bot i-frames (so bots don’t get combo’d unfairly) plus a new Practice config for duels/kits later. /pupg got a small upgrade so mainhand boosts can apply on hit.
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:hrdPSCxi:s8Jbr0ks"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:hrdPSCxi:s8Jbr0ks"
}

