That is the cleanest way to say it.

Before FUDGE, most role-playing games described characters with numbers first. Strength 14. Dexterity 11. Skill 63 percent. Sword 17. The number meant something only if you already knew the system’s scale.

O’Sullivan asked a simpler question.

What if the character sheet just said the thing?

Fair. Good. Great. Superb.

That was the breakthrough. Not because words had never appeared on a character sheet before. They had. The breakthrough was making the words the operating system.

FUDGE put ordinary language at the center of resolution. The numbers still existed underneath, but they stopped being the face of the game. A Good swordsman was good. A Superb detective was superb. The player did not need a chart to know what the word meant.

The math disappeared behind meaning.

The Gurps Years

O’Sullivan did not begin as a minimalist.

He entered the field through GURPS, Steve Jackson Games’ great universal toolkit. GURPS is a beautiful piece of machinery for people who like machinery: point values, advantages, disadvantages, skills, modifiers, and enough structure to model almost anything.

O’Sullivan wrote for that machine.

GURPS Swashbucklers showed his love of history, fencing, and genre detail. GURPS Bunnies & Burrows adapted a famously odd animal-role-playing premise into the GURPS framework. His work was careful, researched, and comfortable inside a system that rewarded precision.

That precision taught him the cost of precision.

Every lookup has a weight. Every modifier pauses the table. Every chart asks the fiction to wait while the players consult the machine. For some games, that weight is the pleasure. For others, it is friction.

O’Sullivan became interested in the friction.

He called it system intrusion: the moment the rules step between the player and the experience.

FUDGE was his answer.

The Online Engine

FUDGE began in public.

In 1992, O’Sullivan posted an idea for a collaborative RPG project to the rec.games.design newsgroup. He wanted input, but he also understood why purely committee-built designs fall apart. People could contribute, argue, suggest, and test. He would make the final calls.

That balance mattered.

The system changed names and shapes. SLUG became FUDGE. The acronym eventually stood for Freeform Universal Do-it-yourself Gaming Engine. The text that emerged in the mid-1990s was O’Sullivan’s, but the process had community fingerprints all over it.

This was unusual.

FUDGE was free on the internet before the Open Game License, before online RPG publishing became normal, before most of the industry understood what an open system could do for design culture.

O’Sullivan treated a rules engine like shared infrastructure.

Not a box to guard.

A toolkit to hand out.

The Free Engine

That decision was not cosmetic.

A free system changes the behavior around it. People can test it without asking permission. They can hack it without waiting for a license call. They can send it to a friend, rewrite a piece, run a convention game, or build a campaign that bends the original text in directions the author never planned.

That is exactly what FUDGE wanted.

The game was called Do-it-yourself for a reason. O’Sullivan was not only lowering the financial barrier. He was lowering the psychological barrier between player and designer. The table was allowed to finish the system.

That idea would become normal later.

In the early 1990s, it was strange.

Most publishers protected systems as products. O’Sullivan released a system as a starting point. The distinction matters because the greatest proof of FUDGE’s success was not that everyone played FUDGE exactly as written. It was that other designers could take its tools and make something else.

The Ladder

The Adjective Ladder is the part everyone remembers.

Terrible. Poor. Mediocre. Fair. Good. Great. Superb.

The ladder can extend higher or lower, but the center is easy to grasp. Fair is ordinary. Good is good. Great is great. Superb is not just a bigger number. It is a word with a feel.

That matters because RPGs are interfaces.

A number asks the player to learn the scale. A word brings the scale with it.

The dice support that idea. Fudge dice use plus, minus, and blank faces. Roll four of them and the result usually stays close to the character’s established rank. Extreme results can happen, but the curve is tight enough that competence feels like competence.

That is the design philosophy in one mechanic.

Characters are usually who the sheet says they are.

The game still has uncertainty. It still has drama. But the dice do not constantly sabotage the fiction for the sake of swinginess. They bend the moment around the established truth of the character.

That is why the ladder traveled.

The Toolkit, Not The Cathedral

FUDGE was not a complete game in the way many players expect a complete game to be.

