https://metafetish.github.io/buttplug-tutorialBeen spending the last few weeks putting this together. It's a Twine (interactive fiction engine) based tutorial for getting people up and running with the basics of the Buttplug App Suite. Probably not going to be much new for patrons here, but if you have feedback, do let me know. I'm hoping to use it as our main guide for both the Buttplug App Suite (which will be changing names at some point in the nearish future I hope) as well as things like Syncydink, and maybe even outside apps like ScriptPlayer if the authors are interested.

The tutorial has been a pretty heavy test of the buttplug-js library, and I've just pushed v0.6.0 which has most of the features and bugfixes required. Hoping to get playground and syncydink on this soon too, should fix a few bugs there.

Here's a quick update about what's going on around Buttplug HQ (aka my office in my house)We released Buttplug C# 0.2 and Buttplug-js 0.5 last week. So far, the C# version has seen over 160 downloads and zero crashes reported so far, which is pretty exciting. 

The JS library has seen... 3 point releases because it's complicated and our tests still aren't covering everything we need. :|

Fucking. Finally.It's been 4 months since the last release of the C# applications and library, which is just way the fuck too long for a small project like this. I'm really hoping we'll speed up iteration on that side, because I've released... wow. 12 versions of the JS library in that time.

If you upgrade the C# applications (WebSocket server, Game Vibration Router, etc...), chances are you're probably not going to notice much in the way of changes. While there's some new hardware support (ET-312, Youcups, etc...), most of the changes in these releases are deep in our libraries, around how we communicate let applications communicate with devices. Since you're giving me money, I figure you may be interested in some details, so here you go:

Just realized I forgot to post a Q&A at the beginning of the month, so if you've got any questions, as usual, feel free to post them here.

I mean, 2017 was too, but nothing saying that we can't have multiple years with that as the theme.Working on lots of documentation right now, as well as finishing up the Buttplug Twine interactive fiction engine integration so I can build our new interactive tutorial in that.

Also finished up scripts for 2 new videos, and got myself a fancy new microphone setup, so hopefully gonna have new video content posted this month!

Thanks to the holidays I've been rather quiet, but that doesn't mean work isn't happening!However, that also doesn't mean the work is very interesting to anyone but core developers, either. :)

As of last week, we've mostly finished up the new v1 implementation of the Buttplug Protocol Spec. This adds a couple of really important things:

Yet another quick non-buttplug-related update, but it's important.https://blog.patreon.com/not-rolling-out-fees-change/

I will now return to holding it against you if you discontinue your patronage. (No I won't)

Just wanted to say, anyone that does not want to deal with the new Patreon fee model, no hard feelings if you stop support for my campaign. What I have gotten so far has been very appreciated, and I plan to continue my patreon campaign, as well as look at other options like Ko-fi. 

I know the new fee system change is pretty rough though, and I'm not gonna hold it against anyone if they don't agree with it.

Another month, another Q&A. Roping in the $1 tier for this month because it's Christmas.So, if you got questions about metafetish/buttplug/life/etc, feel free to post them here and I'll answer to the best of my ability.

It's been a little quiet around here lately, so I figured I'd share what's going on in development.- ET-312 Estim serial protocol support is now in the C# client. This allows users with ET-312 boxes to scale intensity based on input.

• .NET Standard conversion of the C# project is finished. This is a fancy way of saying we're getting closer to being able to use C# for mobile apps on Android/iOS. Our goal there is to have a Websocket Server App for phones, which will solve even more platform issues (we hope).