MultiMUD QuestEngine

MultiMUD QuestEngine was the system that ran automated quests in MultiMUD, a free text-based multiplayer game (a MUD, or Multi-User Dungeon). MultiMUD was a CircleMUD derivative hosted in Freiburg, Germany, and was opened to the public in May 1995. The game’s own advertising credited it with “intelligent, questengine steered mobiles”, meaning computer-controlled characters that could hand out tasks, check on progress and give rewards without a human game master present.

The engine was never released, documented for outside use or written up anywhere else, so very little about it can be checked. This page covers what the surviving sources show. It also says plainly what they do not show, and that includes whether the “QuestEngine” was a scripting language with its own syntax at all.

What the Sources Actually Say

Only three kinds of source describe the quest engine, all of them produced by or around the game itself:

A player review on The Mud Connector from August 2012 gives the player’s side. As well as quests and tournaments run by the immortals (staff), “there are also a number of them already programmed into the MUD. Roam the area and find mobs talking to you asking for your help with some problem or another. Prizes vary from experience points, to items, or quest points.”

The name “QuestEngine” itself appears only in that homepage line, spelled in lower case as “questengine”. No help file, manual or code listing for the engine has turned up.

History and Origins

MultiMUD’s history comes from an account written in July 2002 by its implementor, known in-game as Aragorn. The game’s website and in-game help files both published it. It says that in 1994 some players of R.o.M., a Circle-based MUD, disliked the direction of that game and decided to start their own. A bare CircleMUD with a few standard zones ran as a test server in the fall of 1994. The plan from the start was a world with “zones of all variations - from fantasy/medieval to sci-fi”. The MUD’s hometown, Freyburg, was modelled loosely on Freiburg, where the server was located.

The game opened to the public in May 1995. The Mud Connector gives the same creation date, May 1995, and lists the codebase as a “CircleMUD 3.0bpl8 derivative”. CircleMUD’s own release history dates 3.00 beta patchlevel 8 to 23 May 1995, which fits the opening date.

According to the 2002 history, 1995 to 1997 went mostly into building zones, and code work became more important after that. Several immortals are named as coders over the years, and two, Roy and Nork, are credited with “a lot of work into questing”. The history does not say whether that meant writing the quest engine or writing quests for it. The game’s in-game credits list coders by character name and real name, but none is credited with the quest engine.

That leaves the engine’s start date open. The catalog record says “1990s”, which is possible: the game was being actively developed through the late 1990s. But the earliest dated mention of a quest engine is the October 2003 homepage capture, and nothing earlier confirms it.

How It Appears to Have Worked

Built on CircleMUD’s special procedures

MultiMUD’s help files describe autoquests as special procedures carried by mobs, rooms and objects. That is CircleMUD’s own term. In CircleMUD and its maintained continuation, tbaMUD, a special procedure is a C function attached to a mobile, object or room. The tbaMUD coding manual says that in the standard code they “are defined and assigned at compile time and cannot be changed or reassigned during runtime”. Each procedure is called on every game heartbeat, on every combat round and before every command a player types nearby, so it can respond to what players do.

Here is a stock special procedure from the tbaMUD source, dump, which destroys anything dropped in a room and pays the player a small reward. It is CircleMUD-lineage code, not MultiMUD’s, and is shown only to illustrate the mechanism MultiMUD’s help files name:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17

SPECIAL(dump)
{
  struct obj_data *k;
  int value = 0;

  for (k = world[IN_ROOM(ch)].contents; k; k = world[IN_ROOM(ch)].contents) {
    act("$p vanishes in a puff of smoke!", FALSE, 0, k, 0, TO_ROOM);
    extract_obj(k);
  }

  if (!CMD_IS("drop"))
    return (FALSE);

  do_drop(ch, argument, cmd, SCMD_DROP);
  /* ... award experience or gold for the dropped items ... */
  return (TRUE);
}

Whether MultiMUD’s quest engine was a set of hand-written C procedures like this, a general C framework that quest designers filled in, or an interpreter for a separate quest-description language cannot be told from the surviving sources. The catalog classifies it as a scripting language, but no example of a QuestEngine script has been found.

What players could see

The help files describe these behaviours, all of which the engine either drove or worked alongside:

• Autoquests: quests run by procedures on mobs, rooms and objects. They could be limited by level, alignment and other conditions, and “may not be triggered all the time”. The help file points to the actor and Rusty in Freyburg as quest-givers, and to the beggars and the Avatar plate in the Cathedral as other procedures at work.
• Mobask: a system that lets certain mobs answer players’ questions. The examples given are the master of the guards, the smuggler, Yoda and certain shopkeepers.
• Quest items: rewards from quests and autoquests, or bought with quest points in the quest shop. They can only be worn or junked by their owner and cannot be sold.
• Missions: from the homepage, “every 10 levels you may choose to fullfill a mission for the Gods”.

The help files do not say which of these the “questengine” covers and which are separate systems.

The Game Around It

The engine only makes sense as part of MultiMUD, which advertised itself as:

• about 10,000 rooms in some 130 zones, ranging “from Jurassic over Medieval to Science Fiction”;
• 7 major races (each with its own hometown and race channel) and 10 minor races, including vampires;
• a 60-level system with a remort system into special classes (the 2003 homepage says “16-class”, and the later homepage says 20 classes);
• clans and followings of in-game deities, built on what the site calls “a very flexible entity system”;
• live quests run by immortals alongside the automated ones.

The site’s “Freyburg Tourist Information” and “Mos Eisley Tourist Information” were in-game credits for the fantasy and science-fiction zones. Along with mobs like Yoda, they show a world that mixed borrowed settings, such as Star Wars’ Mos Eisley, with areas original to the game.

Current Status

The MultiMUD website was still being served when it was archived in March 2025. It listed the game at multimud.net port 4242, and its newest news item was an Easter event dated 30 March 2021. Archive requests from November 2025 onward get HTTP 502 errors. A connection attempt to port 4242 on 25 October 2026 was not answered. A single failed attempt does not prove the game is gone, but there is no sign of recent activity.

Because the quest engine was part of MultiMUD’s private server code and was never published, it has no independent existence. If the game has closed for good, the engine survives only in the archived pages quoted above.

Why It Matters

MultiMUD QuestEngine is a small but typical piece of 1990s MUD history. CircleMUD and the other DikuMUD descendants gave hobbyist teams a working game server for free, and the teams then competed on what they built on top of it. Automated quests were one of the features games used to stand out from the stock code: computer-controlled characters that talked to players, set them tasks and paid them, so the world still had stories when no staff were online.

Most of these systems were never released or written up, and they ended up like this one: a name in a game’s advertising, a few help-file paragraphs and players’ memories. The catalog keeps the name. What the engine actually was will remain unknown unless the source code or a builder’s manual turns up.