Links
Tags
Creators
Details
All versions
Added -
2.0.6
Release
Fake Player Plugin 2.0 (FPP) 2.0.62 months ago 2,517
Compatibility
Minecraft: Java Edition
26.2
26.1.x
1.21.x
Platforms
BungeeCord
Folia
Paper
Purpur
Velocity
Changes
Added - /fpp spawn --location
- Admins (
fpp.spawn) can now spawn a bot at an arbitrary spot instead of only their own location:/fpp spawn --location <x> <y> <z> <world>, combinable with--name. User-tier spawns (fpp.spawn.user) are unaffected and still always spawn at the sender's own location. Tab-completes coordinates and world names.
Improved - Left/Right-Click Overhaul
- Auto tool-switch: before mining a block,
/fpp left-clicknow auto-equips the best available tool (highest tier of the right category - pickaxe/axe/shovel/hoe) already in the bot's inventory, the way a competent player would. Toggle vialeft-click.auto-tool-switchinconfig.yml(default on). Reuses the same tool-selection logic/fpp find's auto-mining already relied on, instead of a second copy of it. - Off-hand fallback for right-click: a bot's right-click now tries the main hand first and, only if that action had no effect, retries with the off-hand item - mirroring the vanilla client's own hand-loop exactly. Bots carrying a shield or food off-hand can now actually use it; previously the off-hand was never touched by right-click at all.
- Fixed: a bare
/fpp right-click <bot>(no--once/--repeat/--holdflag) skipped the mode-specific permission check entirely - a player holding onlyfpp.right-click.stopcould still start a default click. Now always gated on the resolved mode's permission, matchingleft-click. - Fixed:
/fpp right-click's task-resume path silently did nothing if its cached aim state was missing (e.g. after certain restart races) - the task stayed registered but never actually ran. It now rebuilds a fresh aim from the bot's own view and resumes normally, matchingleft-click. - Internal:
LeftClickCommand/RightClickCommandnow share one base class for aim geometry, stand-location search, and the stop/cleanup/save-restore lifecycle instead of two nearly-identical ~1000-line copies; the three parallelONCE/REPEAT/HOLD/STOPmode enums collapsed into one.
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:oioBwOz4:F7K0ySgp"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:oioBwOz4:F7K0ySgp"
}

