01
Publication, format, and entry context
A veteran player opens an early technical readout and finds a Marauder drawn with the long, predatory silhouette remembered from the nineteen-eighties. A newer book shows the same BattleMech with different armor shapes, different proportions, and a design language that belongs to another generation of artists. The record sheet still says Marauder. The history still says Marauder. Yet one image disappeared from publication for years while the machine itself never left the battlefield. That apparent contradiction is the best entrance into BattleTech continuity, because canon, apocrypha, retcons, and the Unseen are four different problems that fans often compress into one argument.
Canon is the body of officially approved material that defines the shared BattleTech universe. It is not a measure of quality, popularity, realism, or personal affection. A beloved computer game can be apocryphal. An unpopular novel can still be canonical. A fan-created regiment can fit the setting perfectly and remain non-canon. The distinction exists so writers, developers, and players have a common historical map. Without one, Hanse Davion could invade the Capellan Confederation in three incompatible ways, the Clans could arrive in several different years, and every new book would first require an apology to every older adaptation.
BattleTech generally maintains one core continuity for the tabletop setting, its sourcebooks, and its official fiction. That continuity has passed through several publishers and development teams, but it remains cumulative. New material is expected to work with what came before, except where an error is corrected or a deliberate change is made. This does not mean every published sentence carries equal authority. It means the setting has recognized custodians and recognized sources. The rule is less glamorous than a Trial of Possession, but it prevents a forty-year-old fictional history from becoming a box of unrelated parts labeled approximately the same thing.
The most important distinction inside canon is between what happened and what someone in the universe claims happened. Narrative fiction often places the reader close to events through scenes, actions, and character perspectives. When an omniscient narration directly describes a BattleMech falling, that event normally carries strong authority. Sourcebooks frequently present intelligence reports, historical essays, military briefings, intercepted messages, or propaganda written by people inside the setting. The document may be canonical while its author is mistaken, biased, deceptive, or working with incomplete records. The report exists. Its conclusions may still be wrong.
That method is not a loophole created whenever editors need to escape a contradiction. It is part of BattleTech’s character. Great Houses write histories that justify their claims. ComStar classifies information according to institutional interests. Clan accounts interpret events through honor, caste, and political rivalry. Mercenary commands remember contracts in ways that tend to improve their own reputation. Two canonical sources can therefore disagree without requiring two universes. Sometimes one is better informed. Sometimes both describe only part of the event. Sometimes the historian’s most professional conclusion is that everyone involved was lying, though not necessarily about the same thing.
02
The major paths into the setting
Artwork occupies another level. It helps define the machines, uniforms, worlds, and people of BattleTech, but an illustration is not always a perfect engineering drawing or courtroom exhibit. Artists emphasize different features. Printing limitations change details. A BattleMech may appear taller, wider, or more human-shaped from one publication to another. When art conflicts with a clear written description or a narrated event, the prose usually carries more weight. This matters enormously to the Unseen. A machine can remain canonical even when a particular picture of it is withdrawn, replaced, or reinterpreted. The portrait can change without the soldier being removed from the regiment.
Official and canonical are therefore not synonyms. A company may hold a valid license to make a computer game, television series, miniature, or regional publication while lacking authority to alter the central tabletop timeline. The license answers whether the product may legally use BattleTech. Canon status answers whether future core publications must treat its new facts as established history. Those are different questions. This arrangement gives adaptations room to function in their own medium without forcing every interface choice, dramatic shortcut, or marketing decision into the sourcebooks. It also explains why an official logo on the cover settles the legal question while leaving the historical one open.
Apocrypha is different. In BattleTech usage, apocryphal material is usually official and licensed, but it does not possess full authority over the core continuity. Many computer games, console games, comics, magazines, and the animated television series fall into this category. They are not fan fiction, counterfeit products, or automatically false. They were created to tell BattleTech stories, often by people working closely with the franchise. They may use canonical wars, factions, characters, and machines. Their limitation is that another canonical source does not have to obey every mission, statistic, visual choice, or plot detail they introduced.
Computer games demonstrate why this category is useful. A game must let the player make decisions, win battles, customize machines, and sometimes reload after converting a proud command into an unusually expensive debris field. Those choices cannot all become one official history. Game balance also changes weapons, travel, repair, and force sizes to create an enjoyable experience. BattleTech therefore often accepts the broad outline of a game’s story without treating the player’s exact campaign as documentary evidence. A named hero, recovered artifact, liberated world, or military operation may enter canon later, while the exact lance composition and sequence of missions remain specific to the game.
The Aurigan Coalition provides a clear modern example. It was created for the BattleTech computer game developed by Harebrained Schemes. The game itself remained apocryphal, including the variable mercenary campaign experienced by each player. A later official sourcebook, House Arano: The Aurigan Coalition, brought the realm, major characters, and broad history into core continuity. That did not retroactively make every random contract, customized BattleMech, or tactical decision canonical. Canonization is selective. A later source can adopt a person, place, or event without absorbing the entire product that first introduced it.
03
Military themes and representations
The animated series offers an even more BattleTech solution. The television show is not treated as a literal canonical record of the Clan Invasion. Its characters and the First Somerset Strikers were incorporated into canonical material, while the series itself was described inside the universe as a dramatized holovid based loosely on their exploits. The exaggerated action, inaccurate equipment, and heroic simplifications become features of an in-universe production rather than facts the setting must defend. The cartoon happened in the real world as an adaptation. In the fictional world, something resembling it happened as propaganda. Bureaucracy occasionally produces elegance by accident.
Non-canon and fan-created material occupy a separate category. A home campaign, custom BattleMech, alternate timeline, or fan novel can be excellent and fully compatible with the setting, but it does not become official because many players enjoy it. The same applies to a wiki. A reference site can carefully summarize canonical publications, yet the site itself is not a source of canon. It is a map assembled from sources. This distinction protects both sides. Official continuity remains identifiable, while players remain free to modify it at their own tables without submitting a request through ComStar’s Department of Recreational Historical Compliance.
Retcon is short for retroactive continuity. It occurs when later material changes, replaces, or reinterprets an established fact about earlier events. The word is often used too broadly. Adding the name of a battalion that fought in a battle is not necessarily a retcon if no earlier source said it was absent. Describing an undocumented colony in a sparsely mapped region may simply fill an empty space. A new BattleMech variant is not a retcon merely because an older technical readout did not list it. Continuity can expand without contradicting itself. Silence is not always a prohibition.
A true correction can be very small. An early technical readout once assigned the Zeus a development history that placed it before the Mackie and before the industrial circumstances required to build it. Later material corrected the error. The Zeus did not cease to exist, and the entire book did not become useless. One claim was superseded because it could not fit the setting’s established chronology. BattleTech has accumulated thousands of dates, worlds, units, manufacturers, family relationships, and equipment descriptions. Some corrections are inevitable. The remarkable achievement is not perfect consistency. It is that the repair crew usually knows which panel must be removed.
Errata, retcons, and unreliable narration should not be confused. Errata corrects mistakes in a published product, including rules, numbers, names, maps, or wording. A retcon changes the accepted fictional history, even if the change is made to repair an old mistake. An unreliable source is different again. If a Capellan intelligence report misidentifies a regiment and a later novel reveals the actual unit, the setting may not have changed at all. The report was always wrong inside the story. The later source has changed the reader’s understanding, not necessarily the event. That distinction lets BattleTech revise knowledge without casually rewriting history.
04
Continuity, terminology, and source status
When canonical sources conflict, context matters. Directly narrated fiction generally outranks an in-universe report about the same event, because the report may contain error or propaganda. Even fiction must be read carefully. A character’s belief is canonical as a belief, not automatic proof that the belief is correct. A message quoted inside a novel may be forged. A battlefield witness may misunderstand what was seen. Among comparable sources, newer material often clarifies or supersedes older material, especially when the later publication was designed to resolve the conflict. Canon is therefore not a simple stack in which the newest book crushes everything beneath it. It is an evidence problem.
BattleTech also uses canonical rumors. A sourcebook can establish that people inside the universe tell a story without confirming that the story is true. Reports of hidden colonies, secret weapons, lost commands, and conspiracies may be presented with competing explanations. The rumor itself is canon. Its solution may remain deliberately open. This is particularly useful in a setting built around damaged archives, state propaganda, ComStar secrecy, and centuries of war. Not every mystery requires a final answer, and not every ambiguity is an editorial failure. Sometimes uncertainty is the subject.
The Unseen belongs to none of those categories. It is not another word for apocryphal, retconned, obsolete, or forbidden inside the fictional universe. The term arose from a real-world publishing and licensing problem involving the visual designs used for several early BattleMechs. Those machines remained part of BattleTech history. Their names, battlefield roles, technical characteristics, pilots, and appearances in fiction continued. What became difficult to publish were particular images and miniatures associated with them. The BattleMechs were not destroyed by a secret Successor State operation. Their artwork encountered intellectual property law, which is harder to defeat with an autocannon than the rules might suggest.
When Battledroids appeared in nineteen eighty-four, before the game was renamed BattleTech, FASA licensed a collection of existing Japanese mecha images through Twentieth Century Imports. The source designs came from Super Dimension Fortress Macross, Fang of the Sun Dougram, and Crusher Joe. They were adapted to represent machines including the Wasp, Stinger, Phoenix Hawk, Warhammer, Marauder, Rifleman, Archer, Griffin, Shadow Hawk, Wolverine, and several others. These images helped give early BattleTech a distinctive visual identity, even though the machines had originated in unrelated animated stories with different settings and purposes.
The legal chain behind those images proved far less sturdy than a BattleMech’s internal structure. Rights claims involving Macross imagery, Harmony Gold, FASA, and other companies produced years of dispute. A settlement in the nineteen-nineties led FASA to stop using a group of contested images. The company also withdrew additional externally sourced designs to avoid further uncertainty. Fans began calling the affected machines the Unseen because familiar illustrations disappeared from new products. The term described absence from publication, not absence from history. A Warhammer could still fight in the year thirty twenty-five even when a new book could not show the classic picture readers associated with it.
05
How the framework changes by format or era
This distinction is essential. The Unseen BattleMechs did not become non-canon. Their original visual depictions became unavailable for normal use, while the underlying BattleTech designs continued to exist. Record sheets, written references, and older products remained part of the game’s history. Players could still field the machines, and existing miniatures did not suddenly become evidence in a criminal investigation. The practical problem was new production. Publishers needed art they could safely print, manufacturers needed miniatures they could sell, and writers had to describe famous machines that current books were reluctant to illustrate.
The absence affected perception. Several Unseen designs were among the most recognizable and common BattleMechs of the Succession Wars. When they vanished from new artwork, younger players could reasonably conclude that these machines were rare, obsolete, or no longer important. Historical scenes became visually distorted because artists could not freely populate them with designs that the lore said should be present. This was not an intentional in-universe change, but it shaped how the universe looked. Publishing constraints can influence historical memory even when the fictional history remains officially unchanged.
Project Phoenix offered one solution in the early two-thousands. New artwork and upgraded configurations reimagined many affected BattleMechs for the in-universe year thirty sixty-seven. These designs were often called Reseen. They were not initially presented as proof that every older machine had always looked exactly like the new version. Instead, the book framed them as later evolutions and rebuilds associated with Vicore Industries and wider modernization efforts. That approach solved two problems at once. The publisher gained original designs it could use, while the setting explained why familiar BattleMechs appeared in substantially altered forms centuries after their introduction.
The solution was clever but incomplete. Fans who wanted to depict the Succession Wars still needed visual representations of the classic-era machines, not only later upgrades. Beginning in the mid twenty-tens, BattleTech introduced new original artwork for many famous designs, keeping recognizable features while establishing a distinct modern visual language. The Warhammer still carried its shoulder-mounted missile rack and arm weapons. The Marauder retained its forward-canted posture and heavy gun arms. The Rifleman remained unmistakably an anti-aircraft machine with paired arm cannon. The new illustrations evoked the roles and silhouettes players remembered without simply reproducing the earlier anime-derived images.
This later artwork is sometimes called Reseen, Newseen, or redesigned Unseen, depending on the speaker and the specific generation of art. The vocabulary is less standardized than the machines’ record sheets. What matters is the distinction between an in-universe design and its real-world representation. A BattleMech can have one canonical service history and several published visual interpretations. Some later images may replace older art for current products. Others represent later variants or rebuild programs. The reader must ask whether the publication is changing the machine’s history, changing its appearance, or merely choosing a new way to depict the same established object.
06
Military historian’s assessment
The Unseen story is sometimes described as a retcon, but that is only partly accurate. Project Phoenix created genuine later-era redesigns inside the setting, which expanded continuity. New classic-era artwork can function as a revised visual representation of machines that were always present. Neither requires erasing the battles those machines fought. A Marauder piloted by Grayson Carlyle does not become a different historical machine because a later artist redraws its armor. Visual continuity changed more dramatically than narrative continuity. The legal dispute altered what audiences could see, while the fictional timeline largely carried on as though the lawyers had never discovered jump travel.
A practical reader can navigate BattleTech continuity with four questions. First, what kind of source is this: canonical publication, licensed adaptation, fan work, or reference summary? Second, is the statement direct narration, an in-universe report, a character’s belief, or a rumor? Third, has later canonical material confirmed, corrected, or replaced it? Fourth, is the apparent contradiction about an event, a game mechanic, or only an image? Those questions resolve most disputes before anyone needs to mobilize a regiment. They also prevent the common mistake of treating every difference as a separate universe.
Canon should not be used as a weapon against play. A group can field an old Unseen miniature, use a unit from a computer game, adopt a fan-created planet, or rewrite the Clan Invasion. The tabletop has always allowed alternate outcomes. The useful habit is simply to label the choice. Core continuity provides the shared starting point. Apocrypha provides official possibilities and adaptations. Fanon provides individual invention. Retcons record changes to the shared history. None of those categories determines whether a campaign is enjoyable. They determine only what another reader can safely assume without attending the planning meeting.
The endurance of BattleTech depends partly on this controlled flexibility. The setting has one broad historical continuity, but it allows biased documents, incomplete archives, selective canonization, corrected errors, and evolving art. That structure lets new creators add detail without discarding four decades of accumulated history. It also lets the franchise survive real-world changes in publishers, licenses, technology, and audience expectations. Continuity is maintained less like a sacred tablet and more like a BattleMech after a long campaign: inspected, patched, occasionally rebuilt, and still recognizable when it walks out of the bay.
Canon tells us which history the shared universe recognizes. Apocrypha marks official stories that may inform that history without controlling it. Retcons describe the moments when the recognized account is deliberately changed. The Unseen describes a visual and legal problem that removed famous images without removing the BattleMechs they represented. The old Marauder in the veteran player’s technical readout and the redesigned Marauder in a new box are therefore not proof that BattleTech has lost its past. They are evidence of how carefully the setting has carried that past through circumstances its original designers could not have predicted.