FluffOS vs Evennia: Choosing a MUD Engine

Evennia and FluffOS can both power text worlds, but they make very different promises. Evennia gives you Python and modern web-stack familiarity. FluffOS gives you the LPMud lineage: LPC, long-running mudlibs, and a model built around persistent rooms, objects, and living systems.

Important Icesus note: Icesus runs on the open-source FluffOS driver, but the Icesus game codebase is private and maintained by trusted contributors. This page compares engines; it is not claiming the Icesus mudlib is public.

The short version

If you want...	Prefer...	Why
Python, Django-style development, web integration	Evennia	It is built for Python developers and modern tooling.
Classic LPMud architecture and LPC	FluffOS	It continues a long MUD tradition with object-oriented room/item/player code.
A brand-new public hobby project	Evennia	Python lowers the barrier for new contributors.
To contribute inside a mature production text world	Icesus / FluffOS	You can learn from decades of solved problems instead of starting from an empty map.

What Evennia buys you

Evennia is attractive because it starts where many modern developers already are: Python. If your team knows Python, wants web integration, likes familiar package management, or wants to build a MUD-like project from scratch, Evennia is a serious choice.

Python is easier to recruit for than LPC.
The project has clear public documentation and examples.
It fits developers who want to own the whole stack.
It is a good way to learn text-world architecture without first learning LPMud history.

If your goal is "I want to build my own MUD in Python," start by reading the Evennia documentation.

What FluffOS buys you

FluffOS is a modern driver in the LPMud family. Its language, LPC, was built for persistent object worlds: rooms, exits, items, NPCs, spells, guilds, and game systems that live together on a running server.

LPC maps naturally onto MUD objects and game behavior.
The architecture has been battle-tested by long-running worlds.
It rewards contributors who like reading existing systems and extending them carefully.
It is less fashionable than Python, but it is very close to the problem domain.

Why Icesus chose FluffOS

Icesus is not choosing a stack in 2026. It has been compounding on LPMud/FluffOS ideas for decades. That changes the question. The value is not only the engine; it is the world built on top: rooms, races, guilds, quests, combat systems, lore, tools, and the institutional memory of people who know why things work the way they do.

For Icesus, FluffOS is not nostalgia. It is continuity.

Which should you pick?

Pick Evennia if...

You want Python.
You are starting a new public framework-based project.
You want modern web-stack familiarity more than LPMud lineage.
You want to teach beginners using a language they may already know.

Pick FluffOS if...

You specifically want the LPMud/LPC model.
You like object-driven game code.
You want to understand how long-running MUDs structure rooms, items, NPCs, and systems.
You are interested in contributing to an existing FluffOS world like Icesus.

The contributor path

If your real itch is not "own a server" but "build meaningful game content," you may not need to start a new MUD. Icesus already has players, history, areas, maps, guilds, and a working production environment. Contributors can help with areas, quests, lore, accessibility, documentation, and eventually trusted wizard work.

Want to build inside an existing FluffOS world?

Contribute to Icesus