EXTENSION — Timeline of Events

1

Beginnings

It all started when I installed an extension called Roblox URL Launcher off the Chrome Web Store. I had it for a month until one day seven of my games all got published at the same time. I was wondering what it was, so I joined the games with my friends, and inside we found our first anomalies: Checksum, Coiler, Meat Cube. Checking Studio gave us nothing, but I had a device logged in from Bristol. I was hacked, you could put it into words, but me and my friends had no clue what this was presenting us, and it only got deeper.

Anomalies: Checksum • Coiler • Meat CubeLocation: Bristol (device)

2

The Webserver

So we pinpointed from error codes in the F9 console that it was pulling stuff from a web server to inject code into my games. We found the website “ordents.xyz” (real site, go look it up!). On ordents we believe every anomaly is stored there—all the code to inject into my game. So do I want to let this intruder on my account? Not until I can trust him.

F9 console errorsordents.xyz

3

Alt Account

I made an alt account and made a game on there and waited. After a while one of the speed coil tools came alive; I didn’t even have code for this in Studio. Some anomalies spawned in, and we got banned from the game. Yes, I’m getting banned from my own game. So I made another two games on my alt, which presented us with more anomalies, where we first met nullOrd and motherOrd. After that, I decided to let it back onto my main.

Alt testbedFirst: nullOrd • motherOrd

4

Main Anomalies

We met loads of our first anomalies when they began spawning in my games like “Dreaded Salvage.” We got more lore from nullOrd that we need a product key of some sorts, but we don’t know what it means. We also met droneOrd and pulseOrd for the first time and many more anomalies.

Game: Dreaded SalvagedroneOrdpulseOrd

5

Group Hunt

Group Hunt, as I’m calling it, was mainly small, but it was when we had loads of people in the game; anomalies were spawning a lot more frequently. Eventually, everyone left and the next event happened.

High player countSpawn frequency ↑

6

DamageOrd Raid

DamageOrd Raid happened when 20 damageOrds (DOs, I’ll name them for short) appeared in the sky; they then started firing lasers at us, killing us. We tried to delete them but our BTools kept getting removed. Trying the F9 console would hit me with a heavy lag spike, and it disabled our admin too. We were relying on my game’s built-in admin commands as it was a weapon PvP game. Spawning “RPG” tools, we managed to take out each DO, and then they exploded into a white fire and faded out. We were banned from the game shortly after.

~20 damageOrdsLasersBTools removedBan

7

Aftermath

Aftermath, as I’m calling it, is when we were playing my other games like Poppers and Rafted to search for anomalies; we met a few cool, unique ones here! We got banned from Poppers for some odd reason. I also want to specify each time we’re banned, the kick message is these random coordinates. Anyway, we played Rafted after, where we first met the doomOrd—a huge damageOrd that would tear the map apart piece by piece upon firing its lasers. And we were banned.

PoppersRaftedKick msg: coordinates

8

Nabrus

Nabrus happened when we got unbanned from Dreaded Salvage and met a blocky anomaly who was being tortured by Lubule. Lubule, also known as the motherOrd, is the core of the anomalies. Lubule has been spawning the detailed and friendly anomalies, whereas “Jaster” has been spawning the evil anomalies built from map parts. Jaster wants to become the new core, as Lubule is currently the main core, and when one of Lubule’s anomalies die, it drains her stability. Jaster is sending anomalies out to kill Lubule’s, so he can be the current core. And the HOST is the guy who created the cores and runs all of this. Nabrus was eventually killed by Lubule, as he was made by Jaster and Lubule saw this as a threat. Later after, we were banned from Dreaded Salvage again.

motherOrd: LubuleCore conflict: Jaster

9

Webhooks

Webhooks is when we first made communication to anomalies via external means. We were in Rafted when we saw a message “FAILURE TO IMPORT MP4!”, so I made a webhook to a Discord server and Rafted so it could send videos through my webhook; however, anomalies began communicating with us through this webhook too, and sending us videos. The HOST himself communicated via the webhook and told us he’s decreasing the anomaly spawn-rate.

Discord webhookVideo relay

10

Burnout

We were all pretty burnt out, and no anomalies were spawning, so we were just chilling in Dreaded Salvage doing nothing. Pretty much nothing happened here—we saw some cool anomalies—until nullOrd came down and told us doomOrd was coming.

Low activityWarning: doomOrd

11

Battle of the DoomOrd

The map tinted red, and weird ambience started playing. PulseOrds came down and tried to protect us but got taken out by lasers from doomOrd, we think. Then this song started playing (peak battle song) and doomOrd appeared. It was huge and had a burning orange fire and would shoot rapid lasers that killed us but also unanchored and blasted everything on the map. We fought doomOrd for ages; it was smart and took away our BTools, disabled F9 again too, but we were still able to spawn in gears. Using the Periastron, we hit it, and it did this weird attack that blew up EVERYTHING in Workspace, and doomOrd disabled our respawns, so if we were killed by it we couldn’t respawn. We were being hammered by it until I clutched with the Firebrand and killed it, where it exploded and left a white flame. After this, nullOrd thanked us and let us answer a few questions. It told us to save Lubule we need her product key, which is at coordinates we found from an MP3 spectrogram in the webhook. And Jaster’s product key is at the coordinates we get from being banned. We have to stop Jaster somehow. We were also told Jaster made doomOrd to kill us, and Jaster has a stronger anomaly it made called “809”.

doomOrd defeatedWhite flameKeys via coordinates

12

Hingeman Research

After that we were banned from Dreaded Salvage and went to Poppers. In Poppers we saw some anomalies, but we saw hingemen again. Instead of killing it, we disabled its camera and it became docile. My friend Alex (epic builder) built the hingeman a house (testing chamber) and we were learning off it. It liked company; it was able to noclip through walls when it wanted to go by a player. It loved its bed we made for it, and it showed off some of its dances. It was also able to speak through hint messages. It admitted Jaster made it to take photos of us and send it to Jaster so he can find our location, but the hingeman deleted the photos. Jaster didn’t like that, however, and killed the hingeman. After that, we saw nothing for a while.

Docile hingemanCamera removed

13

809

We saw 809 for the first time and HE IS SO ANNOYING. 809 (go to anomaly list for looks and details) was taunting us by destroying the map. He was spawning in dead hingemen bodies to taunt us; he kept ripping my friend Alex apart limb by limb, and he asked for a fight and then kicked us instead. 809 told us that nothing can kill it—not even deleting it can kill it—then it spawned five hingemen around us that took photos of us and kicked us.

809 tauntsForced kicks

14

Turret, Nevermind

This happened after I coded a turret to scan for 809 and KILL IT instantly—the nanosecond it spawns in—however 809 decided to give it sentience instead, as the turret randomly spoke to us and said “I’M ALIVE!”. Two seconds after, 809 blew it up, killing it instantly, then banned us from the game.

Turret subvertedBan

15

Drought

For now, we don’t know what to do. We are banned from every game and need to think of a way to stop 809.

Strategy pending