Iron Realms Entertainment

A comprehensive reference on Iron Realms Entertainment (IRE) and its MUDs, with particular focus on Achaea, Dreams of Divine Lands. Covers business model innovation, game design, technical protocols, and lessons applicable to building an Urbit MUD.

1. IRE Business Model: Inventing Microtransactions

History

Matt Mihaly founded Iron Realms Entertainment (originally Achaea LLC) in 1996, launching Achaea in September 1997. He studied political science at Cornell, discovered MUDs through BatMUD and Avalon, and after an unsatisfying stint as a stockbroker decided to commercialize MUD development. The company was renamed from Achaea LLC to Iron Realms Entertainment in 2001 after the release of Aetolia. Jeremy Saunders serves as president. (Wikipedia: IRE, Wikipedia: Matt Mihaly)

The Problem

Achaea launched the same month as Ultima Online, into an industry that was abandoning hourly billing. AOL’s shift to flat-rate pricing in 1996 made players hostile to subscription fees for text games. Mihaly needed a new revenue model. (50 Years of Text Games: Achaea)

The Innovation: Virtual Asset Sales

In 1997, Mihaly held in-game auctions for virtual weapons and armor in Achaea – the first business to use what is now called the microtransaction or virtual asset sales (VAS) model. When those auctions generated $5,000 during financially lean periods, he established a persistent web storefront. Players initially mailed paper checks to his San Francisco address. (PCGamesN, 50 Years of Text Games)

In 1999, he created the first hard-to-soft currency exchange in an online game, allowing players to trade purchased credits for earned in-game gold. (Wikipedia: Matt Mihaly)

The Credits System

IRE’s monetization centers on a dual-currency system:

• Gold – earned in-game through questing, bashing (hunting), crafting, and trading. The free currency.
• Credits – the premium currency. Can be purchased with real money or bought from other players using gold on an in-game credit market/exchange.

Credits are used for:

• Lessons – learning and advancing class skills and general abilities
• Artifacts – powerful items with permanent stat bonuses, special abilities, or quality-of-life features
• Customizations – custom item descriptions, housing additions, pets
• Trade skill permits – additional crafting specializations beyond the two free ones
• Class changes – multiclassing requires credit investment

The IGDA noted that Achaea reported “substantially higher average revenue per customer than the usual subscription prices.” (Wikipedia: Achaea)

Why It Works

• No paywall for core gameplay – the game is completely free to play. Many players roleplay for years without spending money.
• Player-to-player credit trading – creates a market where free players can acquire credits through in-game effort, while paying players get gold.
• Artifacts are powerful but not strictly required – they provide advantages, not gates.
• Social pressure is organic – players want to be competitive or prominent, driving voluntary spending.
• A 2020 exposé revealed some players spending over $10,000, but supporters note that MUDs aren’t about “winning” and many free accounts thrive. (50 Years of Text Games)

This model predates mobile gaming microtransactions by over a decade.

2. Achaea, Dreams of Divine Lands

Overview

• Launch: September 9, 1997
• Creator: Matt Mihaly (lead designer and producer)
• Engine: Rapture Runtime Environment (proprietary, C/C++ with Lua scripting)
• Genre: High fantasy MUD
• Scale: Over 20,000 rooms across the continent of Sapience, surrounding oceans, islands, and alternate planes
• Player base: ~1,000 regular players as of 2020
• Setting: Sword and sorcery fantasy with deep lore, active gods, and player-driven politics

(Wikipedia: Achaea, Achaea.com)

The Rapture Engine

The engine went through three major iterations:

1. Hourglass – initial implementation
2. Vortex – licensed from Avalon’s creator; IRE eventually bought Vortex from its developer and revoked licenses to the other two Avalon-clone MUDs using it
3. Rapture – the current proprietary engine, written in C/C++ with Lua scripting

Rapture powers all IRE MUDs (with per-game modifications). It was also adapted for a UN-affiliated interactive chat system for the 7th Annual World Summit of Young Entrepreneurs. (Wikipedia: IRE, 50 Years of Text Games)

Class System

Achaea has 21 classes, each with three skill trees containing 20-50 abilities each, giving most classes close to or more than 100 class-specific abilities on top of general skills:

Players can multiclass (for credits), and each class plays fundamentally differently in combat. (Achaea Classes, AchaeaWiki)

Combat System

Achaea’s PvP combat is widely considered one of the deepest in any MUD (or MMO). It is affliction-based rather than primarily damage-based.

Core Mechanics

Balance and Equilibrium:

• Balance – physical readiness; consumed by physical attacks, recovers in ~4-5 seconds
• Equilibrium – mental readiness; consumed by magical abilities
• Most offensive abilities require one or both; you cannot act while recovering
• This creates a turn-like cadence within real-time combat

