Update README.md

Author: danewhero

usermods/user_fx/README.md

@@ -230,17 +230,47 @@ return FRAMETIME;
 * ⚠️ Important: Because the actual frame logic is gated by strip.now - SEGENV.step, returning FRAMETIME here doesn’t cause excessive updates — it just keeps the engine responsive.  Also note that an Effect should ALWAYS return FRAMETIME, and choosing a higher number can have negative side effects.
 * The final bracket closes the `mode_diffusionfire()` function itself.
 
+
 ### The Metadata String
-At the end of every effect is an important line of code called the **metadata string**.  
+At the end of every effect is an important line of code called the **metadata string**.
 It defines how the effect is to be interacted with in the UI:
 ```cpp
 static const char _data_FX_MODE_DIFFUSIONFIRE[] PROGMEM = "Diffusion Fire@!,Spark rate,Diffusion Speed,Turbulence,,Use palette;;Color;;2;pal=35";
 ```
-This string is passed into `strip.addEffect()` and parsed by WLED to determine how your effect appears and behaves in the UI. 
-Let's break it down field by field, following WLED's metadata format.
-The string format WLED uses is semicolon-separated sections, with commas used for control labels.
-Let’s split this into logical sections (delimited by semicolons ;):
-**TODO**
+This metadata string is passed into `strip.addEffect()` and parsed by WLED to determine how your effect appears and behaves in the UI. 
+The string follows the syntax of `<Effect Parameters>;<Colors>;<Palette>;<Flags>;<Defaults>`, where Effect Parameters are specified by a comma-separated list.
+The values for Effect Parameters will always follow the convention in the table below:
+
+| Parameter	| Default tooltip label |
+| sx	       | Effect speed |
+| ix	       | Effect intensity |
+| c1	       | Custom 1 |
+| c2	       | Custom 2 |
+| c3	       | Custom 3 |
+| o1       	| Option 1 |
+| o2	       | Option 2 |
+| o3	       | Option 3 |
+
+Using this info, let’s split the Metadata string above into logical sections:
+
+| Syntax Element                                  | Description |
+| :---------------------------------------------- | :---------- |
+| "Diffusion Fire@!"      | Name.  (The @ symbol marks the end of the Effect Name, and the begining of the Parameter String elements.) |
+| !, | Use default UI entry; for the first space, this will automatically create a slider for Speed |
+| Spark rate, Diffusion Speed, Turbulence,              | UI sliders for Spark Rate, Diffusion Speed, and Turbulence. Defining slider 2 as "Spark Rate" overwrites the default value of Intensity. |
+| (blank),                        | unused (empty field with not even a space)  |
+| Use palette;                 | This occupies the spot for the 6th effect parameter, which automatically makes this a checkbox argument `o1` called Use palette in the UI.  Label for a checkbox (SEGMENT.check1); when this is enabled, the effect uses a palette (ColorFromPalette()), otherwise it fades from SEGCOLOR(0).  
+The first semicolon marks the end of the Effect Parameters and the beginning of the `Colors` parameter. |
+| Color;                  | Custom color field (SEGCOLOR(0)) |
+| (blank);                  | Custom color field (SEGCOLOR(0)) |
+| 2;                  | Number of custom sliders used |
+| pal=35;                  | Default Palette ID |
+
+
+
+
+
+
 
 
 
@@ -350,17 +380,17 @@ Notice that there are three different modes that we can define from the single e
 uint16_t mode_sinelon(void) {
   return sinelon_base(false);
 }
-# Calls sinelon_base with dual = false and rainbow = false 
+// Calls sinelon_base with dual = false and rainbow = false 
 
 uint16_t mode_sinelon_dual(void) {
   return sinelon_base(true);
 }
-# Calls sinelon_base with dual = true and rainbow = false 
+// Calls sinelon_base with dual = true and rainbow = false 
 
 uint16_t mode_sinelon_rainbow(void) {
   return sinelon_base(false, true);
 }
-# Calls sinelon_base with dual = false and rainbow = true 
+// Calls sinelon_base with dual = false and rainbow = true 
 ```
 
 And then the last part defines the metadata strings for each effect to speicfy how it will be portrayed in the UI: