The Summoner PS2 Randomizer Project

We are taking apart Summoner and Summoner 2 — the 2000 and 2002 PlayStation 2 RPGs from Volition and THQ — down to the file formats, and rebuilding them into a proper randomizer. Doors and entrances, items, shops, encounters, characters, cutscenes and maps. This is the build log.

VPP format cracked Text-script layer solved ISO pipeline working Doors solved — 151 of 218 remapped Binary patching live Summoner 2: VPP v2 reader still to write Play-testing help wanted
github.com/nto-live/Summoner-Summoner2-Randomizer → Read the FAQ

What is a Summoner randomizer

A randomizer shuffles a game's contents so that no two playthroughs are the same. In most randomizers that means shuffling which items appear where, so you have to search the whole game for the thing you need instead of walking a memorised route. This project aims to go further:

  • Entrance and door randomization — doors lead somewhere other than where they used to, so the map itself becomes a puzzle.
  • Item and shop randomization — what you find, and what it costs.
  • Encounter randomization — which creatures show up in which regions.
  • Character and model swaps — who stands where, and what they look like.
  • A one-hour mode — a curated, solver-validated route for racing.

Every seed has to be beatable. That is the hard part, and it is why a reachability solver is a prerequisite rather than a luxury.

Why Summoner, and why nobody has done this

Summoner launched alongside the PlayStation 2 itself in October 2000 — one of the few RPGs on the shelf that day, built by Volition before they became the Saints Row studio. It sold modestly, aged strangely, and got almost no modding attention in the twenty-five years since. The entire community toolset for the PS2 version amounts to a widescreen patch.

Which is exactly why it is worth doing. There is no prior art to lean on, and no documentation to read. Everything below was worked out from the disc.

What we've already cracked

Work started September 2026. Both discs are far more open than expected: the archives store their own filenames in plain text, and the game's data layer turned out not to be binary at all.

FORMAT

VPP archives, decoded

Volition Pack: a fixed header, a table of contents of 64-byte records at 0x800, and entry data packed sequentially from 0x1000. Filenames are stored unencrypted. Nine archives, 6,433 files on Summoner 1 alone.

DATA

The data layer is plain text

All 527 table entries are a human-readable script language — doors, dialogue, spawns, triggers, items. Randomizing them is text surgery, not binary patching.

SOURCE

The linker map shipped unstripped

MAIN.MAP is on the retail disc with the original source tree intact: code/summoner/summoner.o, code/vsdk/…. A function-level index of the executable, for free.

WORLD

50 named levels and their rooms

Real developer names for every map — Catacombs, Jadetemple, KhosaniStrng, Lenele1aa–3d, WorldMap1 and the day/night overworld regions — plus named interior geometry down to individual stairwells.

PIPELINE

ISO in, randomized ISO out

A working end-to-end build: read a disc image, apply table-layer transforms, write a new image. About a minute for 1.2 GB, byte-size preserving so nothing shifts.

TRIVIA

The developers signed it

The level scripts contain section markers named after the people who wrote them — #Abe, #bob, #Dennis, #cathey, #earle.

#Doors  — from a Summoner level script, verbatim

$Door: "cry_tombcen"
+Open sound: "Doors\Open_Stone_verylarge.wav" 20.0 1.0 1.0
+Close sound: "Doors\Close_stone_verylarge.wav" 20.0 1.0 1.0
+Locked: 0.50

// progression gates are expressed as level + flag pairs
+Trigger: "khosanistrng" "ready_for_end"
+Trigger: "TempleInt"    "unhide_madog"

What can be randomized so far

