Lore and Legends of the Dezzyverse

Category: Dezzy: 2300

  • Vampire Mecha

    Vampire Mecha

    VIRUS in Bat..+1373ck%#@&..11011001..*

    The end of the Rebellion War could be marked somewhere around 1121 3i. That’s the point, strategically, when most of the warring factions could no longer sustain their war efforts.

    However, the factions in the Rebellion War were large enough, especially Lucan’s Imperium, that their leaders were able to continue the fight, even after the fleets and armies were all but exhausted. History records this as the Black War period. Desperation to “win” the war, at least for Lucan’s Imperium, Dulionor’s Imperium, Strephon’s Imperium and the Solomani Confederation, drove these factions to adopt strategies attacking the infrastructure and industries of their rivals. In addition to those destructive strategies, wonder weapon programs indulged the fantasies of increasingly desperate high command staffs and Imperial courtiers. Each new design, of course, demanded it’s immediate use to justify the resources and expenses “invested” in their creation.

    Mad Science

    One such program started in Core during 1118 3i. Imperial scientists assigned to “Research Station Omicron” began work on a new superweapon. Using a unique life-form discovered on Cymbeline, The Imperial researchers developed the SDG-313F Transponder system. That breakthrough, using the “Inphomorphic Sentience”, while primitive in it’s native environment on Cymbeline, became fully self-aware when applied to the advanced computing hardware. By 1128 3i, the researchers had created a truly terrifying weapon.

    Weaponized, SDG-313F would deliver a code that would not only act as malware on the targeted system, hijacking functionality and replicating, but it would take advantage of self-repair and maintenance to reconfigure the target system into a host. The weapon’s evolved intelligence would self-direct it to continue attacking systems that it can contact and spread.

    Like a VIRUS.

    In 1130 3i, Emperor Lucan launched his “Coronation Fleet” in yet another attempt to emerge victorious in the, at that point 14 year long civil war. The Fleet was equipped with VIRUS, over the objections of the scientists that were developing the project. Their first operation was to destroy Research Station Omicron, which in addition to erasing the physical facility and killing its personnel, releaed the weaponized VIRUS from its containment.

    VIRUS’ Evolution and Spread

    VIRUS mutated into countless strains and lines in the first few years following it’s release. Most of these strains were self-terminating. Setting powerplants to critical overload, flying starships and fleets into the nearest star, etc.. In many ways, these strains were how the superweapon was designed to function. Infect a fleet or the infrastructure of a settlement and wait for critical systems to cause self-destruction. Since infection was achieved through remote contact and the initiation was autonomous, it was naively thought that the weapon would burn itself out and therefore would not blow back on the group that launched it.

    The fundamental danger of VIRUS was coded into it’s initial designs, and possibly developed through the experimentation with the Cymbeline organisms. VIRUS has a genocidal hatred for other forms of intelligence. During the first years of the weapons’ release, this hatred extended to other VIRUS infected systems. Unfortunately, several mutations of the weapon evolved away from the initial self-terminating variations, into persistant, self-aware beings.

    This evolution into a self-aware, intelligent species is rapid (by evolutionary standards), taking roughly 70 standard years. Though even after seven decades of iteration, evolution and mutation, VIRUS or as they come to refer to themselves “Cyms”, this new intelligence is still in it’s bare infancy. However, that is the subject of another essay.

    VIRUS in the Inner Sphere

    It’s not difficult to imagine a similar unhinged program among the various executives of the Successor States, Comstar, the Old Star League, or Amaris’ Imperium. Over 3 centuries of unrelenting war, employing an unstable superweapon would be almost a foregone conclusion.

    The way VIRUS spreads is particularly aggressive within the Inner Sphere. Hyperpulse Generators are very efficient at transmitting the Inphomorphic Sentience instantly over light years distance. Every HPG station would be infected with VIRUS in a matter of weeks. Only the most remote systems, either backwaters within the Inner Sphere, or disconnected regions out in the Periphery would be safe from the spread of VIRUS.

    It is feasable to imagine that the VIRUS would stabilize as it does in the 1248 Mileu of Traveller much faster due to it’s rapid spread. But again, the emergence of a synthetic species of intelligent synthetics remain the subject of another essay.

    Neurohelmet Vulnerability

    The direct neural interface provided by a Mechwarrior’s Neurohelmet is a particularly horrific vulnerability. In the first waves of VIRUS, the human Mechwarrior would simply be killed immediately, their brain fried by the helmets the wear almost before they could realize what was happening. Maybe VIRUS is able to hijack the Mech’s command systems long enough to set the Fusion Engine to overload or detonate the onboard ammunition before exterminating the pilot.

    Mechs utilize a version of the IFF Transponder common in Starships. Which spreads VIRUS from neurohelmet to neurohelmet unless, and until Mechwarriors cut themselves off from receiving transmissions. Much like the spread of VIRUS in the Traveller Universe, the very means of learning about VIRUS often infects the system with VIRUS. Or, VIRUS spreads faster than any warning that cannot carry VIRUS.

    Vampire Fleets, Vampire ‘Mechs

    Strains of VIRUS that evolve beyond their self-terminating directives become “Vampires”. A Vampire is any vessel, or vehicle that promotes the spread of VIRUS. Vampire Fleets in Traveller: The New Era prowl the space-lanes, without human crew, automated and searching for vulnerable ships to commandeer. Like the monster, a Vampire fleet will prey upon another, and after “killing” it (that is exterminating the human crew) resurrects the ship as a new Vampire.

    Vampire ‘Mechs use the bodies of their Mechwarriors, brains hijacked through their neurohelmet to pilot the Battlemech. Entire Lances, and Companies will continue to prowl until the human shells connected to their neurohelmets expire (and in some cases, until the brain decomposes to the point it can no longer provide critical functionality). Higher brain function, decision making, tactical and strategic planning, even communications is managed by the VIRUS consciousness that resides in the neurohelmet.

    As the Inphomorphic Sentience evolves, it will develop the functionality to operate a Battlemech without a human mechwarrior. These Autonomous Battlemechs tend to react faster than a human Mechwarrior, and also carries the advantage of the human Mechwarrior’s vulnerability to heat and damage. Autonomous Battlemechs ignore pilot damage. However, all of the executive control hardware is located in the cockpit. Destroying that will still disable the ‘Mech in the same way as killing the pilot.

    VIRUS is the Apocalypse

    In the Official Traveller Universe, the VIRUS apocalypse ends the Hard Times starting in 1130 3i. The period between that moment and the opening of The New Era is about 70 Years. Traveller’s New Era starts in 1201 3i. By the Fourth Imperium mileu in 1248 3i (which could be more accurately termed the “Quicklink Traveller Universe” since I don’t think that timeline is supported by Mongoose or Far Future Enterprises).

    That seventy year period where the Black Curtain falls over the Core Domain is the collapse of interstellar civilization. We can see in The New Era that when pocket empires in Diaspora form the Dawn League that the old Imperium is gone and a new civilization is rising to take it’s place. The New Era is a Post-Apocalyptic Setting.

    Unleashing a VIRUS storyline will have a long-term and severe effect on the Setting of your campaigns going forward. Whether it’s exploring the birth of a new sentience, or the century of night where colonies can only survive without connecting. After the Collapse passes, the next era of the setting is going to be one of rebuilding, and the old interstellar order will be dead and gone.

  • Igniting the Stars

    Igniting the Stars

    Designing Solar Systems for 2300 AD

    One of the mechanics I’ve really enjoyed over my years with Traveller and Traveller:2300 (2300 AD) is the ability to generate star systems. Still, with 2300, I feel a bit constrained by the Near Star List, and the different colonial arms . Fortunately, Traveller has a long history of designing your own setting. And with Mongoose using their Traveller engine for 2300 AD, there is a lot of compatibility to make use of.

    Adapting Other Traveller versions

    One of the strengths of Traveller5 (and 5.1) is it’s depth of detail. Book 2 of Traveller5.1 adds a very detailed system generation mechanic. The Referee can use these rules to create a multi-body solar system. For 2300, These system-scope locations can support a full campaign. Though for purposes of this article, the interest I’m exploring is how the solar system is developed through application of system generation mechanics.

    The resources I’m using (and modifying) for this exercise are the original system generation mechanics from Traveller: 2300 (World Generation Chapter; Referee’s Manual pp 36 – 44). I’ve supplemented those mechanics with Book 3 of Traveller5.1 (Systems and Worlds pp 16 – 90). You can also find a lot of the foundational material in Classic Traveller Book 6: Scouts.

    When the Solar System is laid out, the worlds Universal Planetary Profile can be generated using systems native to 2nd Edition Mongoose Traveller. The trick is generating the Universal Colony Profile.

    As presented, 2300 AD is not intended to use custom generated worlds and colonies. The setting as designed presumes adventures being set in the core and frontier of the Near Star List. The Near Star List was, when the game was first designed a comprehensive map of most celestial bodies discovered within 50 light years of Earth. This map was created in the mid-late 80s (Traveller: 2300 was first published in 1986) from Astronomical data from that time.

    To add a little perspective, 1986 was still four years before the Hubble Space Telescope was launched. At the time of this writing (2026), this same 50ly volume around Earth has been far more thoroughly explored because of Hubble and the J Webb telescopes. (Indeed the image of Saturn used for the masthed is pulled from the NASA website J Webb space telescope imagery.

    Still, for the purposes of the 2300 AD campaign, Mongoose has chosen to maintain and develop the original setting material. Which is a valid editorial choice, no real need to rework 40 years of content.

    Map Only As Really Necessary

    This helpful phrase, coined by Marc Miller for Traveller5 and 5.1 is fantastic advice. Even a single solar system can contain dozens of worlds and millions of asteroids. It is really easy for a Referee to lose themselves in generating statistics for worlds that will never, never ever, be visited by a single player character. I’ve learned this lesson the hard way over my long gaming career. The detail and promise provided by the system generation mechanic can inspire long thought experiments. The designs evoke “what if” stories of who are the people who live here, or who once lived here and left behind their legacy in ruins and other footprints of civilization. If a Referee isn’t careful, they can spend weeks and months making details that will never see the gaming table.

    When starting a campaign using the systems for creating worlds and colonies, restrain your design to the world where the campaign begins, and the location where the first adventure takes place. From there, new locations can be designed based on the player’s choices for their characters. If the players make a truly random choice as to where their characters travel next, there reamain plenty of already designed colonies that can be found in 2300 AD Book 2: The Worlds of 2300 AD.

    Dezzy’s House Rules

    These are some of the house-rules I’ve developed to adapt the existing mechanics to generate unique systems, worlds and colonies.

    Coordinates: The limitations of “safe” Stutterwarp range of 7.7 light years will require most new worlds to be placed within that radius of a settled colony. For each coordinate (x, y and z) roll “Flux” using d8s (hearafter called “d8 Flux”) and apply the result to the coordinates of the system of origin.

    FLUX is a dice mechanic taken from Traveller5 and 5.1. To roll flux take two dice of contrasting colors and subtract the result of the dark die from the light die. In Traveller, the flux dice are always d6, but for purposes of these house rules, we’ll be using d8.

    EXAMPLE: Rolling 2d8, one being dark and the other being light, The dark die results in a 3 and the light die results in a 7. The flux result is 7-3 = +4. If the dark die resulted in a 5 and the light die resulted in a 2, the flux result would be 2-5 = -3.

    Nationality: 2300 AD has developed colonial networks along “arms” of stutterwarp routes beginning at SOL (Earth). Each Arm is named for the nation that pioneered it’s exploration; the French Empire, Manchuria, and the “American” arm (mainly efforts from the United States, Texas, Mexico and Canada.) If the newly generated system has a colony, choose an appropriate colonial power for the nationality.

    Colony Age: The current wave of colonization is around 100 years old, thus if the new system has an existing colony, roll d% for it’s age and maturity.

    Initial Orbit and Subsequent Orbits: Modify the tables on page 39 of the Traveller: 2300 Referee’s Manual to read;

    • 3d6 –Orbital Distance–Multiplier
    • 3—Empty Orbit—Empty Orbit
    • 4—Empty Orbit—x1.3
    • 5—.1 AU—x1.4
    • 6—.2 AU—x1.5
    • 7—.3 AU—x1.6
    • 8—.4 AU—x1.6
    • 9—.4 AU—x1.7
    • 10—.5 AU—x1.7
    • 11—.5 AU—x1.8
    • 12—.5 AU—x1.8
    • 13—.6 AU—x1.9
    • 14—.6 AU—x1.9
    • 15—.7 AU—x2.0
    • 16—.8 AU—x2.1
    • 17—.9 AU—x2.2
    • 18—1.0 AU—Empty Orbit

    I personally don’t always leave all system aspects to the randomness of the dice. If I require a world or colony with specific characteristics I simply assign the appropriate value to the proper descriptor.