I'd like to be able to register commonly used sequences that I can then call later - generally this would be more useful for mods (but in those cases a mod could basically create a file that houses those sequences), or it could be useful for someone who just has a lot of macros that manually (or via World Scripter or something similar) registers some sequences when they load the browser.
Example use, I run basically the following on every spell, swapping out the animation for the proper school and the color for whatever color I feel best matches the given spell.
An alternative I also thought about was instead of doing something like Sequencer.registerEffect('name')... you could do something like Sequencer.register('name').effect()... which would probably make it easier to register sounds, animations, etc. But with this it might also be less clear about what's being pulled out of the registry if the "get" method was just registered(name) instead of something like registeredEffect(name).
I have evaluated this, and come to the conclusion that it would require a large scale refactor for an arguably small feature. Thank you for the suggestion, but it's not viable at this point.
I'd like to be able to register commonly used sequences that I can then call later - generally this would be more useful for mods (but in those cases a mod could basically create a file that houses those sequences), or it could be useful for someone who just has a lot of macros that manually (or via World Scripter or something similar) registers some sequences when they load the browser.
Example use, I run basically the following on every spell, swapping out the animation for the proper school and the color for whatever color I feel best matches the given spell.
So what if I could do something like this
So that would register that effect as
'spellSchoolAnimation'
and I could pull it out later to play it as is or add-on/modify to it.An alternative I also thought about was instead of doing something like
Sequencer.registerEffect('name')...
you could do something likeSequencer.register('name').effect()...
which would probably make it easier to register sounds, animations, etc. But with this it might also be less clear about what's being pulled out of the registry if the "get" method was justregistered(name)
instead of something likeregisteredEffect(name)
.