TargetStatusNotes
Door locks & soundsworkingLock and audio data shuffle today.
Cutscenes & musicworkingGood for pacing and for chaos seeds.
Shops & economyworkingPrice shuffle, everything-free, crazy numbers, and a no-shops lever.
Chests & loose itemsworkingChest payouts, what a chest actually yields, and item scatter.
Encounters & spawnsworkingCreature placement swap, swarm, and a none / few / many / all dial.
Enemy stats & healthworkingDifficulty scaling, hostile stat shuffling, and a one-hit-kill lever.
XP & enemy dropsworkingRandom or settable kill XP, random drops, guaranteed drops.
Weapons & armourworkingWeapon damage and armour protection levers, clamped per field.
Item stats & descriptionsin progressThe item table is located; the levers above ship, shuffling the stats themselves is next.
Door destinationsworking200 of the 218 doors rewrite their destination at a typical seed from the level tables, with the overworld hub and the opening-area sources held back on purpose — their load path is a different animal, and a stranded boat ride is game-breaking. Two discs differing by one rewritten name have been loaded live in the game.
Party statsworkingThe playable party’s own numbers shuffle among the party — hit points, ability points, aggression, ranges and turn rates.
Rooms & layoutworkingWithin a level, what populates it moves to other spots in that same level — a level is furnished differently while every location stays reachable by construction.
Bossesworking — one limitA level’s bosses gather onto one point of that level. One giant shared arena is not reachable this way: a spawn anchor only resolves inside the level that declares it (the same names repeat in up to 107 different levels), so moving bosses between levels needs extra bytes the archive cannot give. Documented as blocked rather than faked.
Loot routingworkingShop stock and quest rewards trade into chests, so a good has to be found rather than bought. Nothing is lost or invented — names only ever swap at equal length.
NPCsworkingWho stands where is shuffled: the people of the world are relocated within their level and re-cast.
Character classes & skillsplannedClass and skill records identified.
Character modelsplanned2,556 model files; format not yet decoded.
Summoner 2 (all of it)blockedNeeds the VPP version 2 archive revision decoded first.

How the Summoner 2 disc differs

Summoner 2 (SLUS20448, 2002) is a different animal. Its assets live under /S2ASSETS/ instead of the disc root, its cutscenes are split into individual archives organised by region, and its boot executable SLUS_204.48 is only 1.8 MB — against 17.5 MB for Summoner 1.

Critically, it uses a newer VPP revision: same magic number, different header, and a 28-byte table-of-contents record where version 1 used 64 bytes. The old reader returns zero entries for these files. Decoding that revision is the current blocker for Summoner 2.

Its level scripts are readable already, though — arena, city-of-glass, cm1-wheel through cm7-lair, coral-grotto, endgame, galdyr-pass, halassar, highwater, indubal, khargathalan, mud-god-boss.

The one-hour mode

A normal Summoner run is a twenty-hour proposition. We want a mode a competent player can finish in about sixty minutes — roughly a 20× compression. Shuffling alone cannot do that, so the plan is a curated critical-path slice:

  • Pre-satisfy the flag chain. The game gates progress with flags on doors and triggers. Anything that gates only optional content gets granted up front. This is where the hours actually come from.
  • Critical-path doors only. Randomization is confined to levels on the solved route, so a seed can never strand you in a dead-end area.
  • Combat floor removed — fights become traversal, not time sinks.
  • Cutscenes bypassed — a large fraction of a casual run.
  • Encounter rates cut in the overworld regions.
  • Every seed validated against a reachability solver before it ships. An unbeatable seed is a bug, not a challenge.

How to play a Summoner randomizer

  1. Own a copy of the game. You need to dump your own disc — we do not supply one. See the note below, and it is not a formality.
  2. Run the randomizer against your disc image. It produces a new, size-preserving image with the shuffled data written in.
  3. Play it in PCSX2 on a PC, or on real hardware via softmod such as FreeMcBoot with OPL, or on a modded console.
  4. Share the seed. Identical seed plus identical settings equals identical randomization, which is what makes racing possible.

The project is in active development, so none of this is a release yet.

Roadmap

  • DONE
    VPP format v1 decoded, full asset inventory of Summoner 1, working ISO pipeline, both discs dumped and hash-verified. Door destinations solved — all 218 doors mapped, remapped in the engine, and proven in game. Every lever requested for Summoner 1 is now built — 47 modes over 57 transforms, from shops and chests to stat shuffles, random rooms, loot routing and boss gathering.
  • NOW
    In-game verification — watch the levers actually happen (doors, stat dials, chest grants, boss gathering) instead of only proving them at the byte level, and build the flag graph + reachability solver that a full door remap needs. In parallel: the VPP version 2 reader for Summoner 2.
  • NEXT
    Build the flag graph and reachability solver so the critical path is computed, not guessed.
  • THEN
    v0.1 “Chaos” — items, shops, audio, cutscene order. No lock risk.
  • THEN
    v0.2 “Doors” — entrance randomization across a whole act. Interior doors already ship; the reachability guard is what is missing.
  • LATER
    v0.3 the one-hour mode, then a raceable v1.0 with spoiler logs.

Progress log

