When I used next, I noticed the trip duration and speed were shorter and slower compared to main. Is there something wrong with my settings?
You mean the stroke length is shorter or faster? If so have you adjusted the length from the plugin? Or are you referring to something else.
Also handy 1 or 2? I haven’t done testing with 2 yet so there may be bugs but lmk.
Ok, so this is now the version of the plugin I have:
Wasn’t sure if I used the right URL you are talking about though, because I am still getting the same python error in the logs when attempting to run the tag task
Looks like python isn’t set in your system PATHenv. The plugin defaults to searching from here and doesn’t use the Python Executable Path value found in Stash settings (just realized this was a thing lol).
But no it doesn’t need to be the python from the store but it must setup python. If you open up your command prompt I bet you only have python3 instead of both python and python3 available.
As a quick fix you can type which python3 find the file and copy+rename it to python in the same location. You can also run which python to see if its found or not.
Please! 
Was also browsing this post for some Stash tips/tricks and noticed a little SIT: Multi-Script tag reference 
1 Like
ALPHA RELEASES 
So there will be alpha releases for people that want to test the new/likely to break features.
First new feature is support for more devices.
- Default = how stash currently handles it (v2 api)
- FW4 = uses v3 api (sse streaming)
- FW BT = uses buttplug.io and requires FW4 hasn’t been tested AT ALL so pretty sure it will just blow up on yall lol.
FW4 should have most of the support, but may be iffy with ivdb token.
Also in this build should fix some issues around loading multi scripts (not responding to dropdown changes) as well as some issues when you navigate from one video to another.
Shout out to @iveplay for their ive-connect library. With this we will be able to support AutoBlow and others down the line.
1 Like
i have the funosr pro if youd like me to have a tear at the multi-script dependability.
Ok I meant to reply to this sooner, sorry.
So, when you say command prompt, I assume you mean the Windows one?
From what I can tell, I do see Python312 as a Path in my environment variables. It’s located in AppData\Local\Programs\Python\Python312\Scripts...
EDIT: OK, I think maybe I found the issue? I tried re-installing Python, but made sure it was installed in the C drive rather than under AppData. Then in the stash app settings under system, I set the Python executable path manually, and now the tasks finally run!
Now what I think I need help with is how to get the multi-axis script heatmaps to show. The scenes are properly tagging, but they still only show 1 axis heatmap. When running the remap task, the console give the error “Task module ‘remap’ not found”
For funscript file organization reasons… is there possibly a way to have the Interactive: Scripts drop down list default to anything other than “Default”?
Taking this as a feature request. I’ll see what I can come up with.
1 Like
Sorry didn’t see your edit. I have a feeling it’s something do to with the python path and the script.. can you dm me the full error log when this error happens. I’ll see if I can unpack what is going on. Thanks
A bit longer then I wanted but released a new alpha version . A lot of stuff under the hood to support some other management type features (drag and drop, link files without having to keep the same filename, change displayed name of script ). The first is setting scripts as default.
Add this as a new plugin source and disable the other branches (main/next)
You can also test the ability to disable interactive support completely by clicking on the new handy icon (it animates as well when actively working)
Disabled
Enabled
Be sure to run the install task if not the plugin will let you know the install is invalid and provide a button to try to install then refresh page once its completely. If you run into any issues lmk
2 Likes
Excited to try the new features. I tried to add the source (both the link from above and https://raw.githubusercontent.com/xtc1337/StashInteractiveTools/refs/heads/alpha/stash-alpha.yml) and neither worked as a source. I checked and it looks like my SIT_next source isn’t working either even though it was a day or two ago. I can see the yml and even download the zip manually in browser with the link so I am not sure if it is just a server issue or something else. I can see other plugin sources though they are github_io links not raw user content links.
Can you dm the stash log output to see whats happening. My first guess is some issue with python dependencies. I’ll see if I can try to reproduce with a fresh install. Are you using the most latest stash release or an older version?
Edit:
Actually I found the problem, I’ll push up an update today.
1 Like
It sounds like you may have already found the issue. Just for reference in case you need more confirmation, I am on the newest V0.31 stash and haven’t changed anything with python dependencies since it was last working on next branch a couple days ago. The debug I see isn’t super helpful either other than maybe seeing what is missing:
2026-04-10 09:37:28
Debug
fetching https://raw.githubusercontent.com/xtc1337/StashInteractiveTools/refs/heads/next/stash-next.yml
2026-04-10 09:36:02
Debug
fetching https://raw.githubusercontent.com/xtc1337/StashInteractiveTools/refs/heads/alpha/stash-alpha.yml
I just click on the arrow to expand the source, it loads briefly the first time and then shows nothing, no error (unless I am using the non-raw content link in which case it errors out).
Ok pushed a new version 1.2.0-alpha.4 as for the reason why reverting back to next wasn’t working . It looks like stash gets a bit confused when switching because both plugins use the same ids.
So to get around that you will need to completely uninstall (not just disable) say the next and then install the alpha. But even with that I ran into some cases where it still didn’t update so I had to press the “update” button in stash to force the change.. Odd and I need to see if I can resolve it or handle these different branches better.
1 Like
I am liking the idea/ui so far. A couple issues that I am not sure if are on my end or just the alpha nature.
For reference, I dragged out the entire folder group for my old plugin, disabled and made sure it was gone from the menu before installing the alpha. Installed it from plugins, enabled it, ran the install and init tasks, updated it in plugins, and did another scan or two just in case.
- The first time I open a scene that multiple scripts (or just 1), it is just blank:
If I refresh and it has multiple scripts, the drop box/heart pops up, but the drop box html is set to disabled:
If I then F12 and set it back to enable, it seems to work and correctly swaps the heatmaps when I select them. Though it did duplicate the scripts in the menu for one instance. It was the first video I checked I believe, and I cant remember if I did anything odd like running tasks with it open or anything. The debug only shows it finding the 3 but it says there are 6 known scripts. It doesn’t seem to be happening on other videos I open.
I am definitely excited for the drag and drop, linking files, maybe even changing or at least seeing metadata from the script when that comes. The one question I have is if there is a plan to allow it to eventually change the served funscript (http ://192.168.x.x:9999/scene/1056/funscript) or if changing that isnt likely to happen in core stash anytime soon? Primarily asking because I am using MFP and it defaults to that one when using Stash in the Web Source and would make it the smoothest if I could change the script in stash instead of MFP.
No that’s definitely because of all the changes.
The install script is pretty extensive because it has to install a few python dependencies (you can see them in the tasks/install.py of the plugin folder) so that takes a while. Given that you said you ran the install task from stash settings I wonder if something is happening there. I’ll have to spend more time testing from a fresh install.
As for the double listing this is a bug with the switch to try to auto discover (file name approach) but also use the database (it’s a stash-interactive-tools.db file which is sqlite) I thought I solved some edge cases but till seems if you refresh multiple times or run the init task multiple times it may have a race condition. I’ll check it out
Right now the only way to fix is to delete the the .db file within the plugin folder . This will remove all your default settings.
This is where having an Editor to manage the funscript would come into play to rename them,link etc.
I’ll need to add a bit more validation on the db inserts so it doesn’t happen , completely forgot about that .
Keep the feedback coming, let me know how the enable and disable toggle work (to right nav bar).
As for MFP, I made the plugin in a way that it can be used by others BUT they have to call a special graphql query from stash to execute. Due to stash server code being go and no hooks around serving funscript there is current no way(this is why the multi scripts are served from a different path).
What is the special graphql query you use? It might be possible to directly hook it into MFP w/o messing with too much.