OBS-PowerShell Effects

[StartAutomating]

OBS PowerShell should introduce the concept of "effects" and "effect commands".

This should include:

• Import-OBSEffect
• Get-OBSEffect
• Start-OBSEffect
• Stop-OBSEffect
• Remove-OBSEffect

It should generate effects from Commands or JSON files that match the naming pattern:

(?>
    ^OBS.(?>fx|effects?)\p{P}
    |
    [\p{P}-[-]]OBS\.(?>fx|effects?)$
    |
    \p{P}OBS.(?>fx|effects?)\.(?>ps1|json)
)

It should also be able to Import an effect from a dictionary. In all cases, the effect will become an OBS.PowerShell.Effect

Once imported, it should be possible to Start the effect. It may not be possible to Stop it (unless we are looping)

If an effect is a JSON file, it will be treated as a series of messages and encapsulated into an OBS.PowerShell.Effect

If the effect is a command, it should be run when the effect is Started, and any results of that command that are requests should be stored as the effect.

When an effect is started, it should generate an OBS.PowerShell.Effect.Started event.

Then, any timings should be calculated and a .NET timer should generate an OBS.PowerShell.Effect.Ended event after that delay.