Through the Gate: My Stargate Collectible Card Game

Before Space Battles, before the Star Wars fan-film edition, and before Sundered Stars, I was exploring another way to bring a favorite science-fiction universe to the gaming table: a Stargate collectible card game.

This was a game pitch and a playable prototype, with a designed card set, construction rules, a complete turn structure, and several different ways for a battle to develop. I wanted players to command a force, respond to changing conditions beyond the gate, and make difficult decisions about where to commit their people.

The surviving archive contains eighty card images: seventy-nine fronts and a card back, together with a ten-page rulebook labeled Rules v0.6. The rulebook calls the underlying design the AGROE system. Its introduction even welcomes the player to Stargate Command under the signatures of General Jeff Demarest and General Patrick Aquilone.

I remember the pitch as being around 2010, although the surviving cards carry a 2004 copyright notice and the PDF metadata dates to September 2004. Those earlier files are part of the project’s history rather than evidence that every stage happened on one particular date.

About the Artwork: These cards were originally created using screenshots for a personal Stargate game pitch. The illustrations shown here are AI-generated replacements created for this retrospective. This is an unofficial fan project and is not affiliated with or endorsed by the Stargate rights holders.

More Than Familiar Faces on Cards

The recognizable characters were an invitation into the game, but the design had to do something once everyone sat down. A good hand needed to become more than a collection of favorite episodes and familiar names.

The central decisions were about command and commitment. Which Units should enter play? Who should fight now? Who should remain ready to defend? Would an Upgrade make a modest Unit more useful than another expensive reinforcement? Could a Mission force an opponent into an uncomfortable choice before the main attack began?

The gate itself helped prevent the battlefield from remaining static. Its location could affect resources, defenses, and the conditions under which the next Stargate appeared. Both players had to live with those shared circumstances.

This feature documents that original design. The replacement illustrations are new; the underlying card concepts and the rules being discussed belong to the archived prototype.

What You Were Trying to Accomplish

Each player had one Base representing their command. Protecting it was the foundation of the game. If a Base had taken enough damage to be destroyed when the game checked during the End phase of any player’s turn, its commander lost unless another card changed that outcome.

You could win by breaking through to an opponent’s Base, but the system also allowed Quests to establish different objectives. That distinction mattered: a player building toward an alternate victory might force the other commander to respond to something besides the largest attacking force.

The rules gave card text precedence over the general rules. A card could change a normal restriction, modify combat, or introduce a special condition. Flavor text provided the connection to the series, while the ability text did the mechanical work.

Reading the Card Design

The gold frames organized several different kinds of information. The artwork and title identified the subject; the numbers down the side answered different questions about its role in the game.

Part of the cardWhat it meant
Gold Action CostAction required to deploy the card.
Silver ActionContribution from an in-play card to command resources.
Crossed swordsAttack Strength used in combat.
Blue shieldDefense Strength. Bases tracked remaining Defense over the battle.
Rarity symbol and point valueRarity and the card’s contribution to the deck-construction budget.
Alignment colorCompatibility when selecting cards for a deck.
Allegiance and AttributesRace, affiliation, or descriptive labels referenced by other cards.
Keyword and ability textMechanical capabilities, restrictions, and exceptions.

A card’s Alignment was separate from its Allegiance and Attributes. Alignment helped determine deck compatibility. Allegiance described the associated race or group, while Attributes provided labels that other cards could refer to. A Unit being Human, SG-1, or a particular kind of vehicle could matter because another card specifically cared about that label.

The unique symbol meant that only one copy of that card could be in play at a time. The deck could still contain multiple copies within the construction limit; uniqueness was a restriction on the battlefield, not a blanket one-copy deck rule.

A Whole Set of Different Jobs

The eighty archived images cover every card type described in this rulebook. That makes this a particularly useful snapshot of the system: it preserves ordinary troops and equipment alongside the cards that gave the game its larger structure.

TypeArchived frontsRole
Unit33People, troops, and vehicles that form a commander’s military presence.
Event15Conditional responses and special actions.
Upgrade9Attachments that modify an eligible Unit or, where allowed, a Base.
Stargate9Shared location conditions and the baseline resource situation.
Element8Persistent locations and other effects that can stack.
Base2Command centers whose survival determines ordinary victory.
Mission1Focused confrontations before Advanced and Melee combat.
Order1Current instructions, with consequences for disobedience.
Quest1Broader objectives that may establish an alternate victory.

