Britt Gresham

Hey there, I believe it was invalid yaml that was rendered in our pipeline but not that i've tried to reproduce it it's managing to elude me.

I've also not added a docs PR yet, if that would be helpful for reviewing this PR let me know and I can expand upon the additional effect options in...

@mxklb I've also added documentation for this feature over at https://github.com/Aircoookie/WLED-Docs/pull/179. I'll see if I can get someone else to verify this build. It only requires WLED be configured with...

Discourse thread can be found at https://wled.discourse.group/t/validation-requested-for-expanded-segment-effects-over-e1-31/10522. Also for those catching up, I'm also available in the WLED Discord as `@Demophoon`. If you find this and have further questions about...

> As far as I know, macros in standard DMX mostly utilize the full channel range of 255 possible values. Dividing the full range into X possible macros is a...

> `If`S are there to explicitly not set a state if it is already present. Otherwise, realtime performance wasn't that good. Maybe this is subject of change, but shall be...

@mxklb > Finally: Of cause it's okay to do single steps, but should be avoided if just some small amount of macro states shall be triggered. Combining ranges helps to...

@mxklb I went ahead and added the options shift to this PR which guarantees two values between every option step as documented in the new docs PR. This change can...

@blazoncek Rebased to `0_15`. I'll get some testing with this new build later today and update you here