[Legacy] Pippi - User & Server Management - v3.9.14

[Legacy] Pippi – User & Server Management v3.9.14

Pippi is the Swiss army knife for Conan Exiles server admins: a custom chat system, kits, commands, announcements, warp points, MOTD, rule sets, dynamic ranks, and clan management all run through one central interface, so moderators don't need full admin access. Its built-in scripting language, Mushi, lets you build custom NPC encounters, dungeons, quests, and even animated scenes without touching any code. With over 640,000 subscribers, it's one of the most installed admin mods for the game. Load order matters on your server's modlist.txt: put Pippi near the top, since other mods hook into it. Every player needs to subscribe to the exact same version on Steam, and after a major update it's worth checking for a Pippi update before restarting, since outdated admin mods can block a clean boot.

Plan the rollout and operation

Pippi is useful when moderation, travel, kits, and custom role-play content should live in one interface. Grant each role only the permissions it needs rather than giving every helper full access. Run new warps, kits, and Mushi scripts with an ordinary test account first, checking cooldowns and destinations. Back up the Pippi configuration separately from the world afterward so rules and authored content can be restored without rolling back unrelated player progress.

For a safe rollout, back up the world and server configuration, record the current modlist.txt including order, and start a copy on the exact same game version. Review the boot log for missing packages, then join with a client using the same Workshop list. A useful smoke test covers joining, spawning, one core mod feature, saving, restarting, and joining again. After major game updates, delay the live update until the mod and its dependencies are explicitly compatible. Change only one part of the list per test run; otherwise a crash cannot be traced to a specific entry. Before removal, use a world copy to check for stored items, buildings, thralls, or configuration owned by the mod. Remove its Workshop entry from production only after the save loads cleanly without those assets. This keeps rollback and diagnosis manageable.