Issue: There are times when we want to block off some animations from manual mode. Like, a vampire mod might want to stop you from selecting vampire animations, or filtering out F/F anims during straight scenes.
OStim addons can handle generating these blacklists, just need an OSA feature to receive and then process them.
a function in either diasa or omajor takes a csv list of scene ids
The list is merged with a larger one in memory that is kept until the end of the OSA scene so multiple mods can send up blacklists to it and they all get used
All scenes that are a part of this blacklist are greyed out in the navtab and maybe have a different halo
Also any transitions that point at one of these scenes is greyed out the same
The first value in the CSV sent to OSA will just be a "error message" to display in place of the normal scene description. Like a vampire mod would send up "Not a vampire" and instead of "Bite them" appearing when you mouse over the icon, it instead says "Not a vampire" in red letters
After the creation of this feature I can make an easy to use ostim function for addon devs to send in blacklists quickly.
Issue: There are times when we want to block off some animations from manual mode. Like, a vampire mod might want to stop you from selecting vampire animations, or filtering out F/F anims during straight scenes.
OStim addons can handle generating these blacklists, just need an OSA feature to receive and then process them.
After the creation of this feature I can make an easy to use ostim function for addon devs to send in blacklists quickly.