(AchaeaWiki: Combat Overview)

The Affliction System

There are approximately 50-75 distinct afflictions in the game. Combat revolves around inflicting afflictions faster than the opponent can cure them, then exploiting the resulting vulnerabilities.

Affliction categories and their cures:

(AchaeaWiki: Combat Overview, AchaeaWiki: Afflictions)

Venoms

The Serpent class can bite every ~2 seconds with one of 26+ venoms, each causing a different affliction. Higher-level Serpents can milk venoms into vials, which weapon-using classes (Knights, Infernals, etc.) can apply to their blades to deliver afflictions on hit. Key venoms include:

• Curare – paralysis
• Xentio – clumsiness
• Slike – anorexia
• Kalmia – asthma
• Gecko – slickness
• Aconite – stupidity
• Darkshade – sensitivity

(AchaeaWiki: Venom Skill)

Affliction Locks

A “lock” occurs when a combination of afflictions prevents the victim from curing any of them. The key lock afflictions are:

• Anorexia – cannot eat herbs
• Asthma – cannot smoke pipes
• Slickness – cannot apply salves
• Paralysis – cannot use tree tattoo or fitness

Lock types:

• Soft lock – two of the above; the victim can still cure through the remaining channels but is severely constrained
• Hard lock – three of the above; extremely difficult to escape
• True lock – all four present simultaneously; the victim cannot cure through any normal channel and is effectively helpless, leading to death via damage or instakill abilities

The strategic depth comes from curing priorities: your curing system must decide which affliction to eat/smoke/apply first when multiple are present, and attackers exploit predictable priority orders. (AchaeaWiki: Curing, Achaea Forums)

Kill Conditions

• Damage kills – reduce HP to zero through raw damage
• Affliction-to-damage – stack afflictions that prevent healing, then burst damage
• Instakill abilities – many classes have a “finisher” that requires specific setup (e.g., Occultist Vivisect, certain Monk combos)
• Lock-to-kill – achieve a true lock, then the victim is helpless

Server-Side Curing

IRE introduced server-side auto-curing (pioneered in Aetolia, later ported to Achaea). The system automatically cures afflictions for you, tracks all afflictions even when paused, and can detect and attempt to break locks. This lowered the barrier to entry for combat, which previously required extensive client-side scripting. (Svof Documentation)

Political System

City-States

Six player-run city-states, each with distinct culture, philosophy, and Divine patrons:

Each city has ten Ministries (War, Trade, Maritime Affairs, etc.) run by players. Cities collect taxes, manage armies, set laws, declare war, and forge alliances. (Achaea City-States)

Divine (Gods)

Gods are roleplayed by admin staff and are deeply integrated into gameplay:

• Gods interact directly with players in real-time
• Players can join a god’s Divine Order, rise in ranks, and build shrines
• Shrines channel divine powers for worshippers
• Gods gain power based on active worshiper count
• Gods drive major world events and storylines
• Examples: Aurora (Light), Aegis (War), Deucalion (Righteous Fire)

(Achaea Game Features, 50 Years of Text Games)

Houses

Player-run organizations within cities (formerly called guilds). Each has its own leadership structure, requirements, culture, and internal politics.

Economy

Earning gold:

• Questing – the primary gold source for most players
• Bashing (hunting NPCs) – more lucrative at high levels
• Crafting and selling – player-run shops in cities
• Trading – buying/selling commodities, credit market speculation
• Fishing, diving, ship trading – maritime economy
• Sea monsters – high-risk, high-reward

Trade skills (14 total): Armoursmithing, Weaponsmithing, Tailoring, Cooking, Jewellery, Furnishing, Gathering, Harvesting, Inkmilling, Remedies, Synthesis, Toxicology, Augmentation, Conjuration

Players get two free trade skills (at levels 30 and 50); additional permits cost 50 credits each. All crafted items go through an approval system for description quality. (AchaeaWiki: Trade Skills)

Housing

• Fully player-designed: unlimited rooms (materials required), custom descriptions, hidden exits, doors, locks
• Servants can be hired and scripted with behavior
• Furnishable with player-crafted items
• Houses can be built in city-states or in the wilderness

Ships and Seafaring

Three ship classes serving different playstyles:

• Windcutter – small, fast; exploration and island-hopping
• Thalassian Seastrider – trading vessel with large cargo hold
• War Galley – slow, massive, bristling with weapons

Activities: piracy, sea monster hunting, port-to-port trade routes, treasure diving, deep-sea fishing, island exploration. Ship-to-ship combat is a full subsystem with crew management, ammunition types, and naval tactics. (Achaea Game Features)

Progression

