DARKBEACON GUIDE
Create and assign macros
Record a short action sequence, review timing and repetition, assign it to one key, and recover a safe mapping.
Applies to: Blade keyboards (61, 68, 84, 87, and 100), Flux keyboards (61, 68, 84, 87, and 100), Flux 68, Flux 84, and Flux 87 regional models, Devil Breaker and related keyboards, Steampunk, Other supported wireless keyboards shown in the App
What you will accomplish
Create a short macro (A reviewed sequence of input actions and delays that runs from one assigned trigger), review each action and delay, assign it to one key, and keep an ordinary-input recovery path.
Applies to
Steps
- Open Macro Editor and choose New Macro.
- Enter a purpose-based name, confirm it, and select an existing tag or create a suitable tag.
- Choose an available trigger mode: Single Trigger, Hold Repeat, Toggle Switch, or Sequence. Use the table below to understand release behavior.
- Open the macro details, start recording, and enter the shortest required sequence in a harmless test context. Stop recording immediately afterward.
- Review every press, release, delay, loop, and step order. Remove accidental input and use moderate timing before trying faster playback.
- Use Single Trigger for the first test. For Hold Repeat, Toggle Switch, or Sequence, confirm exactly how playback stops before assigning the macro.
- Assign the macro to one non-essential key on the intended layer and preview it.
- Keep DarkBeacon App running and test in a blank document or safe application. Check release and stop behavior and confirm every modifier is released. Do not change focus during playback: input may reach the newly focused application.
- When the result is predictable, save to device (Store the current settings on the device so they remain after the App disconnects or power is restored).
What release means for each macro mode
| Trigger mode | On activation | On release, including an RT release |
|---|---|---|
| Single Trigger | Runs the sequence once. | Does not interrupt a sequence already running. Rapid re-activation can leave another run pending; repeated activations are not an unlimited queue. |
| Hold Repeat | Repeats while the trigger remains active. | Requests repetition to end; a running cycle can finish rather than stopping between its actions. Rapid re-presses can leave another run pending. |
| Toggle Switch | Starts playback; a subsequent activation stops it. | Release alone does not stop playback. |
| Sequence | Runs the press section, followed by the hold section while active. | Moves toward the release section after the current section completes. It does not instantly cut off the current action. |
Do not use release or a focus change as an emergency-stop guarantee. Keep test sequences short and harmless, and wait for playback to stop before editing assignments or changing applications.
Using RT on a macro trigger
RT changes when the assigned physical key sends activation and release; it does not change the macro's actions or its selected trigger mode. A small upward movement can count as release, and pressing down again can activate the macro without lifting your finger fully off the key. Very sensitive settings can therefore repeat Single Trigger unexpectedly or flip Toggle Switch on and off.
First verify the macro with RT off. Then enable RT on its physical trigger key and test one press, partial release, re-press and full release. Judge success using the mode's stop rule above, not “every macro stops when I lift my finger.” Toggle Switch is a macro mode, not the separate Toggle advanced-key feature.
An empty mapping starts no macro. Disable prevents new trigger actions while the key remains disabled; assigning a macro to that key re-enables it in the current App. Do not rely on disabling or clearing the trigger to cancel a sequence already running. Remove a conflicting DKS, MT or Toggle assignment before assigning a macro, and use only combinations accepted by the App.
Confirm success
The trigger produces the reviewed sequence, stops according to its selected mode, and leaves no unintended held modifiers. Full release, partial release with RT, and a deliberate second activation have the expected results.
Save result
Saving a macro definition and assigning its trigger can be separate actions in the App. Confirm that both the sequence and key assignment remain after reconnecting. App 1.16.206 can combine non-overlapping local and cloud edits, but the merged macro still requires review before device use.
For the current App-managed macro path, keep the App running during playback. A saved keyboard trigger, or choosing hardware output where offered, does not by itself mean the macro can play without the App.
Limits and cautions
Recovery
Stop playback according to the selected mode and wait for it to finish before removing the macro assignment. Then delete or correct the sequence, restore the original key mapping, and save the recovered profile.