Immortal Realm

Expeditions: Charter-Based Group Content for 2-4 Players

Charter-based 2-4 player Expeditions on Immortal Realm — private regions, 90-min timer, and the Sunken Archives variant.

Expeditions are Immortal Realm's charter-based 2-4 player group content — defined dungeon-flavored quests where a small party forms a charter, enters a private region, works through shared objectives on a time limit, and earns rewards on completion. They're the small-group equivalent of the shard's other group-content surfaces, sized for the players who want coordinated party play with real stakes.

A note on "instanced" terminology — Expeditions are not instanced in the MMO sense (no per-party copy of the dungeon geometry). Each charter registers a private ExpeditionRegion over the same shared physical area; non-members of that charter are ejected on entry. In practice that means one party at a time per expedition variant — the first party to claim a charter holds the dungeon until they finish, fail, or time out. Two simultaneous parties on the same expedition would conflict at the boss room. On a small shard this is rarely an issue; the design implication is "first to charter wins."

This page covers how the framework works, what makes an expedition different from a convoy or a dungeon run, and what the Sunken Archives expedition (the first variant) looks like in practice.

What an Expedition Is

An Expedition is built from these parts:

  • A charter — a Blessed item issued by the expedition's lead NPC. The leader holds it; allies join the run by double-clicking it within 3 tiles. The charter is the handle that creates and tracks the run.
  • A definition — the expedition's template: title, description, objectives, region bounds, entrance point, time limit, member-count range.
  • A region — a private dungeon area gated by membership. Non-members who try to enter are auto-ejected back to the entrance.
  • Shared objectives — the goals the party works through together. Progress is shared across all members the moment any one of them completes an objective.
  • A time limit — 90 minutes from charter creation, plus any Order buffs (see below). The clock runs whether the party is making progress or not.
  • A failure trigger — running out of time auto-fails the run; the charter being abandoned by every member also ends it.

The framework is reusable — each individual expedition is a definition plugged into the same underlying engine. New expeditions can be added as content rolls out without rewriting the runtime.

How Expeditions Differ from Other Group Content

The shard offers several group-content surfaces; each fills a different niche:

Convoys Dungeons Expeditions Champion Spawns
Coordination required None Optional Required Heavy
Party size Variable (any) Variable 2-4 Variable
Region access Open to all Open to all Charter members only Open to all
Failure consequence Lost trip Death + recovery Run forfeit Lost contribution
Time pressure Travel duration Self-paced 90 min hard Spawn cycle
Reward shape Per-player gold Loot + tokens Shared completion Powerscrolls + loot

The Expeditions row is not a per-party instance — the dungeon geometry is one shared physical area; access is gated to charter members. Functionally that means the same area is locked to one party at a time.

Expeditions are specifically the structured-party option. A duo or small group of friends who want a focused, time-pressured run with predictable shape — that's the expedition niche.

The Charter

The Charter item is the expedition's anchor:

  • One charter = one expedition run.
  • It's issued and the run starts in the same step — talking to the expedition's lead NPC creates the charter, drops it into the leader's pack, and starts the timer immediately. There is no separate "activate the charter" action.
  • The leader is the only member at start. Allies join afterward by walking to within 3 tiles of the leader and double-clicking the charter.
  • The charter persists for the lifetime of the expedition (90 minutes plus buffs). On completion, failure, or timeout the system destroys the charter.

The charter approach means expeditions don't queue or schedule — they fire on demand. There's no system-side timer waiting for a "raid window"; if a duo wants to run an expedition at 3 AM, the leader walks to the lead NPC and goes.

Two Order systems can enhance a charter with bonus time before the expedition starts:

  • High Ledger — a Witness+ Ledger member targets the charter and adds time, but the bonus is the same per tier regardless of the applier's specific rank: +5 minutes at Witness or Arbiter, +10 at Chancellor, +15 at Proctor or above.
  • College of Chirurgeons — a Chirurgeon at sufficient rank applies a Prestige Hunt blessing: Tier 1 = +3 min, Tier 2 = +5 min + party revival, Tier 3 = +8 min + party revival, Tier 4 = +10 min + party revival + loot boost.

The two buffs stack additively, so a fully-buffed charter (Ledger Tier 3 + Chirurgeon Tier 4) starts with 115 minutes instead of 90 (90 + 15 + 10).

