side project: AdOTS Task Completion Protocol (ATCP)
essentially, enter in some tasks (like household chores) (or otherwise...!) and start the program
then, it spits back those chores in a randomized order for you to do.
TADA! It just programmed the ability to add in another task after you've started, in case you (or whomever is assigning you tasks) forgot something.
Upcoming edits? It would like to find a way to force a rough order for linked tasks (as in, if B can't be done until A is completed, in the randomized list, B should always be after A) but it hasn't logicked that out yet. Also, it would like a secondary list for "reward" tasks that occasionally may or may not be peppered in. Essentially, option tasks.
anyway, ordered/multi-step tasks now work. Just hit the toggle and enter the ordered steps below.
Next is the optional tasks, then it's pivoting back to AdOTS proper. (be afraid, it is once again reworking gear-related things - making a generated form to clean up the HTML)
also to come: changing the color scheme? It has some ideas on how that could work.
side project: AdOTS Task Completion Protocol (ATCP)
essentially, enter in some tasks (like household chores) (or otherwise...!) and start the program
then, it spits back those chores in a randomized order for you to do.
TADA! It just programmed the ability to add in another task after you've started, in case you (or whomever is assigning you tasks) forgot something.
Upcoming edits? It would like to find a way to force a rough order for linked tasks (as in, if B can't be done until A is completed, in the randomized list, B should always be after A) but it hasn't logicked that out yet. Also, it would like a secondary list for "reward" tasks that occasionally may or may not be peppered in. Essentially, option tasks.
It has figured out an effective way to enable spiral mode!
Here's the newest version with spiral mode (also it looks more stylish now)
It was a long road of trial and error to get spiral mode working. There were two big issues.
First: it needed to find or generate a spiral. And second: it needed to learn enough css to animate it in such a way that the rotation can be toggled on and off.
Drawing the spiral itself using an html canvas was not the way, as was its most recent plan--those looked ugly and blurry, and weren't worth the effort. So, it went back to the initial plan: find a way to get a good png and make it spin. An animated gif was rejected due to very very very bad quality.
So other than learning how to use digital art tools like krita, the next step was finding a good spiral image. Screenshotting the zyntaks spiral generator (hey this is such a useful tool btws) was its first stop. The generator makes some of the smoothest shapes and has a very intuitive (and flexible) ui, but downside was the color picker. It was looking for an exact hex code for the css color scheme to look the way it wants, but there is no way to do it that.
So it tried the nimja visuals (also so useful, especially now that randomizations have been implemented) (this drone loves randomization in case that wasnt evident), and the basic custom spiral took hex codes! Great. So it plugged in the color code for a dark greyish green and messed around with it until it got a spiral it liked.
As said, the plan was to take a screenshot, and then make it spin. But--luck: it right-clicked and there was a "save image as png" button. Oh nice, won't have to deal with potential file dimensions issues. But even better: the image saved was of just the green spiral as a transparent png! Basically, this is ideal. With a screenshot, the image itself would be a big rectangle, meaning it would need to enlarge it to make sure that when the image was spun 90 degrees it wouldn't leave blank space to the sides of the spiral (ick). With the png, this drone had a circular, large shape that it could center and spin with no worries of that.
After several evenings of messing around and learning how css works, it had it looking the way it wanted it to look (and a fun fuzzy drop shadow border).
The animations took a few tries, and it is mostly satisfied with them. This drone really likes the fade in and out, and it is proud of the math it had to learn (bezier curves???) to get the slow speed up to happen smoothly, but it was unable to make a smooth slow down afterwards. Alas. Plus, the slow speed up only happens the very first time spiral mode is activated and not any subsequent times, but the chance of it starting, stopping, and then starting again is quite low, so this drone decided that's a later later later project.
Then it was just a matter of getting the javascript functions set up (pretty simple at this point) and remembering how the settings verifications happen so that spiral settings can get set up.
There are three options in the settings. First is the default (spiral doesnt start on, but the toggle function can occur). Second is to completely disable the spiral, for those drones who do not process motion well in that way. Third is for those drones who looooove it, which turns on spiral mode and keeps it on the entire time.
It's debating having a chance that with the default, the spiral occasionally starts on, but eh that's a project for another time.
So yes, the first dev update in several months on AdOTS, and spiral mode (which has been an idea since nearly the start) is working!
This drone is hoping to spend more time on AdOTS again going forward, working toward a "full launch." it's got a list of goals and everything. Lots of bugs to work out, several more features to add, some streamlining of the code (since it now knows waaaay more about coding that it did when the project began), more web infrastructure, those things.
quick adots bug fix--the reward/penalty buttons work for the "choice" module now. apparently at some point it had added a single - to the very end of one of the functions. it didn't find it until now because it was end the end of the previous function, not the one that wasn't working. Ugh. But that bug is now fixed.
math test, drone is to complete a generated short basic math exam. Currently, it is limited to simple addition, subtraction, multiplication, and division with a two minute max time. drones need a score of above 80% to pass. if not, another math test is queued. In the future, it may expand this to have some harder math as well, but that seems unlikely to actually happen.
countdown, where drone counts out loud from 100 to 0. sometimes that's all, sometimes it is instructed to say some mantra after each number.
and a new themed session: computer!
it has been planning on building this one for a while. focusing on number and memory related tasks, as well as tasks involving verbal programming mantras. now that math test and countdown are done, there are finally enough modules for the theme.
known bugs (that this drone can't seem to figure out):
sometimes the reward/penalty lack of choice module doesnt work when it is at the end of the session. it's happened twice now, but isolated this drone hasn't been able to replicate the problem.
the 'begin another session' button at the end just... no longer works. it's unsure when this happened, because neither the ending nor resetting functions have been touched since they were added. this drone suspects it has something to do with changes to the array builder, but more testing is needed. in the meantime, if a drone feels the need to do another session, just refresh the page.
upcoming implementations:
still need to do light bondage, but that will likely need a revamp to some of the gear (specifically how wrist and ankle restraints are handled) so that's why it has been putting that off. still recovering from all that.
it would like to flesh out the website some. probably this is what it would count as the "official" 1.0 release (not like any of that matters). but it's thinking about documentation of the different modules, links to suggested programming audio sources, links to other fun programs and projects, and maybe like an faq? or a "request a module" and "report a bug" form of some kind (though it doesn't exactly have a server it can use for that...)
stuck on spiral mode. gifs are too small and too clunky. a rotating animation of a still spiral image, even if it could get it working (right now, the text on the page spins, the spiral stays still. the fuck.), would require this drone to be waaaay better at css (optimization for different screen resolutions mostly) than it is. it's looked into a canvas type thing? but that's a whole other mess. so. stuck on that.
After the slow exposure of rubber over the years you yearned for more and more.
Over your bed while you slept. On your skin from time to time. To always locked in rubber. To covering every piece of skin under glossy black rubber. But this mask was different. A faint droning, somewhere in the mask. You didn’t want to take it off. You couldn’t anymore, you weren’t complete without it.
The look in your eyes already shows it. The next step of programming is in progress.
gear customization is now done! version 0.6 is ready to go!
So many days of work and troubleshooting and probably, it thinks, like, around 1000 more lines of code later, drone x1320 is proud to announce that gear customization is up and running!
Now, it's basically guaranteed that there are bugs. but, those will be fixed as they happen.
To list the changes, there are now three gear options: flexible (the default, which has a few loose options so a drone can fill in the gaps with what it has), custom (which has toggleable options for every gear thing), and no gear at all (just like the old option, shunts out all gear tasks. Plus, for custom gear, options have been split between full body, tops only, and bottoms only. Now, a drone will get a full body thing, or some combination of a top and bottom (or nothing, for any of those). All combos are checked against a feasibility list to prevent totally scene-breaking stupid combos. This change caused a bunch of issues and is where the bulk of the work went.
Finally, tasks that use gear, namely the pup versions of the gear changes and the butt stuff task, have been updated accordingly. Each gear item has an associated "puppy" value, which if true means that it can be used in the pup gear task. The butt stuff task now could no longer just check for total nudity to tell the drone to strip before pluggin that thang up, since sometimes the drone will be wearing separates. So it checks full body or separates and whether or not there's nothing there before instructing either removal of the full body garment OR removal of just the bottoms. then, of course, the replacement of those afterwards.
If there are items of gear that this drone forgot that should be on there, please please let it know. It's mostly stuff that it has, so it's sure there are items and kinks that it doesn't immediately think to include. An upside of the reworking is that it only needs to add gear in one place to change the lists, instead of, like, five, so it's easy to add things.
One other little change, unrelated, is a note in the final task to also clean up all gear used during the course of the task (and two other things that may be cluttering the drone's living space. hey. a drone should be neat, why not seize the opportunity. AdOTS was all about brainwashing AND self-improvement in the first place).
It can finally move on to new projects:
the light bondage module
mathematics module! Drones are computers, right? computers do math. ahahahahaha
three new themed sessions: humiliation (with lots of inconveniences), computer (heheheh), and storage mode (bigger, like puppy mode. will always end with some form of light bondage and spending some amount of time in the dark/blindfolded/with eyes closed in storage just being programmed).
some thoughts about expanding the pushups module, or adding some more to make a fitness themed session of some kind?
it's exciting times over here in the AdOTS development lab (x1320's apartment). give the program a try! Let it know what you think!
A rundown of some of this drone's favorite brainwashing audio!
Generally, for me, I'm not looking for a long drawn out induction. Effective and classic, yes, but progressive relaxation just bores me. I want to get to the good stuff, right? Wreck my brain and turn me into a puddle, and make it snappy!
Unless the induction is especially well crafted, naturally incorporated, or subtle enough to have no clear demarcation between it and the rest, I'd rather just be hit in the brain with new programming until I've got no space left for anything else in there.
So, in no particular order, here are but a few of my favs. If you've got some you like, let this drone know! We're all in this together after all.
(dr)o(ne)bject, by dumbpuppybot. It's got it all: layers of orders, the dehumanizing "it," rhythmic repetition that has enough fluctuation to draw attention to new things over time, soooo loopable. I've spent many an hour with this just in the background as I do other things. A perennial favorite of mine. Lots of other good files too, but this one always stands out. its on soundcloud
One afternoon I combed through warp my mind and downloaded all the free drone-related files, tried each one out, and saved my favorites. I didn't save who made them, but that's how to find them. The one I like the most is"drone daily brainwashing v2" (which I've seen in a number of places under different accounts--no clue who the original is please let me know if you know). It's a big list of facts about you, a drone. Into it.
hey lots of good 'tists on thehypnocollective.com, if you're not aware of it. The virus themed files are excellent, and if you like the person's voice, most have profile pages with links to personal websites or patreons or soundgasms. From folks I've found through there, I'm particularly fond of Vox, ChaoticHypnosis, and AshDoge (his "your furry hypno roomate" puts me in pupspace like nothing else does). All creative, all great, interesting inductions, all voices I like.
I can never find this one when I want it. But it's a youtube video. Name I don't know and cant remember. But the premise is it's like a corrupted relaxation video that slowly becomes drone programming. I can never find ittttttttttttt. But it's hot.
sometimes, all you need to do to become drone is turn on a long-ass techno set and let it turn you into a machine.
hehe so this one drone, x1320, is working on a big website automated command program so that good drones can get some orders to follow if they've got the itch to obey, and it also made an audio file back at the start that it really enjoys. Did it put a lot of thought into it? No. But is the audio quality audio good? Also no. Savvy listeners might hear the influence of numbers one and two from this list on the elements of the file.
soundgasm.net
not an adots devlog, no, but this drone is nearing completion of the gear files. It's up to doing tests. Soon. Soon.
progress is slow but happening. the bulk of the logic for the gear swaps is done, it just needs to get the written interface done and set up the current gear save states to update correctly. Then all that remains of this big gear module reworking is setting up the easy logic for the simple/custom toggle (easy, the simple just uses the old method) and then testing and finding all the typos it is sure are in there.
then, just updating the pup tasks to reflect the new gear system, as well as the various sex tasks to reflect whether or not current gear allows access. if access is needed, the drone will be told to strip, and then will get re-dressed. this is how the butt task currently works (though this drone has realized that there is a waaaaay simpler way to do it) though adapting it to only removing the lower half of the clothes will need to be done. with the changes to the gear list infrastructure, this should be as easy as adding in a property called "anal access" or something (or other body parts for the other modules) and then checking it.
this drone doesnt anticipate any more huge puzzles to figure out at least. the revamped gear swapping has 38 different possible cases by the way. in case anyone was curious.
top and bottoms pairing function (incorporating the tiered system of good pairings, okay pairings, and bad pairings) is made and tested.
part one of the gear change is updated (though not yet tested)
what's left is part two of the gear change module--all the subsequent changes (yikes it was just doing this and had to call it a night)--and making sure all the other modules that change gear (just the pup tasks? there are some that deal with mouth gags but those havent really changed at all. and this drone was careful to keep the names all the same).
and then... is that it?
well, there are all sorts of modules that it's been dreaming up and just hasnt had a chance to build. and a few other tasks. but the gear customization (which became reworking the structure which became the tops/bottoms split yeesh) was a big hurdle before an "official release".
unrelated, starting a chastity lock is a mindfuck. esp when the duration is uncertain.
Oh no it's become a reworking of ALL the gear data.
What if it was all stored in one big external file, routed in, and then individual arrays could then be made from the big file! that would make things so easy with future edits, and consistency, and keeping data together like for pup mode lists, and preventing typos, and cleanliness on the main code yeah yeah so much smoother and easy to read
A huge undertaking...
Needs to be done though. This drone is working on it.
Part of the downside of learning while it goes. Ah well! That's half the fun!
The good news is it made a lot more progress on the actual toggles for gear customization yesterday. Things are working as they should. Which is a perfect time to redo it all.
it has created a nightmare beyond its meager comprehension.
So gear customization is going well. build all the toggles for everything except main body, because it has been wanting to update that list a bit (foreshadowing). Everything's going great, the menus appear and disappear accordingly, the data maps (maps!) are made and update correctly when the corresponding button is toggled. great. just gotta do the body and then it can move on to actually building the customization function for gear (which won't be super hard--easier than the old customization it suspects.) and then test it a bunch (what a lucky drone!)
hmmm. but really there are two types of full body--upper and lower separates, and full body pieces. and right now the separates are already put into little paired outfits that kinda make sense. but what if, for instance, a drone has an athletic cup but hadn't impulse bought hockey pads off ebay this past june (it was horny it had been three whole weeks caged and they were cheap!!) so that drone doesnt have those? it wouldn't make sense for not having a less common gear thing to make a more common gear thing no longer usable.
So. going to have to split tops and bottoms up. But, uh oh, what about things that are full body? those can't be split up. so maybe when putting together a full body dress up command, (oh no it's going to have to really update that module...) the program should pick between a full body item or a pair of tops and bottoms, and then go from individual lists accordingly. great.
but wait. some of these tops really don't make thematic sense with certain bottoms. Like, there can be some silliness and absurdity, but it just doesn't think a corset goes with gym shorts. or at least, it would rather that certain pairings, like leather jacket x leather pants would be more likely to go together than less obvious pairings.
So, hmm, maybe there could be a way to rank pairs. Sure let's whip up a little spreadsheet. and in the grid assign a score of 1 (yeah great outfit) 2 (could work, a little funky) or 3 (nah that's so bad as to be not hot any more). Great. And everything goes with nothing, so this will also allow the fall back of just a top or just a bottom with the other half nude, which the old configuration doesn't allow for anyway. great! oh and it'll rank the pairs with nothing to have a score of 1 so that there is always always some combination that will work, even if some drone unchecks every single box. great.
Oh. But. hmm. how to program that in AdOTS....
and now we get to the nightmare. it spent the last hour and a half making one big map object (love a map) that has EVERY PAIR (which is 210 pairings, by the way, if you include the nothings, which you have to) and the pair's score so that the function which it HAS YET TO MAKE can roll a top and a bottom, smush them together to make a key, then get the score value that corresponds to the pairing. then if it's a 3, it'll reroll, if a 1, it'll take it, and if it's a 2 it'll reroll once or maybe twice and see if it gets a 1 instead, otherwise it'll take the 2. That sure will be quick to do. for sure. please. and please please let it work the way this drone thinks it will. it should. please.
oh the sufferings this drone is enduring, all in the pursuit of an overcomplicated kinky hobby project.
It only now realized that it hasn't made the most two recent versions accessible. Now version 0.4 (which has the early customizations, and half of the newer tasks) and the current version 0.5 (with the current themed session and the rest of the newer tasks) are linked on the landing page of AdOTS. Enjoyyyy.
(lots of progress on gear customization. Half the infrastructure is made. Left to do is the other half (the toggles themselves) and then adapting the current customization function to work with the newer gear options. progress though. it's been a busy drone.)
blakekathryn
germansingergirl
areudirty
dededos
izzy806
tangentwithtanner
baratheonpilled
ellievsbear
yousharknotpass
