Failover script folder, random choice.

[qwksilver]

#94 May have something related, but I didn't see it.
Couldn't find another that looked close to this request.
if a failover function already exists in settings somewhere, i couldn't find it yet.

Want a library folder that can hold fail over scripts, mine are are way longer than any file i have, so in this type of implementation 2 concepts, 1 loop for duration (script too short), and truncate for duration (script way longer) in either case the video length wins, which sets the playback bar and heatmap.

The randomization should not be maped or remembered per video

[Yoooi0]

I don't know if this is something that many users would have a use for.
I think its rather niche setup, but I will will not close this for now.

Settings for this would probably have to be inside the local script library. Problem is that looping will not work with streamed videos since their duration get updated as it is streamed. But could also make the looping funscript be "streamed" kinda like SLR.

For a workaround you could have a looping script motion provider enabled on L0, with blend 100% towards script. But that was made for small repeating patterns not full scripts so it will not show on heatmap.

Other solution is to make a simple plugin, I made a sample plugin below (assuming v1.34.0 or later).
Save the text as Plugins\RandomScriptFallback\RandomScriptFallback.cs.
Edit DirectoryPath to point to your folder with the desired random funscripts (it also searches subdirectories).
There is not script looping because from what I understood your funscripts are already very long.

#:plugin
#:name RandomScriptFallback

using System.IO;

public class Plugin : PluginBase
{
    private static readonly string DirectoryPath = @"A:\scripts";

    protected override void HandleMessage(PostScriptSearchMessage message)
    {
        if (message.Result.Count != 0)
            return;

        var scriptFiles = Directory.EnumerateFiles(DirectoryPath, "*.funscript", SearchOption.AllDirectories);
        var randomFile = scriptFiles.OrderBy(_ => Random.Shared.Next()).FirstOrDefault();
        if (randomFile == null)
            return;

        var readerResult = FunscriptReader.Default.FromPath(randomFile);
        if (!readerResult.IsSuccess)
            return;

        var toMerge = readerResult.IsMultiAxis ? readerResult.Resources : DeviceAxisUtils.FindAxesMatchingName(readerResult.Name)
                                                                                         .ToDictionary(a => a, _ => readerResult.Resource);

        message.Result.Add(toMerge);
    }
}

[qwksilver]

This works really well, and doesn't really require much extra logic, the extra few min to loop an action sequence that makes a good fail-over is minor and a one time problem. I was manually loading the scripts each time, but this eliminates that step. If you added a settings prompt to the plug-in for directory choice, and an easy on/off button, it would be a really good edition to the player package.