Dated entries, newest first. The labels mean exactly what they say — build-verified (the engine applied it, size preserved, changes confined to declared fields), byte-verified (read back off the disc), boot-verified (the emulator reaches gameplay), play-verified (watched happening in the game). Anything unproven is labelled unproven.

  • 02 OCT
    Modes are now sorted into Tested and Experimental. The app splits its mode list by a data-driven flag, so anything that has actually been played through is separated from everything that only builds — and only two presets are in Tested so far. Boss Rush and Roguelike are marked blocked, and the full boss-rush investigation (gold levers, the recovered boss-to-level map, the instruction-level crash analysis and the hard rules learned) is written up in the repo. The headline is now honest about the real bottleneck: the engine is well ahead of the testing, so a play-testing call goes out — if you own the disc and an emulator, you can move a mode from “builds” to “verified.”
  • 30 SEP
    The whole requested Summoner 1 set is built. The last four levers land: random rooms (within a level, so every location stays reachable by construction), an NPC Hunt preset, boss gathering, and loot routing that trades shop stock and quest rewards into chests. The engine now carries 47 modes and 57 transforms. Boss Rush arrived with a correction worth stating plainly: the original design — every boss in one shared arena — cannot work, because a spawn anchor only resolves inside the level that declares it (the same anchor names repeat in up to 107 different levels). What ships gathers a level’s bosses onto one point of that level; the single arena is documented as blocked rather than shipped broken. Verification stays explicit about its tiers: the new disc is byte-verified, record-verified (read back off the built disc by an independent checker), and boot-verified with a level loaded in the running game — but the bosses gathering itself has not yet been watched, and it is labelled that way.
  • 29 SEP
    The tutorial problem, solved twice. The first “tutorials off” claim was wrong — it came from a single lucky play, and later seeds disproved it, so it was retracted and relabelled experimental. The real lever turns out to be the tutorial dispatcher’s input gate: patch that one branch and every tutorial step auto-advances with no button press, so nothing holds you up while the scripted scene actions — the burning village’s fire barrier clearing among them — still run (play-verified). The plausible-looking alternative, hiding the popup window, was play-tested and rejected: the boxes vanish but the gate stays, leaving the player frozen at the start with no instructions. A real end-user soft-lock was closed at the same time — door-name shuffle could rename the fire barrier itself, which the engine removes by a hardcoded name; it is now pinned. One problem stays open and is labelled as such: the full-stack build still freezes movement at the opening, isolated to a transform rather than the tutorial patch, and the bisect is staged.
  • 28 SEP
    The chaos build. Seven new levers into the engine: weapon damage and armour protection maximums, one-hit-kill enemies, random or settable kill XP, random enemy drops, guaranteed drops, and music-only shuffle. The boot logos are gone (play-verified). Three real door bugs found and fixed — a quote-writing bug that silently malformed destinations, a missing arrival-slot check, and the rule that 128 of the 218 doors fall back to the destination's own script name. Coverage is 151 of 218 interior doors, with the overworld held back on purpose. A test suite landed alongside it.
  • 21 SEP
    Doors solved. The destination is a $Trigger: name in the level's own text table — not in the .p3d geometry, which was the wrong tree entirely. All 218 doors mapped, a 218-patch remap applied with zero collateral bytes, and the mechanism proven in game: two discs differing by one rewritten name load two different levels.
  • 20 SEP
    First playable pipeline. Disc image in, randomized image out, byte-size preserving. Headless emulator verification working, which is what made everything after this provable rather than hopeful.
  • SEP
    The format work. VPP archives decoded (filenames in plaintext), the data layer turns out to be a human-readable script language rather than binary tables, and the retail disc ships its own unstripped linker map — a function-level index of the executable, for free.

Source code and the full build log on GitHub →

Help wanted: play-testing

This randomizer is built and verified by hand, one disc at a time, and that hand is the bottleneck. Almost every mode in the engine is boot-verified at best — it builds a disc that starts — but next to none of it is play-verified: nobody has played it through in game. If you own Summoner (PS2, SLUS-20074) and an emulator or a console, you can move a mode from guesswork to fact.

The project rule is: boot-verified is not play-verified. A mode only moves from the Experimental tab to the Tested tab after somebody plays it and confirms it behaves. Only two have made it so far.

Already play-verified (the “Tested” tab)

  • Vanilla — No Tutorials. The retail game with only the opening tutorials turned off.
  • Tested — No Tutorial + 1HP + Random Loot (the “CHAOS” recipe). Tutorials off, enemies randomized within their own area, every enemy dies in one hit, random drops and maxed gold, boosted XP. Confirmed to boot, move and progress past the opening.

Needs testing (everything in the “Experimental” tab)