Forming a Party

Party formation happens after the leader receives the charter, not before:

  1. Talk to the expedition's lead NPC. They issue the charter and the expedition starts immediately. The leader is now the only member; the 90-minute timer is running.
  2. Recruit 1-3 other players from chat, the Commons, your guild, or anywhere else. The cap is 4; the design floor is 2 (the runtime doesn't strictly enforce the floor — the expedition will run with just the leader, but the encounters aren't calibrated for solo play).
  3. Have each recruit walk to within 3 tiles of you and double-click the charter in your pack or hand. Each successful join broadcasts to the party and bumps the member count toward the 4-member cap.
  4. Travel to the expedition region. Joining the charter does NOT teleport anyone — each member walks, recalls, or moongates to the area on their own. The region's entry guard ejects non-members back to the entrance, but it's not a teleport target for members.

There's no roster lock. Members can keep joining mid-run as long as the cap isn't met and the expedition is still active. A late arrival can hop in five minutes before the timer expires if the party still has a slot open.

Inside the Expedition

Once the expedition is live:

  • The party works through objectives in the order the expedition defines. Some are linear, some are parallel, some have prerequisites.
  • Progress is shared across all members. When one player flips the lever or recovers the document, the objective marks complete for everyone.
  • The region is private. Non-members are ejected back to the entrance the moment they cross the region boundary.
  • The timer is visible. Double-clicking the charter (or any member running the [ExpeditionStatus command) opens a gump showing time remaining, the member roster (with online/offline tags), and the objective checklist with checkbox marks.
  • The system fires warnings at 15 minutes and 5 minutes remaining — every online member sees "WARNING: 15 minutes remaining!" and "WARNING: 5 minutes remaining!" respectively.
  • Disconnects are recoverable. A member who disconnects is auto-prompted on reconnection: a system message confirms they're still in an active expedition, the gump opens, and a Rejoin Expedition button (also available via [ExpeditionStatus) teleports them to the latest checkpoint location, which the system updates as the party advances.
  • Charter holder disconnect does NOT end the run. The charter is an item; the expedition's anchor is the charter's serial, not the leader's connection. Anyone holding the charter, or anyone in the party at all, can keep playing.
  • Death drops the player to a corpse like any other UO death. Resurrection options are whatever the player and party can muster — there's no built-in respawn system in the framework. The Chirurgeon T2+ blessing adds party revival on top of that. The run only fails on full party departure (every member uses Leave Expedition) or timeout.

The 90-minute window is deliberately tight for first-time runs and comfortable for experienced groups. The first three or four runs of an expedition are about learning the layout and objective sequence; later runs are about efficiency.

The Sunken Archives Expedition

The first (and currently only) live expedition is The Sunken Archives — a flooded library southeast of Britain containing centuries of lost knowledge, guarded in its deepest chamber by a corrupted water spirit.

  • Party size: 2 (design floor) to 4 (hard cap).
  • Time limit: 90 minutes from charter creation, plus any Order buffs.
  • Theme: aquatic / library / lost-knowledge.
  • Objectives (4, in sequence, with shared progress across the party):
    1. "Clear the foyer and unlock the inner gate" — opening rooms plus a locked gate; at least one member needs lockpicking (or the run can't proceed past room 1).
    2. "Recover the waterlogged tomes from the stacks" — three Waterlogged Tomes scattered across the library stacks; pick up all three.
    3. "Breach the sealed vault" — a second locked door, the Vault Door, in the deeper section.
    4. "Defeat The Archivist and recover the ancient scroll" — final boss fight against the water-spirit Archivist; recover the Ancient Archive Scroll on the kill.
  • Lead NPC: Archivist Marek, "the keeper of lost knowledge," at (1539, 1747, 15) on Trammel — a building near the Britain docks. He issues the charter and accepts the recovered scroll on completion.
  • Per-member reward (dropped to each member's pack on completion): 1,500 gold + 10 Time Tokens + 3 Blood Crystals + 1 Archived Knowledge volume, plus a Seasonal Ledger source credit (sunken_archives_done).
  • Repeatability: once per account, ever. A successful completion sets the SunkenArchivesDone account tag; Marek will not issue another charter to that account afterward.

The flavor is deliberate: the Sunken Archives is a knowledge-recovery expedition, not a combat-only dungeon. The combat is real — The Archivist is a serious water-spirit fight — but the framing is preservation. It pairs naturally with civic-archival players (Ledger members, Golden Beads collectors) who care about durable record-keeping.

Future expeditions are designed to use the same framework with different themes, objectives, and lead NPCs. The 2-4 player range, the 90-minute window, the on-demand charter-issued shape, and the Order buff system are the load-bearing parts; the content layer is where each variant differentiates.

Why the System Exists

The shard's design instinct: coordinated party play deserves a structured surface. Two failure modes Expeditions are built against:

  • Open-world group content overrun by passers-by. When a party of three is in a shared dungeon and a random fourth player walks in and starts pulling, the run can collapse. Expeditions gate the dungeon to charter members — your party's run is your party's run, even though the underlying world geometry is shared.
  • Raid scheduling overhead. Larger MMOs require pre-formed guild raid groups, weekly schedules, prerequisite gear gating. Expeditions are deliberately smaller — a duo or small friend group can fire one whenever they're together.

The 90-minute window is the design's pacing answer: long enough for real depth, short enough that "let's do an expedition" doesn't mean "let's commit our evening." Two friends who log on for 2 hours can run an expedition together and have time left for other content.

How the System Connects

Expeditions plug into several other systems:

  • Immortal Realm Dungeons — the broader dungeon system covers the open-world dungeon layer; Expeditions are the charter-gated subset.
  • Convoys — the open-world group-content companion that doesn't require pre-formed parties.
  • Achievements — completion of specific expeditions is recorded as achievements.
  • Time Tokens — successful completion typically pays Time Tokens to all qualifying members.
  • Custom Guilds — small guild groups are a natural fit for expedition party formation.

The system is the slot for "structured small-group play" that complements the shard's other group surfaces rather than replacing them.

How to Engage

If you want to run an expedition:

  1. Find 1-3 other players willing to commit a 90-minute window (or longer with Order buffs). Friends, guildmates, or chat-pickup all work.
  2. Talk to the lead NPC. For the only currently live expedition, that's Archivist Marek near the Britain docks. He issues the charter; the run starts in the same step.
  3. Have allies meet you within 3 tiles to double-click the charter and join — this happens after the charter is in your pack, not before.
  4. Watch the timer. 15-minute and 5-minute warnings fire automatically; plan your last objective push around them.
  5. Note the per-account repeat policy. The Sunken Archives is a one-completion-per-account expedition; failing or letting it time out also consumes the charter. Treat your one run as a real attempt.

For solo players: a single-leader expedition is technically runnable (the runtime doesn't enforce the 2-player floor), but the boss and encounter scaling are calibrated for 2-4. If you want comparable structured content alone, Convoys and Britannia Murders are the better fit.

Frequently Asked Questions

How are Expeditions different from convoys?
Convoys are scheduled ambient content — the caravan exists whether anyone shows up or not, and strangers can escort the same convoy without coordination. Expeditions are charter-based — a defined party of 2-4 players forms intentionally, enters a private dungeon region (gated to charter members; not a per-party instance, just a single shared physical area with membership enforcement), and works through shared objectives on a 90-minute timer. Convoys are open-world group play; Expeditions are coordinated party play.
Do I need to be in a guild to run an Expedition?
No. Expedition charters are private to the party that holds them, but the party itself can be guildmates, friends, or strangers who paired up for the run. There's no guild requirement. Most expeditions form through the Commons or chat, run together for the 90-minute window, and disband or repeat as they choose.
What happens if my expedition runs out the time limit?
The expedition fails. The system messages the party 'The expedition has FAILED! Time has run out.', teleports all online members back to the entrance, destroys the charter, and pays nothing — there is no partial credit. Warnings fire at 15 minutes and 5 minutes remaining so the party knows the deadline. Order buffs stack additively: High Ledger gives +5 min at Witness/Arbiter, +10 at Chancellor, or +15 at Proctor+; Chirurgeon Prestige Hunt blessing gives +3/+5/+8/+10 by tier (revival at T2+, loot boost at T4). A fully buffed charter starts with 115 minutes instead of 90.

Related Guides

Shield icon

Looking for a modern UO experience?

Play on Immortal Realm.

Play on Immortal Realm
Footer ribbon flourish