Skip to content

Add description and parameter settings for all new 16.0 effects#313

Merged
DedeHai merged 3 commits into
wled:mainfrom
DedeHai:FX_doc
May 7, 2026
Merged

Add description and parameter settings for all new 16.0 effects#313
DedeHai merged 3 commits into
wled:mainfrom
DedeHai:FX_doc

Conversation

@DedeHai
Copy link
Copy Markdown
Collaborator

@DedeHai DedeHai commented May 6, 2026

Add animated gifs and descriptions of all new effects.
Also updated documentation on overlay modes.

GIFs created using https://github.com/DedeHai/WLED-Tools/tree/main/FX%20to%20GIF

Summary by CodeRabbit

  • Documentation
    • Expanded Effects documentation with improved formatting and updated table headers for clarity.
    • Added comprehensive Effect Overlay support guide for version 16.0+, including mode descriptions and legacy behavior notes.
    • Documented new particle system effects available since 16.0 with detailed parameter information.
    • Created reference section for retired effects with replacement suggestions and retirement dates.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 6, 2026

Review Change Stack

Warning

Rate limit exceeded

@DedeHai has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 43 minutes and 37 seconds before requesting another review.

To continue reviewing without waiting, purchase usage credits in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: e08f7ef1-1d15-468a-a38c-9b852d925263

📥 Commits

Reviewing files that changed from the base of the PR and between e442b81 and cea88db.

📒 Files selected for processing (1)
  • docs/features/effects.md

Walkthrough

Single documentation file updated with revised Effect Overlay section, corrected Effects table header, comprehensive 16.0+ particle-system effects catalog with parameter descriptions, and new Retired Effects section mapping obsolete effects to replacements and retirement dates.

Changes

Effects Documentation Expansion

Layer / File(s) Summary
Documentation Structure
docs/features/effects.md
Added Effect Overlay documentation block with modes and legacy notes; introduced new section header "Effects available since 16.0" with introductory text; added Retired Effects section with replacement mapping table.
Effects Catalog & Parameters
docs/features/effects.md
Populated 16.0+ effects section with comprehensive list of particle-system effects (IDs 187–269) including descriptive headers and detailed parameter documentation.
Table Formatting & Corrections
docs/features/effects.md
Revised Effects table header row with column labels (ID, Effect, Description, Flags, Colors, Parameters); fixed column header typography and added table border formatting.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Poem

🐰 I hopped through pages, lines alight,
I placed new overlays in the night,
Particles whirl with numbered cheer,
Old effects bow — new ones appear,
Docs sparkle like a lantern bright.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately describes the main change: adding descriptions and parameter settings for new 16.0 effects, which aligns with the primary objective of documenting new effects introduced in version 16.0.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
✨ Simplify code
  • Create PR with simplified code

Tip

💬 Introducing Slack Agent: The best way for teams to turn conversations into code.

Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.

  • Generate code and open pull requests
  • Plan features and break down work
  • Investigate incidents and troubleshoot customer tickets together
  • Automate recurring tasks and respond to alerts with triggers
  • Summarize progress and report instantly

Built for teams:

  • Shared memory across your entire org—no repeating context
  • Per-thread sandboxes to safely plan and execute work
  • Governance built-in—scoped access, auditability, and budget controls

One agent for your entire SDLC. Right inside Slack.

👉 Get started


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 5

🧹 Nitpick comments (1)
docs/features/effects.md (1)

232-232: ⚡ Quick win

Improve grammar and clarity.

The sentence has a few issues:

  • Missing article before "pacman"
  • "Pacman" effect is not shown in the new effects list, which may confuse readers

Consider rephrasing for clarity:

📝 Suggested improvement
-All new effects support palettes except pacman. Effects with the prefix "PS" use the particle system.
+All new effects support palettes (except Pacman, if present). Effects with the "PS" prefix use the particle system.

Or if Pacman is not actually included:

-All new effects support palettes except pacman. Effects with the prefix "PS" use the particle system.
+All new effects support palettes. Effects with the "PS" prefix use the particle system.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docs/features/effects.md` at line 232, The sentence "All new effects support
palettes except pacman. Effects with the prefix "PS" use the particle system."
is grammatically awkward and ambiguous about whether the Pacman effect is
included; update it to use proper capitalization and an article (e.g., "the
Pacman effect") and clarify inclusion: either list Pacman among the new effects
or explicitly state it is not part of the new effects (for example: "All new
effects support palettes, except the Pacman effect." or "All new effects support
palettes; the Pacman effect is not included. Effects with the prefix 'PS' use
the particle system."). Ensure references to "Pacman" and "PS" remain exact so
the change is traceable.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/features/effects.md`:
- Line 267: In the Shimmer effect entry update the typo in the parameter label
by changing "Revers:" to "Reverse:" so the list of options for the **Shimmer**
effect reads "**Reverse:** Invert direction" (look for the "Shimmer" table row
and the "Revers" label in the effects description).
- Line 267: Replace the misspelled word "accross" with the correct "across" in
the Shimmer effect description (the line containing "**Shimmer** | A shimmer
moving accross the strip..."); update the Markdown string so it reads "A shimmer
moving across the strip with optional modulators." and keep the rest of the row
unchanged.
- Line 12: Change the "Effect Overlay" heading from a level-4 heading to a
level-2 heading by replacing the "#### Effect Overlay" line with "## Effect
Overlay" in docs/features/effects.md so it uses the top-level section style
(follow the project's header hierarchy of ## for top-level, ### for
subsections).
- Line 50: Update the table header row that currently contains the misspelled
column label "Parmeters" to the correct spelling "Parameters"; locate the header
string in the effects table (the header line that reads "|  ID | Effect |
Description | Flags | Colors | Parmmeters |") and change only that label to
"Parameters" so the column header is spelled correctly.
- Around line 269-270: The Markdown table starting with the row for "Slow
Transition" needs a blank line above it to ensure proper rendering; edit
docs/features/effects.md and insert a single blank line immediately before the
table block that contains the row with "**Slow Transition**" (the table
header/row around FX_219) so the table is separated from the preceding
paragraph; save and verify the table renders correctly.

---

Nitpick comments:
In `@docs/features/effects.md`:
- Line 232: The sentence "All new effects support palettes except pacman.
Effects with the prefix "PS" use the particle system." is grammatically awkward
and ambiguous about whether the Pacman effect is included; update it to use
proper capitalization and an article (e.g., "the Pacman effect") and clarify
inclusion: either list Pacman among the new effects or explicitly state it is
not part of the new effects (for example: "All new effects support palettes,
except the Pacman effect." or "All new effects support palettes; the Pacman
effect is not included. Effects with the prefix 'PS' use the particle system.").
Ensure references to "Pacman" and "PS" remain exact so the change is traceable.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: e4641ee2-fe33-4368-8712-aefa6aa0a29a

📥 Commits

Reviewing files that changed from the base of the PR and between daa632a and 68b6629.

⛔ Files ignored due to path filters (35)
  • docs/assets/images/content/effect_gifs/FX_151.gif is excluded by !**/*.gif
  • docs/assets/images/content/effect_gifs/FX_161.gif is excluded by !**/*.gif
  • docs/assets/images/content/effect_gifs/FX_187.gif is excluded by !**/*.gif
  • docs/assets/images/content/effect_gifs/FX_188.gif is excluded by !**/*.gif
  • docs/assets/images/content/effect_gifs/FX_189.gif is excluded by !**/*.gif
  • docs/assets/images/content/effect_gifs/FX_190.gif is excluded by !**/*.gif
  • docs/assets/images/content/effect_gifs/FX_191.gif is excluded by !**/*.gif
  • docs/assets/images/content/effect_gifs/FX_192.gif is excluded by !**/*.gif
  • docs/assets/images/content/effect_gifs/FX_193.gif is excluded by !**/*.gif
  • docs/assets/images/content/effect_gifs/FX_194.gif is excluded by !**/*.gif
  • docs/assets/images/content/effect_gifs/FX_195.gif is excluded by !**/*.gif
  • docs/assets/images/content/effect_gifs/FX_196.gif is excluded by !**/*.gif
  • docs/assets/images/content/effect_gifs/FX_197.gif is excluded by !**/*.gif
  • docs/assets/images/content/effect_gifs/FX_198.gif is excluded by !**/*.gif
  • docs/assets/images/content/effect_gifs/FX_199.gif is excluded by !**/*.gif
  • docs/assets/images/content/effect_gifs/FX_200.gif is excluded by !**/*.gif
  • docs/assets/images/content/effect_gifs/FX_201.gif is excluded by !**/*.gif
  • docs/assets/images/content/effect_gifs/FX_202.gif is excluded by !**/*.gif
  • docs/assets/images/content/effect_gifs/FX_203.gif is excluded by !**/*.gif
  • docs/assets/images/content/effect_gifs/FX_204.gif is excluded by !**/*.gif
  • docs/assets/images/content/effect_gifs/FX_205.gif is excluded by !**/*.gif
  • docs/assets/images/content/effect_gifs/FX_206.gif is excluded by !**/*.gif
  • docs/assets/images/content/effect_gifs/FX_207.gif is excluded by !**/*.gif
  • docs/assets/images/content/effect_gifs/FX_208.gif is excluded by !**/*.gif
  • docs/assets/images/content/effect_gifs/FX_209.gif is excluded by !**/*.gif
  • docs/assets/images/content/effect_gifs/FX_210.gif is excluded by !**/*.gif
  • docs/assets/images/content/effect_gifs/FX_211.gif is excluded by !**/*.gif
  • docs/assets/images/content/effect_gifs/FX_212.gif is excluded by !**/*.gif
  • docs/assets/images/content/effect_gifs/FX_213.gif is excluded by !**/*.gif
  • docs/assets/images/content/effect_gifs/FX_214.gif is excluded by !**/*.gif
  • docs/assets/images/content/effect_gifs/FX_215.gif is excluded by !**/*.gif
  • docs/assets/images/content/effect_gifs/FX_216.gif is excluded by !**/*.gif
  • docs/assets/images/content/effect_gifs/FX_217.gif is excluded by !**/*.gif
  • docs/assets/images/content/effect_gifs/FX_218.gif is excluded by !**/*.gif
  • docs/assets/images/content/effect_gifs/FX_219.gif is excluded by !**/*.gif
📒 Files selected for processing (1)
  • docs/features/effects.md

Comment thread docs/features/effects.md Outdated
Comment thread docs/features/effects.md Outdated
Comment thread docs/features/effects.md Outdated
Comment thread docs/features/effects.md
Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

♻️ Duplicate comments (1)
docs/features/effects.md (1)

255-271: ⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Fix visible typos in effect descriptions/parameters.

There are user-facing spelling issues: accross, prefrence, Exmple, and Persistant.

📝 Proposed fix
-| 204 | **PS Dancing Shadows** | Shadows rushing accross the strip. <br /> ...
+| 204 | **PS Dancing Shadows** | Shadows rushing across the strip. <br /> ...

-| 205 | **PS Fireworks 1D** | ... **Firing side:** Starting point prefrence <br> ...
+| 205 | **PS Fireworks 1D** | ... **Firing side:** Starting point preference <br> ...

-| 161 | **Shimmer** | A shimmer moving accross the strip with optional modulators. <br /> ...
+| 161 | **Shimmer** | A shimmer moving across the strip with optional modulators. <br /> ...

-| 219 | **Slow Transition** | ... **Exmple:** Create a preset ...
+| 219 | **Slow Transition** | ... **Example:** Create a preset ...

-| 151 | **PacMan** | ... **Smear** Persistant tails <br> ...
+| 151 | **PacMan** | ... **Smear** Persistent tails <br> ...
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docs/features/effects.md` around lines 255 - 271, Fix the visible typos in
the effect descriptions: change "accross" to "across" in the PS Dancing Shadows
description, change "prefrence" to "preference" in the PS Fireworks 1D parameter
"Firing side", change "Exmple" to "Example" in the Slow Transition note, and
change "Persistant" to "Persistent" in the PacMan parameter "Persistant tails";
update these strings in the docs entries for the corresponding effect names (PS
Dancing Shadows, PS Fireworks 1D, Slow Transition, PacMan).
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/features/effects.md`:
- Around line 260-271: Several parameter lines in the effects table are missing
separators and colons which breaks rendering; update the parameter cells for "PS
1D Balance" (add a separator between "**Blur:** Motion blur" and "**Tilt:** Tilt
strength"), for "PS Springy" (ensure "**Smear:** Full blur" has a colon and is
followed by a <br> where appropriate), and for "PacMan" (add colons to
"**Smear:** Persistant tails" and "**Compact:** Narrow dots" and ensure each
parameter is separated with <br>); keep the existing bold parameter names (e.g.,
"**Blur:**", "**Tilt:**", "**Smear:**", "**Compact:**") and normalize
spacing/punctuation so every parameter is "• **Name:** value <br>".
- Around line 237-271: The GIF image tags for the listed effects (e.g., "PS
Volcano", "PS Fire", "PS Fireworks", "PS Vortex", "PS Fuzzy Noise", "PS
Ballpit", "PS Box", "PS Attractor", "PS Impact", "PS Waterfall", "PS Spray", "PS
GEQ 2D", "PS GEQ Nova", "PS Ghost Rider", "PS Blobs", "PS Galaxy", "PS
DripDrop", "PS Pinball", "PS Dancing Shadows", "PS Fireworks 1D", "PS Sparkler",
"PS Hourglass", "PS Spray 1D", "PS 1D Balance", "PS Chase", "PS Starburst", "PS
GEQ 1D", "PS Fire 1D", "PS Sonic Stream", "PS Sonic Boom", "PS Springy",
"Shimmer", "Color Clouds", "Slow Transition", "PacMan") currently use empty alt
text; replace each ![](...) with a meaningful alt attribute using the effect
name (e.g., ![PS Volcano effect
GIF](../assets/images/content/effect_gifs/FX_187.gif)) keeping the same relative
path pattern, ensuring each entry's image tag has descriptive alt text following
"GIF of <Effect Name>" or similar to satisfy accessibility/MD045.

---

Duplicate comments:
In `@docs/features/effects.md`:
- Around line 255-271: Fix the visible typos in the effect descriptions: change
"accross" to "across" in the PS Dancing Shadows description, change "prefrence"
to "preference" in the PS Fireworks 1D parameter "Firing side", change "Exmple"
to "Example" in the Slow Transition note, and change "Persistant" to
"Persistent" in the PacMan parameter "Persistant tails"; update these strings in
the docs entries for the corresponding effect names (PS Dancing Shadows, PS
Fireworks 1D, Slow Transition, PacMan).
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: cc171745-9ae6-4133-a64e-0b1e3671781c

📥 Commits

Reviewing files that changed from the base of the PR and between 68b6629 and e442b81.

📒 Files selected for processing (1)
  • docs/features/effects.md

Comment thread docs/features/effects.md Outdated
Comment thread docs/features/effects.md Outdated
@DedeHai DedeHai merged commit 2e211da into wled:main May 7, 2026
1 check passed
@DedeHai DedeHai deleted the FX_doc branch May 7, 2026 19:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant