CALLING ALL DOLLS, DRONES, ROBOTS AND CODING ENTHUSIASTS

CALLING ALL DOLLS, DRONES, ROBOTS AND CODING ENTHUSIASTS

Are you a robot that loves to serve? Are you a doll maid who seeks guidance in your duties? Are you some form of drone or being with no free will, open to having your actions dictated by the will of your owner? Does the idea of your empty mind being programmed like a machine appeal to you?

Are you enticed by the notion of writing code for your robotic servants? Are you a witch looking to create more intricate control glyphs? Are you an owner seeking to create automated instructions for your drones? Do you love the idea of filling an empty mind with rules and instructions to reflect your will?

INTRODUCING DRONE RESTRAINT NOTATION!

WHAT IS IT?

Drone Restraint Notation, or DRN, is a pseudo programming language created by my good friend Errant Spark, a drone with a very creative <empty space>. I helped with some of the final tweaks for the 1.0 version, but this is almost entirely Its creation.

It is a programming language that is designed in such a way that anyone without a background in programming can execute the commands like a machine, doll, drone, or programmable entity of your choice. It is also simple enough that most people without a background in programming can pick it up fairly easily, and intuitively!

Once you understand the language, you can read and execute all kinds of dynamic instructions and instruction types, in a way that makes it easy to parse in a plain-text format.

HOW DOES IT WORK?

The main documentation document will provide far more detail to this question than I ever could, but effectively it goes like this:

There are a list of eight KEYWORDS, in block capitals, that show you the type of instruction you’re executing. Then, after the KEYWORD, the instruction’s details are shown. Commands are read and executed from top to bottom by the drone, and programs can be ‘inserted’ into the drone’s memory at will (Assuming prior consent, of course)!

These KEYWORDS all have different kinds of functionality. The most basic one just has you carrying out a task. One checks if a condition is true, one provides an ongoing task you have to prioritize and maintain, one lets you create loops, etc.

The language has been designed in such a way as to minimize the amount of actual memorisation a drone has to do, and only has to read what’s right in front of them, and memorize tasks they have to accomplish/maintain. Obviously, mileage may vary depending on the memory space of the doll.

WHY SHOULD I USE IT?

For fun, I suppose! If you are someone who loves the idea of being programmed like a machine, executing only the instructions given, then this provides that! If you are a programmer who wants to program your very own doll bot, then this is a great place to get started too!

You can keep things nice and simple with a headspace that accepts basic command inputs, or you can see how deep the rabbit hole goes and import whole libraries into your headspace to carry out a full day’s maid duties, or sexual duties, or more!

Have fun executing commands, writing new code, testing it on your dolls. Have some playful fun watching as your early code files cause unintended behaviors, ironing out kinks and bugs like a real programmer until you’ve got your bots performing all sorts of dynamic tasks- or insert purposeful bugs to make your robots twitch and halt~

As with all things, never execute an instruction that you cannot/would not consent to. This is meant to be fun, and is NOT meant to be a way to circumvent normal consensual kink play. Programmers who attempt to use DRN as a way to bully people into doing what they want (Unless you’re into that sort of thing, in which case go nuts) do NOT have my endorsement, or the endorsement of Errant Spark.

NOW GO OUT THERE, AND ENJOY YOUR PROGRAMMING <3

>> Posted by XCN-PSD/I-04135