It was a toolkit. A language. A set of resolution assumptions and modular pieces that a game master could shape into the campaign they wanted. Gifts, faults, traits, scale, magic, combat detail, genre assumptions: the table could decide how much to use.

That was both strength and weakness.

The strength is obvious. FUDGE could become many things. It could support fantasy, detective stories, space opera, superheroes, swashbuckling, or homebrew weirdness. The ladder and dice held the center while the outer pieces changed.

The weakness is just as real.

Toolkits demand builders. A new group may not want to assemble the game before playing it. A bad build can stack bonuses too high, make the ladder unstable, or leave the skill list too vague. FUDGE trusts the game master. Sometimes that trust is a gift. Sometimes it is a burden.

O’Sullivan knew the tradeoff.

He chose openness anyway.

Sherpa And The Lower Limit

Sherpa pushed the same idea even further.

It was designed to be played while hiking. Character information could fit on a small card. The randomizer could come from a digital watch. The point was not novelty for novelty’s sake. It was an experiment in how little interface a role-playing game could need and still remain a role-playing game.

That is pure O’Sullivan.

Remove everything that gets between player and experience.

If the game can fit in your pocket and run while walking up a trail, the rules have learned to get out of the way.

Not every game should be Sherpa.

But Sherpa proves the question was serious.

The Princess Bride

The Princess Bride Role-Playing Game, published in 2019, shows the mature form of O’Sullivan’s philosophy.

It still uses FUDGE at the core. The adjective ladder is still there. The dice are still there. The commitment to readable, low-intrusion play is still there.

But the design is no longer only a universal toolkit.

It is tuned to a specific story world. The meta-currency speaks in the language of the film. The swordplay cares about style and timing. The system is still light, but it has learned how to be pointed.

That matters because it answers one criticism of FUDGE.

FUDGE can feel too open.

The Princess Bride narrows the lens. It shows that O’Sullivan’s engine can serve a beloved license without smothering it. The game does not ask players to admire the machinery. It asks them to step into a tone they already love and start playing.

Twenty-six years after FUDGE first appeared, the same design idea was still alive.

The Fate Line

FUDGE’s largest legacy runs through Fate.

Fred Hicks and Rob Donoghue built Fate from Fudge play. The name itself began as Fudge Adventures in Tabletop Entertainment. Fate inherited Fudge dice, the ladder, skills rated in ladder terms, and the basic belief that descriptive language could carry mechanical force.

Then Fate added its own central invention: Aspects.

That is how influence should work.

O’Sullivan did not design Fate. Hicks and Donoghue did. But Fate could not be what it became without the FUDGE foundation. The ladder, the dice, and the free toolkit culture gave later designers something to refine into a more plug-and-play game.

Fate went places FUDGE did not.

It won awards, powered major titles, gathered a larger community, and became one of the defining story-forward RPG families of the 2000s and 2010s.

That is propagation.

Not vague inspiration.

Lineage.

What He Actually Built

Steffan O’Sullivan did not invent role-playing resolution.

He did not invent descriptive language in games from nothing. He did not build a huge commercial catalog. He did not turn FUDGE into the largest version of itself.

What he built was the interface that made later work possible.

He made adjectives carry rules weight. He matched those adjectives to a dice curve that respected character competence. He released the engine freely enough that other designers could build from it. He proved that a system could be both formal and conversational.

That is the real achievement.

The game did not need to ask, "What does 14 mean?"

It could say Good.

And everyone at the table understood.

Where To Find Him

O’Sullivan’s work remains visible through FUDGE, Fate’s ancestry, The Princess Bride Role-Playing Game, his GURPS supplements, Sherpa, and the continuing presence of Fudge dice in the hobby.

His catalog is not huge.

His footprint is.

Most designers who give away a system lose control of where it goes. That is the risk. O’Sullivan accepted it. Then Fate happened. Fudge dice became a familiar object. The adjective ladder became part of the RPG vocabulary. A free toolkit became infrastructure.

That is why this story still matters.

He did not build the empire.

He gave away the tools.

Other people built with them.