Hello boys and girls, this is B. F. Nigels, adventurer, bug hunter and all around cool old guy, welcoming you to a new episode of Bug Hunting! Today we are travelling deep into the mysterious place of The Engine in order to hunt the last two remaining known bugs, both being extremely dangerous and/or annoying. Get ready for an adventure!
The Six-Legged Crasher is a well known bug in this place: mostly harmless, but also a pain in the ass, it was discovered over a year ago but this is the first time that its hunt is attempted. As its name suggests, this bug is infamous for provoking what the natives call a "crash".
According to our observations, this bug attacks when people walk to Editor Mode from Play Mode, but only some times. His unpredictability makes it quite the annoying little bugger.
Thanks to our most advanced tracking tools, we found its natural habitat: a zone called The Player HUD, a place known for keeping track of the more "special" travellers, known as "player characters". For some reason, when travellers walk back to Editor Mode, the player character is always brutally killed one way or another. Always. This has nothing to do with the bug: apparently, according to the locals, this is the way the Gods punish the players for having "free will", whatever that is.
Despite this unfortunate event, the HUD still has the player's contact information stored in a device known by the locals as a "pointer", without knowing that he or she is now deceased. It is when people try to contact this person using this device when the bug attacks, causing a "crash" in the process.
With this information at hand, we travelled to Play Mode with our collaborator Dave, a well known player who had no idea of the curse by the Gods, and as soon as we arrived, we ran back to Editor Mode without him. Unsurprisingly, the Six-Legged Crasher got out of hiding, and without thinking twice, my camera man crushed him with his right foot. Victory for the hunting team!
The homies from the HUD thanked us for our ordeal: the Six-Legged Crasher is no more, but this victory was achieved at a great cost: we will keep Dave, who was a victim of fate, deep into our hearts.
It was a long day, and as soon when we got back to our camp to celebrate our big victory and drink to forget our beloved collaborator, we get a distress call from a group of travellers near the coast: people, and even places, were going missing under very specific circumstances. We immediately grabbed our gear and went to the coast.
Before continuing, I have the need to explain to our viewers the science behind how The Engine works according to the experts: its theorized that this magical place only shows itself to travellers in small squared chunks at a time. These chunks, scientifically known as "sections", always appear in groups of nine at any given time: the central section, where travellers are standing, plus all the eight surrounding ones. If travellers move far enough, the sections shift to accommodate the travellers' new position, always in a group of nine.
Let's say that we are standing still. We will only see our current section plus all eight that surrounds it. Now, if we move far enough front, eventually the three sections from the back will disappear, and three new sections will appear at the front.
This phenomenon, known by the scientits as "Loading", is better explained with the following animation:
Fun fact: some natives believe that this phenomenon is caused by the devil "Optimus", and that he does it just to piss the Gods off.
Back to the distress call, we arrived at the coast in the morning and met the travellers who witnessed this previously unknown bug. According to their observations, this bug only attacked when travellers had the audacity of travelling diagonally and triggering the Loading phenomenon both vertically and horizontally at the exact same time, which is quite the feat. A rare, deadly feat.
When a "Diagonal Loading" happens, our bug viciously attacks travellers -and even the terrain- that are in adjacent chunks of the one where the travellers who triggered the phenomena are standing on, if that doesn't sounds confusing enough. In other words, whole places where disappearing in front of travellers' eyes!
Without hesitating, my cameraman and I started travelling diagonally, and after several tries we finally saw the little bugger, to whom we fondly named "The Coastal Bastard". Ugly and vicious, he attacked the other travellers, who unfortunately where in an adjacent section instead of coming with us.
We couldn't catch the Bastard, so we tried to lure him again. After several tries, and after seeing the Bastard devour several travellers passing by, and even eating the trees and the ground far away, my good friend the cameraman finally put a bullet between its eyes. Hunting was over, the Diagonal Loading Anomaly was fixed, and we were going back home
On the bus, my cameraman had a big smile -he was surely mounting The Coastal Bastard on the wall- but I wasn't sharing his joy: all the way back to the city I was thinking about the Bastard, how he was discovered two years after the hunting started, and how those travellers found him out of pure coincidence. I got shivers thinking: "What if they didn't find him? What if this place opened to the public with that thing still out there?". That, like the locals say, would have been "game-breaking".
This is all for this week's episode. Next episode I will go alone with my handheld camera to explore the wilderness of The Engine in order to discover new bugs. I will try to bring home my own Coastal Bastard, and try to make The Engine a safer place for travellers and locals alike.
B. F. Nigels signing off.