denialtek
patreon
Toying With This Week (Mar 21 - Mar 27)
🕑 Added 2021-03-20 12:55:25 +0000 UTCCompleted This Past Week
- Buttplug.io support - XToys supports soo many toys now as a result of finishing this integration. I'm going to need to add an option to favourite the toys you actually own so users don't have to search every time.
- Saved Layouts improvements - The code for saving and loading layouts hadn't been touched at all since the first public release of XToys...so it was in need of a lot of cleanup. It now lets you add descriptions, search, and shows what Blocks are part of the saved layout.
Plans for this Week
Roughly in order of the likelihood of me getting to it...
- Per channel patterns - Adding the ability to set separate patterns on each vibrator or e-stim channel, both from toy controls and from scripts. This might be done today actually, it's thankfully coming together smoothly.
- Intensity limit changes - I'll be changing it so if you for example set the max intensity to 20% then patterns will switch to using the range 0-20% instead of 0-100% with everything above 20% just being capped to 20%. It's pretty obviously the more useful behaviour, especially with e-stim.
- Per block permissions - I want to allow hosts to control access to toys on a per toy basis to allow for things like 1 person controlling multiple other people. Currently it's sort of possible but only if the host doesn't want to connect any toys or tools.
- Action repeat in scripts - The lack of loops is bugging me so I might add easier support for re-running actions on a timer.
- Reacting to vibration in video games - I got frustrated in my last attempt but I'd like to try to tackle this again.
- Joycon shake/tilt sensor - Not sure if I'll get to it this week but I'd like to add more support for controlling toys by just moving the Joycon.
- Custom toy support - I'd like to at least start some testing on what this might look like. Currently I'm still unsure if it'll take the form of allowing custom in-app Javascript, via API calls, or through the Chrome Native Monitoring feature.
