Fake Player Plugin (FPP)

v1.6.4 (2026-04-16)

NameTag Plugin Integration

• New soft-dependency on the NameTag plugin — fully optional, auto-detected at startup
• Nick-conflict guard — prevents spawning a bot whose --name matches a real player's current NameTag nickname (nametag-integration.block-nick-conflicts: true)
• Bot isolation — after each bot spawns, FPP removes it from NameTag's internal player cache to prevent NameTag from treating bots as real players (nametag-integration.bot-isolation: true)
• Sync-nick-as-rename — when a bot has a NameTag nick set (e.g. via /nick BotA Steve), FPP auto-triggers a full rename so the bot's actual MC name becomes the nick (nametag-integration.sync-nick-as-rename: false — opt-in)
• NameTag skin sync — bots inherit skins assigned via NameTag; SkinManager.getPreferredSkin() checks NameTag-assigned skins first
• New NameTagHelper utility class: nick reading, skin reading, cache isolation, formatting strip, nick-conflict checks
• New FakePlayer.nameTagNick field tracks the cached nick from NameTag
• New lang key spawn-name-taken-nick shown when a bot name conflicts with a real player's nick

Skin System Overhaul

• New SkinManager class — centralised skin lifecycle: resolve, apply, cache, fallback, NameTag priority
• Hardcoded 1000-player fallback skin pool — replaces the old skin.fallback-pool and skin.fallback-name config keys; bots with non-Mojang names always get a real-looking skin from the built-in pool
• DB skin cache — new fpp_skin_cache table with 7-day TTL and auto-cleanup; resolved skins cached to database to avoid repeated Mojang API lookups
• skin.mode default enforced as player for existing installs that had it disabled (v58→v59 migration)
• guaranteed-skin default enforced as true for existing installs (v58→v59 migration)
• skin.fallback-pool and skin.fallback-name config keys removed — now hardcoded in SkinManager (v59→v60 migration)
• Exposed via plugin.getSkinManager() — public API: resolveEffectiveSkin, applySkinByPlayerName, applySkinFromProfile, applyNameTagSkin, resetToDefaultSkin, preloadSkin, clearCache

Per-Bot Swim AI & Chunk Load Radius

• Each bot now has an individual swim AI toggle — override the global swim-ai.enabled per-bot without restarting
• Each bot now has an individual chunk load radius — -1 = follow global chunk-loading.radius, 0 = disable chunk loading for this bot, 1-N = fixed radius (capped at global max)
• Both fields are initialised from the global config at spawn, fully persisted across restarts (DB column + YAML key), and editable at runtime

BotSettingGui General Tab Expanded

• General tab now has 7 action slots: Frozen · Head-AI · Swim-AI (new) · Chunk-Load-Radius (new, numeric prompt) · Pick-Up-Items · Pick-Up-XP · Rename
• Chunk-load-radius uses a chat-input numeric prompt (same interaction model as /fpp settings numeric fields); type a number or -1 to reset to global

BotSettingGui PvP Tab

• PvP category now shows full coming-soon override previews: difficulty, combat-mode, critting, s-tapping, strafing, shielding, speed-buffs, jump-reset, random, gear, defensive-mode

DB Schema v14 → v15

• v14: fpp_active_bots gains swim_ai_enabled BOOLEAN DEFAULT 1, chunk_load_radius INT DEFAULT -1
• v15: new fpp_skin_cache table (skin name → texture/signature/source/cached_at) with expiry index
• Fully backward-compatible — existing rows receive safe defaults on schema upgrade

Config v53 → v60

• v53→v54: body.drop-items-on-despawn: false injected into existing installs
• v54→v55: shared global pathfinding tuning keys added
• v55→v56: nametag-integration section added (block-nick-conflicts, bot-isolation)
• v56→v57: nametag-integration.sync-nick-as-rename added
• v58→v59: skin.mode=player, guaranteed-skin=true, logging.debug.skin=true enforced for existing installs
• v59→v60: removed skin.fallback-pool and skin.fallback-name (hardcoded in SkinManager)