# Creating a keyboard remapping tutorial

**URL:** https://community.keyboard.io/t/creating-a-keyboard-remapping-tutorial/343
**Category:** Programming
**Created:** [September 28, 2017, 6:56pm UTC](https://community.keyboard.io/t/creating-a-keyboard-remapping-tutorial/343 "2017-09-28T18:56:23Z")
**Posts on this page:** 1
**Showing post:** 10

<div class="post-metadata">

### Author: ![algernon](https://yyz1.discourse-cdn.com/flex031/user_avatar/community.keyboard.io/algernon/32/4404_2.png) [@algernon](https://community.keyboard.io/u/algernon)
#### Post date: [September 30, 2017, 8:06pm UTC](https://community.keyboard.io/t/creating-a-keyboard-remapping-tutorial/343/10 "2017-09-30T20:06:58Z")

</div>

> [@Preparing plugins for 1.0.0: Looking for documentation reviewers](https://community.keyboard.io/t/preparing-plugins-for-1-0-0-looking-for-documentation-reviewers/263/44):
>
> @algernon - do you think it’d be plausible to move away from the custom code to toggle numlock? (Note that i’m not asking you to try to make the change, just whether you think it’s plausible 😉

It’s a custom macro-like thingy for a number of reasons, including the LED effect. Mostly the LED effect, actually. The code we had before had trouble restoring the previous effect, and couldn’t stack with it, and that ended up being more confusing than it needed to be. I don’t think it’s plausible to go back to just using `Key_Keymap2`, not without sacrificing something else.

---

_[View the full topic](https://community.keyboard.io/t/creating-a-keyboard-remapping-tutorial/343)._