Skip to content
← All guides

DARKBEACON GUIDE

Remap keys and layers

Search for key actions, customize supported Fn assignments, check every affected layer, and save a usable mapping.

On this page

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

Use the App to change one key on a selected layer (A selectable set of key actions that changes what physical keys do), test the result, and keep a path back to the original mapping.

Applies to

Steps

Steps
  1. Open the current device, select Remap, and choose the intended layer.
  2. Select one physical key and note its original action.
  3. Choose the new action from the categories the App provides, such as a keyboard key, shortcut, application launch, disabled key, media control, lighting switch, profile switch, or macro. Not every category is available on every model.
  4. Apply the preview and test the key in a low-risk text field or the intended application.
  5. Check modifier, held-key, and layer-switch behavior. Repeat for another key only after the first result is clear.
  6. When the mapping is correct, save to device (Store the current settings on the device so they remain after the App disconnects or power is restored) and wait for success.

Use the search box in the selected Remap tab to narrow the available choices. Search characters or action names in the key-action tab, macro names or tags in the macro tab, and effect names in the lighting tab. Hover over a character or shortcut to read its description before assigning it.

If nothing matches, try a shorter name or use Clear search to browse again. Searching only filters the choices; it does not change the selected key or add functions the keyboard does not support.

Choose where Fn is assigned

On keyboards and firmware that offer Fn as an assignable action, you can add an Fn key on the Main layer and change an existing Fn assignment where permitted. A protected factory Fn key may remain unavailable for reassignment.

Steps
  1. Select the Main layer and a key whose existing action you can replace.
  2. Choose Fn from the available key actions.
  3. Hold that key and test an ordinary Fn-layer assignment, then release it and confirm normal Main-layer typing resumes.
  4. Keep a working Fn entry before changing the original Fn key. If the App warns that Main has no available Fn entry, restore one before saving.
  5. Save to the keyboard and test both layers again.

Fixed system shortcuts still use their factory physical positions. Moving an ordinary Fn-layer entry does not move protected connection, reset, or other fixed system combinations. If the App warns about using multiple Fn keys with the current firmware, keep one working Fn key instead of relying on the layer staying active until the last Fn key is released.

Existing shortcuts can run on the keyboard

On supported Blade and Flux keyboards, the App automatically converts eligible shortcuts into native key combinations when it applies the profile. Existing assignments on both the Main and Fn layers work without rebinding. For example, Copy can send Ctrl + C on Windows or Command + C on macOS, according to the computer where the App applies the profile.

Native combinations are executed by the keyboard. Use Save to keyboard to retain them for use after the App closes or the keyboard loses power. Test the shortcut in the intended application, including pressing, holding, and releasing it.

Support depends on the connected keyboard and its firmware. Eligible shortcuts combine one ordinary keyboard key with modifiers such as Ctrl, Shift, Alt, or Command. Application launch actions and shortcuts with special timing can still require the App to remain running. If the keyboard does not support native combinations, the App continues to handle the shortcut. When moving between operating systems, apply the profile through the App on the destination computer before saving it there.

Reserved PS5 shortcut

On supported Blade and Flux models that use Fn + Insert for PS5 mode, the physical Insert key on the Fn layer is reserved. The App prevents assigning another action, disabling it, or using it as the source of an advanced-key assignment. The Main-layer Insert key and choosing Insert as another key's output remain available. See Use PS5 keyboard mode for the switching sequence.

Disable, clear, and restore are different

Action Result on the selected layer
Disable Prevents the key's configured keyboard behavior from acting, including an assigned macro or advanced action. It also prevents the key from taking priority in an RS/SOCD pair.
Cancel Disable Re-enables the retained assignment. If its output was empty, it still has no output; re-enabling does not restore a letter. Resolve any assignment conflict the App reports before retesting.
Clear Key Value Clears the output, not the physical key's participation in an RS/SOCD pair. It does not restore the printed key or cancel an existing Disable state.
Assign a new ordinary key or macro Replaces the mapping and re-enables the key in the current App. Recheck Disable after changing its assignment.
Clear all Clears custom mappings and re-enables disabled keys across layers. It does not remove advanced-key assignments, RT, travel or lighting settings. Read the confirmation before using this broad reset.

An empty mapping means no assigned output, not “use the original key.” For example, an enabled SOCD member with an empty output can still suppress its partner. Remove the pair assignment or use Disable if that member should no longer participate. To recover ordinary typing, remove any advanced assignment and restore the original mapping as needed.

Remapping with RT and advanced keys

RT follows the physical key you select, not the letter it outputs. Remapping W to Up Arrow leaves RT on physical W; turning RT off does not undo that mapping. Disable selected keys on the Rapid Trigger page turns off RT only, unlike Disable in Remap.

RS/SOCD allow ordinary keyboard output changes in Remap while retaining the pair's priority rule. DKS, MT and Toggle use their own action assignments: edit them in Advanced Keys, or remove the advanced assignment before adding an ordinary remap or macro. Clearing an individual DKS row or MT action leaves just that action empty; it does not disable the whole physical key or substitute its printed letter.

Read Configure Rapid Trigger for the combination rules and Main/Fn behavior. Do not force a combination the App rejects or treat Disable as a replacement for Gamepad Mode's keyboard-output controls.

Confirm success

The selected key produces the intended action on the intended layer, essential shortcuts remain reachable, and the App shows no unsaved or failed state.

Save result

The preview can be active only for the current session. Disconnect or switch profiles only after explicit device-save success.

Limits and cautions

Recovery

Restore the noted original action, reload the last confirmed profile, or restore the current key or layer to default. Save the recovered mapping only after essential keys work again.