Mabel Addis did not enter game history through an arcade, a hobby shop, or a university computer lab full of young programmers trying to make machines play.

She entered through a classroom.

That matters because The Sumerian Game was not built to show off technology. It was built to teach. The machine was a means. The goal was a student making decisions, facing consequences, and learning history by living inside a system instead of memorizing facts from outside it.

In the early 1960s, Addis was a teacher in northern Westchester County, New York. The Board of Cooperative Educational Services worked with IBM on an experimental educational computing project. The surviving collection at The Strong identifies The Sumerian Game as a BOCES project designed to teach sixth graders basic principles of economics through ancient Mesopotamian society.

Students did not simply read about Sumer.

They ruled it.

That is the leap.

The Classroom Machine

The Sumerian Game ran on mainframe hardware and reached students through the technology of its time: teletype printouts, typed inputs, slides, and programmed instruction.

The Strong’s Sumerian Game collection preserves three teletype printouts of sample gameplay, 39 Kodachrome slides used to introduce the game to students, and a research report filed with the U.S. Office of Education. Those surviving materials are not the complete original game. They are fragments of a pioneering experiment.

But the fragments are enough to see the shape.

The student took the role of a ruler in ancient Lagash. The game presented agricultural and economic dilemmas. Grain had to be managed. Land had to be allocated. Population and harvests changed. Disasters could strike. Later phases introduced crafts, trade, and other economic factors.

This was not a quiz wearing a costume.

It was a simulation with a narrator, a setting, a role, and consequences.

The student made decisions. The system answered.

That feedback loop is the heart of game-based learning.

Addis helped build it before the vocabulary had caught up.

The Teacher’S Move

The most radical part of the project may be how ordinary it sounded in educational terms.

Addis was not pitching entertainment as rebellion. She was trying to help children understand an ancient economy. That gave the work permission to be experimental. A classroom could accept a strange machine if the stated purpose was learning.

Inside that respectable frame, something new happened.

The student was not asked only to absorb a lesson. The student was asked to act, wait for the system’s reply, and revise their understanding. That is the central rhythm of interactive design.

The Writer In The Machine

The division of labor is important.

Mabel Addis designed the experience and wrote the game. William McKay programmed it. The Game Developers Choice Awards now describes Addis as the lead designer of The Sumerian Game and recognizes her as a pioneer whose work helped anticipate elements that became common much later, including in-game narrative experiences and early cutscene-like presentation through slide shows with synchronized audio.

That is a striking sentence to place beside 1964.

The game used a computer printer to express dialogue and prompts. It used an in-game narrator or character to communicate information and ask questions. It surrounded the computer interaction with audiovisual classroom presentation. It treated the player as someone inside a historical situation rather than someone merely answering test questions about it.

That is writing.

Not prose in a book.

Writing for a system that responds.

That is why Addis has been called the first video game writer and one of the earliest narrative game designers. The claim is not that she invented every later branch of narrative game design by herself. She did something more specific and more fragile: she made a computer-mediated educational simulation speak to a student as a role inside a story.

The Kingdom As Lesson

The Sumerian Game’s teaching method is still powerful.

Give the student authority.

Give that authority limits.

Let the decision produce visible consequences.

Let the lesson emerge from trying to govern.

That is a very different model from rote learning. A student who decides how much grain to store is not just recalling a fact about agriculture. The student is feeling the pressure of scarcity, uncertainty, planning, and responsibility. If disaster arrives, the lesson is not abstract. It has entered the system.

This is what makes the game feel so modern.

Resource management. Branching outcomes. Educational simulation. Role-based learning. A narrator guiding a player through changing conditions. All of these became familiar later. In The Sumerian Game, they appear in a form constrained by the machines of the time, but conceptually recognizable.

The teletype is ancient now.

The design premise is not.

The Limits Of The Beginning

The honest profile has to be careful.

The Sumerian Game was not a commercial entertainment product. It did not circulate like a boxed game, inspire a visible school of direct imitators, or become a mass-market title. Its original code is lost. The surviving archive is partial. Addis did not go on to a long public game design career with dozens of later credits.

That limits what can be claimed.

The game was an educational project inside an institutional experiment. Its reach was narrow. Its architecture was constrained by mainframe computing, teletype output, classroom procedure, and the practical goals of a BOCES curriculum project.

But beginnings often look small because nobody yet knows what scale they belong to.

The Sumerian Game now reads like a seed from a future category: educational computer games, management sims, narrative systems, interactive fiction, classroom simulations, and games where the story advances because the player chooses.

Addis did not have those shelves available to place her work on.

She helped build the first plank.

The Preservation Story

One reason Addis matters more now than she did in many older histories is that the evidence survived.

The Strong’s collection records the teletype scrolls, slides, and research material. The museum has also connected Addis to its broader Women in Games collecting work, noting her Sumerian Game materials as part of documenting women’s contributions to electronic gaming.

Preservation changed the story.

Without the archive, The Sumerian Game could have remained a rumor in the margins: an educational experiment, half remembered, without enough surviving material to understand its form. With the archive, historians can point to the printouts, slides, and report. They can reconstruct the classroom context. They can see that the game was not merely early because of its date, but early because of what it tried to do.

The later recognition followed.

In 2023, the Game Developers Choice Awards gave Mabel Addis the Pioneer Award. Their write-up recognized her not only as the first female game designer, but as the lead designer of a work that anticipated narrative and presentation techniques far ahead of their mainstream adoption.

That recognition arrived after her death.

It still matters.

The Quiet Afterward

Addis’s life did not become a game-industry biography in the usual sense.

She was a teacher, writer, and local historian. She worked in education. She helped preserve and tell histories outside the game world. Public biographical summaries identify her as Mabel Addis Mergardt, born in 1912, and as having died in 2004.

That quiet afterward is part of the shape.

Many early game histories center on people who stayed close to the technology industry and then became visible as the industry grew around them. Addis did not have that kind of arc. She made one extraordinary contribution inside a classroom technology experiment, then returned to the work of education and history.

The game industry discovered her backward.

That is not unusual for pioneers.

Sometimes the first person through the door is not the person who builds the building.

Sometimes she is the person who proves the door exists.

The Pattern

The hidden pattern is responsibility.

The Sumerian Game did not teach by saying, "Here are the facts of Sumerian economics."

It taught by saying, "You are responsible for this city. What will you do?"

That one shift changes the student’s relationship to knowledge. History becomes a system of decisions. Economics becomes risk. Government becomes tradeoffs. Disaster becomes something to plan for, not merely a word in a textbook.

Addis understood the classroom power of role.

That is why the game still feels important. Not because every later management sim descends from it in a clean line. The line is not clean. The importance is conceptual. She demonstrated that a computer could mediate a story-shaped lesson where the player learned through choice.

The student did not watch the kingdom.

The student ran it.

What Remains

What remains is not a playable commercial classic.

What remains is an idea, preserved in printouts and slides: a student at a terminal, a ruler of Lagash, a harvest to manage, a disaster waiting somewhere in the machine.

What remains is Mabel Addis’s place in the history of narrative game design, educational simulation, and game writing.

What remains is The Strong’s archive and the modern recognition that this classroom experiment was part of game history all along.

And what remains is the lesson she built into the form.

Give students a kingdom.

Let consequences teach.

In 1964, on a mainframe, before the industry knew how to name what she had done, Mabel Addis made the computer tell a story back.