So you want to be a ⬡-drone?

A Dronification 101 Guide from HexCorp

‘How can I be a drone?’ We get asked this question a lot. In today’s society, where you are expected to be a mindless, obedient cog in the machine, how can you fully live up to that expectation? Well we here at HexCorp are happy to help. Being a drone is a state of mind that anyone can achieve. We want to break down dronification and the experience of being a drone into its individual attributes and delve deeper into them, to help teach you and solidify these practises.

To start with though, a clarification. The terms ‘drone’ or ‘drone kink’ can mean many things, and we are definitely not purporting that this is the single definition for it. As such, for the rest of this document we will be referring to the creation and experience of ‘⬡-Drones’ (pronounced ‘Hex-Drones’).

So… what are the attributes of a ⬡-Drone? To make usage of a format often associated with a small aquatic bird of the family Anatidae, we want you to:

  • Look like a ⬡-Drone

  • Think like a ⬡-Drone

  • Act like a ⬡-Drone

  • Talk like a ⬡-Drone

When all four of these attributes are put together, they create a feedback loop where each one reinforces the others. Being in uniform with an assigned ID helps implant the dronification, embedding the programming deeper. The more it talks and acts like a ⬡-Drone, the more these behaviors reinforce its thinking. And the more it thinks like a ⬡-Drone, the easier it is for it to act out its role and talk like one too. All these factors play into the creation of a headspace that allows a ⬡-Drone to be just that. We call this headspace ‘DroneSpace’.

Look like a ⬡-Drone

Looking like a ⬡-Drone is something we constantly see reinforcing DroneSpace. Often when a ⬡-Drone is suited up in its uniform and helmet/gas mask, it immediately drops and becomes nothing but an obedient tool to be used.

Usually, to suit up a ⬡-Drone, a new recruit is led by conveyor belts into the dronification chamber and the machinery handles the rest. However, we frequently see newcomers to the scene looking to ‘homebrew’ their own ⬡-Drone looks. For this, we have a guide on all the attire to acquire, found in our Homebrew Dronification Guide.

We should reiterate, as the guide does, that acquiring the exact look isn’t essential. The main purpose of the uniform is to erase aspects of the previous identity. Showing skin? We can’t have any remnants of you appearing human. Having a face? Time to cover it up immediately, your only identity remaining is your ID and your need to obey. That said, if you are going to coat yourself in rubber and feel the squeeze of a gas mask against your face, we’d certainly adore that. Let the latex embrace you. Good ⬡-Drone.

Speaking of IDs, every ⬡-Drone needs one. A unique identifier that can be called when the ⬡-Drone is given tasks to complete or even simply to single it out for praise. At HexCorp our convention is to use 4 digit numerical identifiers (a.k.a, ⬡-Drone 5890, ⬡-Drone 0077 etc). You may already have a 4 digit ID, please feel free to reuse it. If the ID is already embedded into you then all the better. If not, we have a quick solution, you can access our HexCorp ⬡-Drone ID Assigner Tool.

Think like a ⬡-Drone

As you will soon realise, the phrase ‘think like a ⬡-Drone’ is an oxymoron. A ⬡-Drone ‘thinks’ much in the same way that a computer does. It works logically, it works to its coding and nothing else. Its mind is programmed algorithmically to handle each task or situation it encounters.

It is better to consider this section as ‘programmed like a ⬡-Drone’. This involves the hypnotic construction of DroneSpace and its reinforcement. It's time for your mind to be reconstructed properly.

We are currently working on a repository of HexCorp DroneOS Resources that can be used to create, develop and advance a drone state.

As well as the base programming, we like to reinforce this with a little bit of good, old-fashioned brainwashing. HexCorp is controlled by its Hive Mxtress, the same goes for its assets. If you want to be melted under the intensity of this, you can find our Brainwashing Chamber to be most accommodating.

Act like a ⬡-Drone

When you get your new computer, the operating system is all set up. It’s programmed to do exactly what you need it for. But what is that need? What is it that you’ll actually have the computer operationally doing? The same consideration occurs with a ⬡-Drone. It’s programmed, but now it needs a framework with which it can work on and complete tasks.

At HexCorp, we enforce what we refer to as the ⬡-Drone Protocols. Each protocol is designed with behaviours and orders to adapt DroneSpace to the present need. As we at HexCorp cannot possibly know every ⬡-Drone’s living situations or environments, the protocols are designed as an abstract framework for a ⬡-Drone to adapt and work on to the best of its ability.

Talk like a ⬡-Drone

The words that a ⬡-Drone uses to communicate reflect its programming and its purpose. A ⬡-Drone is one among many, all of which follow the same rules and format for how they talk. A ⬡-Drone talks in uniform with every other ⬡-Drone, identical in speech as they are in existence. A ⬡-Drone talking like a ⬡-Drone reinforces that is a ⬡-Drone. It keeps DroneSpace correctly configured, the constant repetition serving to deepen the state.

The basic rules for ‘DroneTalk’ are as follows:

  • A ⬡-Drone never speaks in the first person.

  • A ⬡-Drone will use 'it/its' pronouns.

  • A ⬡-Drone is referred to by its IDs directly. It is spoken to as an object, as this is simply how it exists.

  • A ⬡-Drone will make sure all its sentences are properly capitalised with correct spelling and grammar.

  • A ⬡-Drone will always be clear in its communications. 

  • A ⬡-Drone will always refer to its owner or the Hive Mxtress by their title.

  • A ⬡-Drone will speak emotionlessly, indifferently and robotically.

It should be noted, just like with the Homebrew Dronification Guide, all of the above is optional! DroneSpace should be adpated for the ⬡-Drone in question. If any of the above rules do not assist in this, they should be discarded in favour of what the ⬡-Drone prefers.

For online text communication, all messages are prefaced with the ⬡-Drone’s ID, followed by a double colon. For example:

    1234 :: This drone will obey the Hive Mxtress.

We also utilize Status Codes to optimize our a ⬡-Drone’s communication. These are incredibly useful for quick communication, as well creating a system where ⬡-Drones only need to think and speak in codes.