How It All Started/Ended Up The whole shebang begins with me doing something incredibly stupid and trying to chain most of my old games together into one plot in chronological order. Or, in short, it begins with what was
the Prince of Toast. The four PCs in that game were originally supposed to end the world and play a heavily modded SBURB games stolen from the pirates. Due to that game's unfortunate demise, I carried the plot forward in my head to where the four of them managed to prevent fate from making them play the game, leading to the
reboot - in which, once again, the point was to end the world. Another unfortunate game demise later, and I carried the plot even further - this time, a bunch of people managed to break into the deprecated remains of the unused session of the original four and "complete" it in the sense that Frankenstein "completed" his monster. As a result, natural lifeforms didn't develop, and the players who "won" the game (sans a couple who decided to do other things) made robots instead. Fast forward a few thousand years, and you've got
Automaton - where a lonely robot looking for his arm finds a strange object with the code for SREPAIR.EXE written on it. Another game died, and another plot continued itself - the robot and a group of his compatriots/acquaintances managed to get in and fix the session, and then created an organic race which looked much like themselves. That's where TE's species comes from. These guys then manage to play SBURB, shenanigans occur, and another universe is created as the setting of
Guardians of the Artifacts. That's where the chain sort of ends, and where I decide to let the plot thread finally die. That is, of course, besides the few dozen loose ends I like to call characters - because for all four or five sessions that I mentioned here, each one has about eight characters. Only one of those sessions contained anyone you guys give a shit about, so MOVING RIGHT ALONG.
TB's Story and the Code Aspectbegins with SUBURB - Freeform's SBURB playoff. Of course, due to various deviations, I had to create some form of Deux Es Machina to keep him from playing with the SUBURB characters and thus probably dying a terrible death. For this, I made up the Code Bug. Basically, the Code aspect is not an aspect native to the game itself - it's a sort of antivirus/bughunter created by the Automaton session. It operates as a form of override, assigning a player a new session, class, and of course the Code aspect. Of course, the Automaton players didn't think about how incredibly overpowered it would be to give a thirteen-year-old the power to bend reality - especially if it's gained by copying other powers - so once he gets the Cord of Code title, TB promptly goes nuts with it and messes up his session something fierce, resulting in his involuntary expulsion by way of a teammate's cannon. After this, he has a few adventures in the Void, kills some suckers/weak horrorterrors, nothing major. One of the misadventures he has is the breaking of the HSRPG-Scratch session, but more on that later. After his series of misadventures, his timeline meets up with TC's. (More on TC later.) The two generally fall in silly teenager love, and eventually run into the Big Bads of this whole thing - the Lord of Void and the Muse of Rage. (Again, more on them later.) They get split up in the ensuing fight, with TB raging his way through (and copying the power of) a bunch of horrorterrors. This is where he finds CA. Shortly thereafter, he realizes that he's been a bit of a dick and wipes his memory, leaving a few rudimentary things like how to eat behind. TB and CA then go on adventures, being silly and breaking things on accident. They run into and rescue TE, then eventually run into the HSRPG session where they try not to break everything on accident and, of course, break everything on accident. Presumably, TB starts remembering everything, and eventually remembers enough to access the reserves of horrorterror power he's got, and presumably at that point he goes grimdark and becomes some sort of miniboss, Deux Es Machina, or whatever plot device would have been appropriate.
CA's Storywas pretty underdeveloped. I wanted him to sort of be the Eridan of his session, only he was an asshole entirely by choice instead of by title. He was removed from the session because of a very clever yellowblood's plot to lure one of the few enemies that was creating in the Scratching process over to his Quest Bed, resulting in CA's subsequent godtiering and departure from his session. Of course, having just godtiered, CA was left with no weaponry against the large number of horrorterrors, and was subsequently rescued by TB before getting eaten. They go on misadventures and break things.
Oh, and the thing CA wanted to give Alex was his pool-ball set as a sort of "I feel you bro" thing, given that CA's lusus-sprite was decapitated shortly after entering the session.
Yeah I didn't really develop CA very much at all.
TE's Storywas relatively short. He played in his session, used a cruxite weapon, and then got booted from his session. The rest is explained in pesterlogs - he's sort of exactly the character he appears to be on the outside. I was pretty much going to wait things out and see if he'd develop enough to kill his other self, but that didn't really happen.
CC's Storywas even shorter, and explained entirely within the game itself.
TC's StoryOh boy, TC's story. Where do I even start.
First off, this TC is not Apple's character. This TC is teaserCode, the first of the Code players - a member of TE and CC's session. She was "the bitch with the patchword land" that CC refers to. She was left the session shortly after the fight with the Black King just because she was sick of her sessionmates. She wandered the Void for a while, ran into TB, and the two had a short-lived teenage romance before getting split up by the Lord of Void and Muse of Rage. She went on to find Earth and give TB the Code Bug, resulting in his session-jump. Eventually, she manages to find her way back to her original session and rejoins the worldbuilding, only to find that her teammates rebuilt the world without her. Dissatisfied, she decides to do a force reset and gets rid of the teammates who disapprove of the idea. This is the setting of
Guardians of the Artifacts - where the players aren't guarding artifacts in hope of preventing the world from being destroyed as they think, they're protecting what amounts to a series of world-sized timebombs.
Anyways, that game never really ended, so that's where TC's story cuts off.
fa's Story and the Noise Aspectand by fa, I'm referring to the fa in the
Prince of Toast reboot. In some offscreen backstory, she's accused of murdering her younger brother. Claiming innocence, she basically becomes a fugitive trying to end the world out of spite. When she manages to do so, she gains the title of Heir of Noise. Now a diversion for a second to explain the Noise aspect. Noise players are essentially the polar opposite of Code players, and only show up as a result of large amounts of errors within the game itself - such as the wrong person playing. Anyways, being a Noise player, she screws her own session up before being forcibly removed by her teammates. She then wanders the void for a while before allying with the Lord of Void, being a minor player in the split of TB and TC before getting killed in the path of whomever ends up murderating the Lord of Void.
The Lord of Void and the Muse of Rageare the Big Bads of this whole mess. Essentially, their session was created due to TC's attempted world-destruction, and was broken as hell. These two decided "screw that, we're gonna do our own thing" and left to the Void. While there, the Lord of Void ends up fulfilling his title by gathering a small army of lost players, dreamghosts, and the occasional lesser horrorterror to do his bidding. Shortly afterward, they run into TB and TC, and, recognizing TC's species from their deitic pantheon, lose their collective shit, swear revenge, and then take it by way of splitting the couple up and giving them a few scars. I didn't really have any plans for them afterwards except for maybe their eventual comeuppance.
The HSRPG Scratch-Sessionwas something I came up with on the tail end of the rest of this nonsense. Basically, I needed someone (or someones) to beat up the Lord of Void and Muse of Rage so I'd have a good reason for TC managing to avoid the Lord of Void for so long. Essentially, the idea was that TB and CA would show up, accidentally everything, and then run away, leaving the players to either jump into the Void and find ADVENTURE or try to Scratch yet again. This didn't really go very far in terms of ideas just because I wanted everyone's guardians to remain true to their own character - and I couldn't use those characters without knowing what the people playing them would have had them do.
I think that's it - if you have any questions or want me to review something that I skimmed over as "covered in the thread" or "irrelevant to the main plotline", feel free to bug me about it.