Units were the broad military category. They included named characters, soldiers, civilians, and vehicles rather than treating every person or machine as a separate card type. A Death Glider and a member of SG-1 could therefore share the Unit framework while relying on their Attributes, numbers, and abilities to distinguish them.

Elements remained in play and affected the situation. Their effects could stack, so deployment and combat had to account for every relevant Element, not just the most recently played one. Events were more immediate: their conditions determined when they could be played, and meeting a trigger gave the player an option rather than an obligation to use the card.

Setting Up: Draw Seven, Spend Seven, Return to Seven

Setup began with a legally constructed deck. Each commander placed one Base in the combat area, set aside five shuffled Stargate cards, and prepared a way to track the Base’s remaining Defense. The rest of the cards became the Reinforcement deck. A player using Quests could place one into play at setup.

Then came the opening sequence:

  1. Draw seven cards.
  2. If desired, call the game’s opening mulligan. When one player called for it, the other players could also reshuffle and redraw their initial hands.
  3. Spend seven Action on an opening combination of Units, Upgrades, and Elements.
  4. Place those deployed cards face down.
  5. Draw back up to seven cards in hand.
  6. Once everyone has finished, reveal the opening forces and determine who takes the first turn.

The rulebook summarized it as 7-7-7: draw seven, spend seven, hand to seven. That gave each player a starting presence before ordinary turns began, while keeping the exact opening deployment hidden until everyone was ready.

The first player revealed the initial Stargate. From that point forward, a Stargate was always supposed to remain active.

The Turn: Six Rules of Engagement

The rules called a round in which everyone received a turn a Sortie. Within each turn, play followed six Rules of Engagement, or ROEs.

PhaseWhat happened
1. StargateCheck whether the current gate remains or is replaced.
2. ReadyReturn eligible Engaged cards upright.
3. ReinforceDraw two cards from the Reinforcement deck.
4. DeployCount Action; deploy eligible cards, replace Orders, or disobey an Order.
5. CombatResolve Missions, Advanced attacks, then Melee.
6. EndResolve end conditions and check Base destruction or other victory conditions.

Those steps gave the game a predictable rhythm, while Events and triggered abilities created opportunities for responses within that rhythm. Combat itself contained three distinct stages, so committing a Unit early could affect the choices available later in the same turn.

The rules imposed no hand-size limit. That allowed players to keep situational responses, but holding the right card was only part of the problem: its play conditions still had to be met.

The Stargate Changed the Situation for Everyone

Each player brought a separate five-card Stargate deck. The currently revealed Stargate provided shared conditions, including a baseline contribution to Action, and its text determined how long those circumstances remained in effect.

During the Stargate phase, the active player checked whether the current gate’s replacement condition had been met. If it had, that player revealed a new gate from their Stargate deck and the old gate ceased to be the active location. If not, the current gate and its effects remained. Used Stargates could eventually be shuffled back to replenish an exhausted Stargate pile.

Gate of Earth, Giza is a useful example. Any player controlling a Human Unit gains two additional Action points, and all Human Units receive two additional Defense. Its replacement condition calls for three Human Units in play, with the gate remaining for at least one turn.

That creates a shared strategic question. Deploying another Human might improve your force while also helping satisfy the condition that moves everyone away from a favorable location. The gate is a rule that players can influence through their decisions, rather than simply background scenery.

Nine Stargate cards survive in the archive, including Earth, Abydos, Chulak, Cimmeria, Argos, Shavadai, P3X-797, the Gate of Sacrifice, and the Gate of Cave Dwellers. A deck selected five of those possibilities; it did not need to use the entire available collection.

Action Was Command Capacity

Action determined what you could deploy. The gold cost on a card was the amount required to bring it into play; the silver Action value described what an in-play card contributed to your command capacity. The active Stargate and relevant card effects also had to be included.

During deployment, the player counted the available Action and spent it on eligible cards. A card that cost too much could not be deployed merely because it was in hand. The player could deploy multiple cards if the budget and card restrictions allowed it, but unspent Action disappeared at the end of the Deploy phase.