• Level 1-99 via experience from bashing and questing
• At level 99, characters can achieve Dragonhood – transforming into one of six dragon types
• Experience can also be gained non-violently in some IRE games (Lusternia allows full pacifist leveling)

Other Notable Systems

• Mining – player-operated mining businesses with Legion-based defense mechanics
• Libraries – player-written books stored in in-game libraries
• Heraldry – custom coat of arms design
• Marriage and family – formal relationships with other players
• Bardic and artistic contests – regular competitions judged by admin, with credit prizes
• Customizable cooking and tailoring – player creativity within game systems
• Bookmaking – run a betting operation

3. ATCP and GMCP: Client Protocols

ATCP (Achaea Telnet Client Protocol)

Developed by Iron Realms to send out-of-band data between server and client without cluttering the text stream.

Technical details:

• Uses Telnet option code 200 (arbitrary, not standards-endorsed)
• Negotiation: server sends IAC DO ATCP (255 253 200), client responds IAC WILL ATCP (255 251 200)
• Message framing: IAC SB ATCP <message text> IAC SE (255 250 200 … 255 240)
• Content format is plain text; format is implementation-defined
• Supported by cMUD (2008), Mudlet, Aardwolf, and Avalon

(Rapture Manual: ATCP)

GMCP (Generic MUD Communication Protocol)

ATCP evolved into GMCP, which added structured JSON data and standardized namespaces.

Technical details:

• Uses Telnet option code 201
• Negotiation: server sends IAC WILL GMCP, client responds IAC DO GMCP
• Message format: IAC SB GMCP <Package.SubPackage.Command> <JSON data> IAC SE
• Data encoding: JSON (UTF-8), case-insensitive module names, case-sensitive JSON keys
• Bidirectional: both client and server can send messages

Evolution: ATCP (code 200, 2008) -> ATCP2 (code 201, 2010 proposal) -> renamed GMCP after mudstandards.org community initiative. The rename reflected the intent to make it a cross-MUD standard rather than an IRE-proprietary protocol.

(TinTin++ GMCP Reference, Rapture Manual: GMCP)

GMCP Namespaces (IRE Implementation)

(Nexus GMCP Documentation)

4. The Nexus Client

IRE’s proprietary web-based MUD client, playable directly in a browser with no installation required.

Key Features

• Cross-platform: Windows, Mac, Linux, iOS, Android; also available as native mobile apps
• Cloud-synced settings: Macros, triggers, and aliases saved server-side, accessible from any device
• Visual UI: Health/mana bars, affliction icons, balance/equilibrium indicators, graphical character creation
• Windowed layout: Separate panes for main output, inventory, communication, graphical map; fully resizable and customizable
• Scripting: Full JavaScript support with GMCP API access for advanced automation; also offers a simplified no-code trigger builder
• Package sharing: Export/import trigger and alias packages between characters and players
• Keybinding and aliases: Configurable with zero programming knowledge

Significance

Nexus dramatically lowered the barrier to entry for MUDs. Previously, players needed to install a desktop client (Mudlet, CMUD, MUSHclient), learn its scripting language, and configure it. Nexus lets a new player go from clicking a link to playing in seconds, with a modern UI that doesn’t intimidate non-technical users.

(Iron Realms: Nexus Client, Nexus Documentation, Nexus Client Overview)

5. What Makes IRE MUDs Distinctive

Deep Roleplay + Mechanical Complexity

IRE games combine narrative depth with systems that would be complex even in a graphical MMO. The combat alone has a skill ceiling comparable to fighting games, but it exists alongside crafting, politics, religion, economy, and exploration systems that are each deep enough to be someone’s entire gameplay focus. (50 Years of Text Games)

Player-Driven Politics

Achaea’s political systems are not decorative. City leaders make real decisions about taxes, laws, war declarations, and alliances. Players can be exiled, cities can be raided, and political coups happen. Richard Bartle cited Achaea in Designing Virtual Worlds as an example of political game design. (Wikipedia: Achaea)

Living World Events

Admin-run gods drive world events in real-time, with outcomes determined by player actions. Entire pantheons have shifted, cities have been destroyed and rebuilt, and the game’s history is genuinely shaped by its players over 25+ years. The ease of content creation in text (no art pipeline) means events can be reactive and spontaneous. (IRE, 50 Years of Text Games)

Persistence and Consequence

Actions have permanent consequences. Reputation, political standing, organizational membership, rivalries – these persist for years. The social fabric is the game.

Text as Advantage

Mihaly argued that text avoids “the plodding literalism of 3D graphics,” offering unlimited creative possibility. Unlike graphical games facing constant obsolescence cycles, prose-based worlds remain timeless. A room description can evoke a cathedral or an alien landscape with equal ease and zero art budget. (50 Years of Text Games)