Every other mode builds a size-valid disc but has never been played through. Roughly in order of value:

  1. Door Remap — does the world stay completable, or does a door strand you, bounce to the title, or load a black room? Note the seed and where it broke.
  2. Door Shuffle — locks, names and sounds shuffled. Should be safe; confirm nothing soft-locks.
  3. Short Run / One Hour — pacing, cutscenes skipped, XP scaled. Does it play to the end?
  4. No Enemies / Enemy Swarm / Oops All Enemies — do quests still work?
  5. Monster Chaos / Random Enemy Stats — is combat winnable? Any soft-locks?
  6. Item Scatter / Shop / Chest / Item Hunt — does anything required become unreachable?
  7. Random Rooms / NPC Hunt — placement shuffles within a level.

What is blocked (do not expect these to work)

  • Boss Rush / Boss Rooms / Boss Gauntlet — exhaustively attempted and proven unachievable in the data: bosses are hidden, scripted set-pieces, not placeable live enemies.
  • Roguelike — stacks eleven unverified changes; blocked pending validation.
  • Summoner 2 (SLUS-20448) — not implemented. The tool randomizes Summoner 1 only; the “Summoner 2 — TBD” tab is a placeholder, not a working target.

How to report a result

For each mode you test, note the mode name and seed (both shown in the app; the seed is in the output ISO name too), whether it booted, how far it played through, and what broke, exactly — freeze, bounce to title, missing enemies/NPCs, a quest that cannot complete — with the area name and what you were doing. A screenshot of any freeze or black screen is extremely helpful. A clean “played it start to finish, no problems” is just as valuable as a bug — it is how a mode earns its place in the Tested tab.

Report a play-test on GitHub Issues → Full testing doc →

Summoner randomizer FAQ

Is there a randomizer for Summoner on PS2?

Not yet publicly. As of September 2026 this project is building the first one. Summoner has had essentially no modding scene since 2000 — the only community tool for the PS2 version has been a widescreen patch. We have reverse-engineered the VPP archive format, the plain-text data layer and the level geometry index, and have a working ISO-in / randomized-ISO-out pipeline.

Does Summoner 2 have a randomizer?

Not yet. Summoner 2 (PS2, SLUS20448) uses a newer revision of the VPP archive format — version 2 — which has a different header and a 28-byte table-of-contents record instead of version 1's 64-byte record. Decoding that revision is the current blocker before Summoner 2 can be randomized.

Can you randomize doors and entrances in Summoner?

Yes — and this is the feature that landed. A door's destination turns out not to live in the level geometry at all: it is a $Trigger: name written inline in the level's own text table, and rewriting that one string redirects the door completely. That was the wrong tree hunted for days — worth saying out loud. We mapped all 218 doors, verified the mechanism in game on two discs that differ by a single rewritten name, and shipped it in the engine as a seed-driven transform. 151 of 218 interior doors currently remap. The overworld hub is held unchanged on purpose: those doors bounce to the title screen through a load path the tables cannot prove safe yet, and a stranded first boat ride is game-breaking.

What can be randomized in Summoner right now?

Door destinations (interior, 151 of 218), door locks, names and open/close sounds, NPC and enemy character assignments, creature placement and swarm counts, enemy stat and HP levers, kill XP and enemy drops, chest contents and payouts, shop prices (including everything-free and crazy-numbers), loose-item scatter, model references, cutscene ordering, music and SFX shuffles, and the boot logos (removed). All of it is size-preserving table-layer surgery, and all of it is build-verified on a real disc image — the door work is also play-verified in game.

Do I need a modded PlayStation 2 or an emulator?

Either works. The randomizer produces a modified disc image, so you can run it in PCSX2 on a PC, or on real hardware via softmod such as FreeMcBoot with OPL, or on a modded console.

Does the project distribute the game or ISO files?

No. No disc images, ISOs, ROMs or download links are distributed or hosted anywhere by this project, on this site or anywhere else. You must supply your own legally dumped copy of the disc.

Will there be a one-hour completion mode?

Yes, that is a design goal. A normal Summoner run takes roughly twenty hours, and the target is a mode completable in about sixty minutes. It works by confining randomization to the critical path, granting flags that gate only optional content, lowering the combat floor, bypassing cutscenes and validating every seed against a reachability solver.

What are the disc revisions you are working from?

Summoner 1 is the US PlayStation 2 release, SLUS-20074, published by THQ and developed by Volition, released 24 October 2000. Summoner 2 is the US PlayStation 2 release, SLUS20448. Both images are hash-verified against the original source.

Status: active development, October 2026. Door destination randomization is solved and shipping; Summoner 2 is still waiting on its archive revision. Formats are still moving and the pipeline is being rebuilt constantly, so nothing here is a release. Progress is logged as it happens.

Help wanted: most modes are built but not yet played. If you own Summoner (PS2, SLUS-20074) and an emulator, you can move a mode from Experimental to Tested — see Help wanted: play-testing.