That separated two useful design questions: how expensive a card was to bring into play, and how much it helped support future deployment. The deck-construction point value added a third question before the game even began: how much of your overall deck budget should that card occupy?

Engagement Made Every Commitment Matter

To Engage a card, you rotated it ninety degrees. That signaled that it had committed to an attack, an ability, or another action. Ordinarily, a card that was already Engaged could not simply be Engaged again to do another job.

Ready returned cards upright so they could act again, subject to any restrictions printed on them. This made a seemingly simple physical action carry much of the game’s tension. A Unit used for a Mission might be unavailable for the later attack. A Unit used for its ability might not be available to defend when the opponent’s turn arrived.

The archived terminology also used Disengage in an unusual way: it canceled an attempted action but left the affected card rotated. It did not mean returning the card upright. That distinction would deserve especially clear presentation in any updated rulebook.

Combat Began with Missions

The three combat stages occurred in a fixed order: Missions, Advanced, then Melee. Only the active player initiated combat.

A Mission created a small confrontation before the main battle. The active player revealed the Mission and, unless its text said otherwise, selected one ready Unit and Engaged it. The opponent then chose whether to accept or decline.

If the opponent accepted, they selected and Engaged a Unit, and the two participants immediately resolved Melee combat under the Mission’s conditions. If the opponent declined, the initiating Unit was treated as unblocked and struck the opponent’s Base, taking the Mission’s text into account.

There was no fixed numerical limit on Missions in one Combat phase. The practical limit was the force you were willing and able to commit. Each Mission could consume another ready Unit and leave fewer options for the main attack or the next defense.

All for Love shows how a specific story could become a mechanical exception. Daniel Jackson and Sha’re must be in play, and the player must control and select Daniel. The card adds all SG-1 Units’ Attack and Defense to Daniel until the end of the turn, but he does not Ready during the player’s next Ready phase.

That is more than a temporary bonus. It offers a dramatic moment now in exchange for a future limitation. The rescue theme becomes a decision about how much to concentrate into one character and how long the resulting commitment lasts.

Advanced Weapons Added Another Layer

Advanced represented a special weapon attack with a stated damage value. Advanced 2 meant one attack dealing two damage, not two separate attacks. A ready Unit used that capability by Engaging, declaring a valid target, and allowing the opponent to respond.

The detailed combat section allowed a Unit or Base as a target, subject to special restrictions. Block let another ready Unit Engage to intercept the Advanced attack and take the damage itself. That made defensive abilities useful even when they did not directly increase the Base’s printed Defense.

The archived Advanced timing chart describes the unblocked damage going to a Base, while the detailed targeting section is broader. I would reconcile those passages before issuing a revised rules edition. This retrospective follows the detailed procedure rather than silently presenting the two descriptions as identical.

An Advanced attack also used up a Unit’s readiness. The decision was not simply whether a weapon could fire, but whether firing it was the best use of that Unit before the Melee stage.

Melee Was About Matching Attackers and Defenders

For the main attack, the active player declared all attackers and Engaged them. In multiplayer, attacks against different opponents had to be declared together. Each defending player then chose ready Units to Engage and paired them with attackers on a one-to-one basis.

An unpaired attacker struck the Base directly. A paired attacker fought its defender, with both sides checking their Attack against the other’s Defense. Both Units could be destroyed. Unless a card said otherwise, a defended attack did not also spill damage through to the Base.

The printed destruction comparison uses greater than, rather than greater than or equal to. For example, an Attack of five exceeds a Defense of three; an Attack of three does not exceed a Defense of three under that wording. An updated edition would need to state the intended tie behavior explicitly, but I have not changed the archived rule for this account.

Damage on Units remained until the end of the current ROE. A Unit that survived one exchange could therefore still be vulnerable to another applicable effect before the Combat phase ended. Base damage reduced the Base’s remaining Defense, tracked separately over the battle.

Abilities That Changed the Matchup

The core keywords made Units useful in different situations rather than relying entirely on larger numbers.

KeywordEffect in the archived rules
Advanced NA special weapon attack dealing N damage, with targeting restrictions where applicable.
BlockEngage a ready Unit to intercept an Advanced attack and take its damage.
Evade NRestrict blocking by Units with Attack no greater than N; avoid their damage when defending; prevent Advanced targeting under the general rule.
First StrikeApply damage before a non-First-Strike opponent; a destroyed opponent does not retaliate.
FlightOrdinary defense requires Flight or a special permission; Advanced weapons need applicable targeting permission.

Passive abilities applied while their source remained in play. Triggered abilities required the appropriate condition and, typically, a ready source that Engaged to use the ability. Phase-specific wording told the player when an effect was available.

The distinction between a keyword and an Attribute was important. A keyword such as Block supplied a defined mechanical capability. An Attribute such as Human or SG-1 did not grant a universal bonus on its own; it became relevant when a card referred to it.

Making a Team Feel Like a Team

Jack O’Neill provides a clear example of a Unit whose importance extends beyond his own combat statistics. He has Block, contributes one Action, and gives all SG-1 Units an additional point of Attack and Defense while he remains in play.

Samantha Carter has a printed cost of three, an Attack of two, and a Defense of two. With Jack’s team bonus, her combat values become three and three before accounting for other effects. A location such as Gate of Earth, Giza can then change the defensive picture again because she is Human.

Teal’c combines Block with a triggered Combat ability: Engage him to choose and Engage up to two Units. That gives his controller a way to affect which Units are available for the rest of combat, while committing Teal’c himself in the process.

Apophis approaches command differently. His card says he cannot be destroyed and cannot attack. Instead, he contributes two Action and can Engage during Combat to choose and Engage up to three Human Units. His printed Attack and Defense are both zero; his purpose is to support the force and interfere with the opponent’s readiness rather than win an ordinary attack comparison.

Those are distinct roles: strengthening a team, participating in a shared identity, controlling readiness, and commanding from behind the fighting. The design used the same Unit framework to support all of them.

Equipment and Transformation

Upgrades attached to eligible cards during deployment and remained with them until removed or their host left play. Unless the card said otherwise, Upgrades were for Units. If the attached Unit was discarded, its Upgrade went with it.

Machine Gun is a straightforward example: it costs one Action, attaches only to a Human Unit, and adds two Attack. A modest reinforcement could become a larger threat without requiring an entirely new Unit card.

Goa’uld Symbiont takes the framework in a different direction. It adds the Goa’uld Attribute and a point each of Attack and Defense, includes control-related wording, and can move during deployment from an attached Jaffa to another valid Jaffa or Human Unit.

The card’s initial attachment restriction and its later control and movement language would benefit from a precise control-change clarification in a revised edition. For the retrospective, the important design idea is visible without inventing an additional procedure: an Upgrade could represent a change in identity and allegiance, not merely a better weapon.

Orders Could Be Powerful—and Difficult to Abandon

Orders described the force’s current instructions. A player deployed an Order during the Deploy phase and had to abide by its objective while it remained active. The rules allowed replacing it with another Order during deployment, or choosing to disobey it.

Disobedience carried a risk. The player revealed the top card of their Reinforcement deck. If it was a Unit, they discarded a number of their in-play Units equal to that revealed Unit’s Action Cost. If it was not a Unit, their force continued following their command. The revealed card was then discarded.

Kill The Rest illustrates both the attraction and the constraint. It requires all Jaffa Units to attack during the player’s Combat phase, while its activated ability can give a chosen Jaffa Unit Advanced 2. The benefit comes with a commitment to aggression, which may leave fewer defenders available afterward.

I like the design question embedded there: what happens when the order that helped build your attack is no longer the order you want to follow? The system made changing course a command decision with consequences.

Quests Could Change What Winning Meant

Quests represented broader objectives with a condition and a result. A player could have only one uncompleted Quest in play at a time. Completed Quest results were treated as permanent rather than being undone simply by discarding the Quest, although other cards could still alter their effects.

Future Queen offers a story-specific alternative to destroying the enemy Base: capture Sha’re with the Goa’uld Symbiont Upgrade on her for five consecutive turns while Daniel Jackson remains in play.

That creates an objective to establish, protect, interrupt, or rescue someone from. It also exposes a rulebook question worth preserving honestly: the Quest uses capture language, while the surviving general rules do not provide a separate, comprehensive capture procedure. The intended story and victory condition are clear; a modern development pass would need to define those interactions precisely.

Events Let the Situation Turn Suddenly