The Other IRE Games

(Wikipedia: IRE, Starmourn)

6. Lessons for Our Urbit MUD Project

Worth Borrowing

1. Affliction-based combat over pure damage. IRE’s combat is compelling because it’s strategic, not just arithmetic. Stacking afflictions, managing cure priorities, and achieving locks creates decision trees deeper than “hit harder.” An Urbit MUD should aim for this kind of tactical depth rather than DPS races.

2. Balance/Equilibrium as a pacing mechanism. The balance/eq system creates natural turn-like cadence in real-time combat without feeling turn-based. It prevents spam, rewards timing, and makes every action meaningful. This maps well to Urbit’s event-driven architecture – each action is a poke, each recovery is a timer.

3. Player-driven politics with real stakes. Achaea’s city-states prove that players will invest deeply in governance when it has mechanical teeth. Taxes, laws, war, exile – these create emergent narrative. On Urbit, where identity is sovereign and persistent (ship IDs), political systems could be even more meaningful.

4. Dual-currency economy. The gold/credits split is elegant: one currency circulates freely in-game, the other bridges to real-world value. On Urbit, this maps naturally to in-game currency + a crypto token or Urbit-native asset. The credit exchange mechanic (players trading premium currency for in-game currency) creates a self-regulating economy.

5. GMCP-style structured data protocol. GMCP’s approach – JSON-encoded out-of-band data organized into namespaces – is directly applicable. An Urbit MUD client needs structured state updates (room info, combat status, inventory) separate from narrative text. GMCP’s namespace design is a proven schema to adapt.

6. Server-side curing / automation assistance. Lowering the scripting barrier was crucial for IRE’s player retention. Building curing logic and basic automation into the server (or providing it as a standard library) rather than requiring every player to write their own scripts.

7. Living events run by admin-as-gods. The “Divine” model – where admins roleplay as in-world gods with narrative authority – is powerful for world-building. On Urbit, ship owners or designated operators could fill this role, with their authority encoded in the app’s permissions.

8. Crafting with player creativity. IRE’s crafting system lets players write custom item descriptions (subject to approval). This produces a world that feels handmade. On Urbit, with its ethos of personal expression, this is a natural fit.

Worth Adapting or Rethinking

9. Monetization without pay-to-win feel. IRE’s credit system works but generates criticism. For an Urbit MUD, consider: can Urbit’s native identity and address space provide monetization without a premium currency? Land claims tied to ship IDs? Reputation as currency?

10. The text-as-advantage philosophy. Mihaly was right that text ages better than graphics. On Urbit, where the platform favors lightweight apps, a text MUD is architecturally native in a way a graphical game would never be.

11. Decentralized architecture for world persistence. IRE runs centralized servers. An Urbit MUD could distribute world state across ships, making the world inherently persistent, censorship-resistant, and owned by its players – something IRE’s model aspires to culturally but can’t achieve technically.

12. Player-written content as world-building. IRE’s libraries of player-written books, custom room descriptions, and crafted items make the world feel alive. On Urbit, where every user has a ship with storage, player content could be natively hosted and cross-referenced.

What to Avoid

• Artifact power creep – IRE’s most common criticism is that artifact purchases create meaningful combat advantages. Design artifacts/enhancements to be horizontal (more options) not vertical (more power).
• Complexity cliff – Achaea’s combat is brilliant but has a brutal learning curve. Build graduated complexity with good defaults (server-side curing equivalent from day one).
• Admin dependency for events – While Divine-run events are great, the game shouldn’t go dormant when admins aren’t active. Build systems that generate emergent content (faction conflicts, resource competition, procedural events).

Sources

• Wikipedia: Iron Realms Entertainment
• Wikipedia: Achaea, Dreams of Divine Lands
• Wikipedia: Matt Mihaly
• 50 Years of Text Games: 1997 - Achaea – Aaron A. Reed’s excellent deep dive
• PCGamesN: Meet the man who invented microtransactions
• Iron Realms Entertainment
• Achaea.com
• Achaea City-States
• Achaea Game Features
• Achaea Classes
• AchaeaWiki: Combat Overview
• AchaeaWiki: Afflictions
• AchaeaWiki: Venom Skill
• AchaeaWiki: Curing
• AchaeaWiki: Trade Skills
• Rapture Manual: ATCP
• Rapture Manual: GMCP
• Nexus GMCP Documentation
• TinTin++ GMCP Reference
• Iron Realms: Nexus Client
• Nexus Client Documentation
• Muds Wiki: Iron Realms
• Muds Wiki: Achaea
• Svof Curing System Documentation
• Virtual Economy Research Network: Genesis of Virtual Goods
• Starmourn
• Achaea Forums