How to Write a Neopixel Blade Style: Custom Lighting Effects for Proffieboard (2026)

A blade style is the code that tells your neopixel blade what to do — every pixel, every moment. Idle color, ignition animation, what happens when you swing, what the clash flash looks like, how the blade retracts. All of it lives in one style definition that sits inside your Proffieboard config file.

The ProffieOS style system looks intimidating because a complex style can run to hundreds of characters. But the logic underneath is simple: you stack layers, and each layer responds to a trigger. Once you understand that model, even a style you have never seen before becomes readable. This guide teaches you that model, then puts it to work across three hands-on examples at increasing difficulty.

1. What Is a Blade Style?

Your Proffieboard config file contains a list of presets. Each preset pairs a sound font with a blade style. The sound font handles audio — the style handles light. They are independent: you can mix any font with any style, and changing one does not affect the other.

A blade style is a C++ template expression that ProffieOS compiles into instructions for your neopixel LED strip. At runtime, those instructions run dozens of times per second to calculate the color of every pixel based on the current state of the saber — whether it is idle, being swung, clashing, or being ignited.

The good news: you do not need to understand C++ to write useful blade styles. The ProffieOS style system is a domain-specific language built on top of C++. Its building blocks are named functions with descriptive names like Pulsing, RandomFlicker, and AlphaL. You compose them like LEGO bricks.

2. How Blade Styles Work: The Three-Layer Model

Every blade style, no matter how complex, is built from the same three-layer model:

1. Base layer — the idle color of the blade. This is what you see when the saber is on but nothing is happening. Can be a solid color, a gradient, or an animated pattern.
2. Effect layers — additional visuals that appear in response to events: swing shimmer, clash flash, stab tip effect, lockup glow. Each effect is composited on top of the base using an alpha (transparency) value.
3. Trigger conditions — the logic that activates each effect. ProffieOS provides built-in conditions like IsSwinging, InOutFunc, Trigger, and On that correspond to saber states.

The Layers<> function is the container that stacks these layers from bottom to top. The bottommost layer is rendered first; each subsequent layer composites over it. A layer with a zero alpha value is invisible. A layer with a full alpha value completely replaces whatever is below it at that pixel.

3. Reading the Syntax Without Panic

Before writing your first style, spend two minutes learning to read one. Here is the simplest valid blade style: a single solid blue blade with a white clash flash.

Breaking this down:

4. Example A — Breathing Glow Beginner

The simplest animation you can add to a blade: a slow, rhythmic brightness pulse that makes the saber look alive. No layers needed — just a single animated color as the base.

Modifying this example

• Change the color: replace the Rgb<R,G,B> values. R, G, B each range from 0 to 255. For a blue breath: Rgb<0,0,200> and Rgb<0,0,30>.
• Change the speed: lower the millisecond value for a faster pulse (e.g. 800), higher for a slower one (e.g. 4000). A resting heartbeat is around 1000.
• Make it subtler: bring the two color values closer together so the brightness range is smaller.

5. Example B — Flash-on-Clash Intermediate

Flash-on-clash (FoC) is the white or bright burst that appears on the blade when it makes contact. This example adds a clash-triggered layer on top of any base color. The technique works with any base — just swap Blue for whatever color you want underneath.

What each parameter controls

Layering FoC on top of Example A

The power of Layers<> is that you can combine any base with any effect. To add a clash flash to the breathing glow from Example A, replace Blue in Example B with the full Pulsing<> expression from Example A:

6. Example C — Unstable Plasma Advanced

The unstable plasma effect combines three overlapping flicker functions to create an organic, non-repeating electrical arc pattern. No two moments look identical. This is computationally heavier than Examples A and B — if you notice the blade stuttering, it is a sign that your SD card read speed is the bottleneck, not the board itself.

Understanding the flicker functions

Tuning the plasma effect

• More chaotic: increase the BrownNoiseFlicker intensity value above 200, and increase the RandomFlicker max alpha above 16000.
• Calmer / less flicker: reduce intensity to 100 or below, and lower both arc layer alphas.
• Different color plasma: a purple plasma uses Rgb<100,0,180> as the primary and Rgb<180,100,255> as the arc color. A green toxic variant: Rgb<0,160,0> primary with yellow-green arcs.
• If you see stuttering: this is almost always SD card latency. Format the SD card to FAT32, or use a Class 10 / A1-rated card. The board is not the bottleneck.

7. Test, Upload & Switch Styles

A blade style does nothing on its own — it needs to be registered as a preset in your config file. Here is how a preset entry looks:

• Paste your style into the preset

  Replace the StylePtr<…>() placeholder in an existing preset with one of the styles from this guide. Save the config file.

• Compile and check for bracket errors

  In Arduino IDE, click the Verify (✓) button before uploading. This compiles the config without flashing the board. Any bracket mismatch or typo shows as a red error at the bottom. Fix the error, then verify again.

• Upload to the board

  Once Verify passes with no errors, click Upload (→). The saber emits a brief distorted sound when flashing completes, then starts normally with the new style active.

• Switch between presets on the saber

  With the default SA22C prop, hold the power button and click the auxiliary button to cycle through presets. Each preset can have a different blade style, so you can load multiple styles and switch between them without reflashing.

8. Where to Find More Styles

Writing styles from scratch is one path. Borrowing from the community and modifying is faster, and how most people start.

• Fett263 Style Library — the largest curated collection of ProffieOS blade styles, free to use. Every style is documented with parameter explanations. Start here if you want ready-made quality without writing a single line.
• The Crucible (therebelarmory.com) — the main ProffieOS community forum. The blade style sharing threads are active, and the developers (including ProffieOS creator Fredrik Hubinette) are regularly present to answer questions.
• ProffieOS Style Editor — a web-based visual editor at fredrik.hubbe.net that lets you build styles by selecting options in a UI, then generates the corresponding style code. Good for learning what each function produces visually.
• ProffieOS GitHub — the source repository contains full documentation for every built-in function, including parameters and example usage.