Near Miss is a compact example of an Event doing exactly what its name suggests. During Combat, it selects a Unit destroyed as a result of combat and saves that Unit from destruction. Its printed Action Cost is zero, but the timing condition still matters.

The wider archive includes Events such as Alert, Rescue, Strength in Numbers, Strange Feeling, Dial Gate Address, Change Host, and Cartouches. Their presence shows the intended texture of the game: commanders needed to account for sudden responses and circumstances, not just count opposing Units.

When several Events or abilities interacted, the general rule resolved the last action first and worked backward. An effect still needed a valid source and target. The timing charts explicitly cancel an Event or triggered ability whose target has already been destroyed or discarded.

That made the response windows meaningful. Declaring an action did not guarantee that the board would remain unchanged until its resolution.

Constructing a Force Before the Battle

Deck construction used both card-count restrictions and a total point budget. Each deck had exactly one Base, five Stargates separated for play, and no more than five copies of a particular card unless the card allowed otherwise.

FormatMinimum deck sizeConstruction point ceiling
Standard duel60 cards1,500
Advanced duel60 cards1,750
Three-player Standard80 cards1,750
Four or more players, Standard80 cards2,000

The printed rarity values were also construction values: Common cards could cost zero, five, ten, or fifteen points; Uncommon cards twenty, twenty-five, or thirty; Rare cards thirty-five, forty, or forty-five.

The rulebook suggested making at least half the deck Units, since they provided the military presence needed to fight and defend. That was a recommendation rather than a separate hard minimum.

Alignment added another restriction. The six colors were Pure in blue, Order in green, Neutral in yellow, Chaotic in orange, Evil in red, and Unknown in purple. The compatibility wheel and its examples constrained which alignments could be combined. Order was associated with its neighboring Pure or Neutral options, and Chaotic with Evil or Neutral.

Unknown cards could join a deck, but they could not serve as a bridge to combine otherwise incompatible alignments. Allegiance did not impose a universal single-race restriction: players could mix races when the other construction rules permitted it.

More Than Two Commanders

The system included both dueling and multiplayer formats. Normal play separated opposing deck alignments, with exceptions for Neutral and Unknown. Renegade play allowed commanders to fight independently of that opponent-separation rule while retaining the deck-construction restrictions.

Multiplayer supported teams as well as a free-for-all format the rules called Team Renegade. Attacks against several opponents had to be announced together, and a Mission named its defending opponent unless its text said otherwise.

Players could surrender, and the opponent had to accept that surrender as a victory. Otherwise, eliminated commanders left the battle while the remaining players or teams continued.

A Playable Prototype, with Its Development History Intact

What stands out to me now is how much of the framework was already present: a shared changing location, a deployment economy, readiness as a commitment system, staged combat, asymmetric abilities, and objectives beyond ordinary Base destruction.

The surviving rules also contain the signs of development. Some passages refer to ships where the surrounding system uses Units. The timing charts and detailed Advanced targeting procedure need reconciliation. Capture and control interactions need clearer definitions. The printed greater-than destruction threshold deserves deliberate confirmation rather than an assumed correction.

Those details do not erase the work. They show where the next design pass would have gone. A playable prototype can have a coherent structure while still needing clearer wording, additional testing, and a better presentation of edge cases.

The purpose of preserving this project is to show what I was trying to build and how the pieces fit together, including the questions that remained.

From Stargate to Space Battles—and Beyond

This project belongs near the beginning of the design path that later moved through Space Battles: Star Wars Fan Film Edition and toward Sundered Stars. The names and settings changed, but the larger question continued: could the underlying system support different worlds and still produce interesting choices at the table?

Looking back, I can see the appeal of that question in almost every section of the rules. There is a commander trying to keep a Base alive, a limited force being pulled between competing jobs, and a story trying to emerge from the interaction of cards rather than from a script that tells everyone what happens next.

That is the part I wanted to carry forward: the possibility that a familiar setting could open the door to a design with a life beyond its first pitch.

Interested in the Design?

This is an archive of an unofficial fan-made prototype, not an announced or licensed Stargate product. If the underlying mechanics interest you, or you would like to partner on developing an original game from this broader design journey, get in touch. I would enjoy talking about what these ideas could become.

JOIN THE CONVERSATION

Have a favorite moment or a story of your own? We’d love to hear it!

Leave a Reply