Random spots create 2-Dimensional Ripples that go outward and superpose each other

When calling g_aLeds[i].nscale8(brightness) every tick, previous colors get asymptotically erased.
Split into two arrays:
One which the work is done in, and the render() methods are called, and
One which in the end the first array is copied into, and then dimmed.

This enables behaviour like LEDs leaving traces, and effects overwriting others.

So far, whenever you choose either a single color or multiple, the code is the same.
Handle it in the global webhandler, and make a concatenatable HTML block.

Also: instead of having five radio buttons and one color picker, just use five color pickers.

Bonus points: Remember the point in the html string where "value="#ff00ff" " is, and dynamically snprintf/memcopy the current color value, so it represents the status quo

Check out Marching Squares algorithm, although at such a low resolution maybe find something else?

Metaballs you know

directly manipulating the LED array with pointers may be a bad idea, even though we do have our dummy led for parameter faults.
When using a setPixel() and getPixel() function, this may be more general so future compability is assured.

on the Other hand, keep the choords() function for advanced stuff like calling CRGB::methods, and just have a getPixel/setPixel function that acts as a wrapper around choords()

https://www.youtube.com/watch?v=BAq5_Ci4IxE

Slowly reaching the 1000 lines of code, maybe break it up into multiple files for readability

should be as easy as adding a (g_Tick*m_YSpeed) to the noise function.

Replace all instances of the numbers 8 and 35 with defines.
Compatibility and stuff.

And learn wtf that is anyways

When a new speed is selected, ideally there shouldn't be a jump.
Requires some math thinking, previous attempts have failed.

Have bubbles (or other sprites, e.g. hearts) rise from quasi-random locations

Have two modes overlapping, for example Zepelli mode + circle, or Rainbow + Text

Instead of having every Character being 5x7, have them have individual widths.
Individual Widths may be saved in a separate global array (or maybe make a class out of letters?)
Managing the g_aFont array:

1. Keep it the same and have the letters left justified and fill with 0's, to make indexing easy or
2. have a cumulative array of widths, to lookup the array indices, similar to the g_aLeds array.
3. Make it a class.
   -> maybe have a method render(x) that renders the character into the array at the given coordinate
   and automatically increases x (via return value or pointer).

This makes it difficult to have differently colored letters however.