# How to transfer/keep PlayerMappableOptions when remapping

**URL:** <https://forums.unrealengine.com/t/how-to-transfer-keep-playermappableoptions-when-remapping/736479>\
**Category:** Blueprint\
**Tags:** unreal-engine, Blueprint, question\
**Created:** [December 26, 2022, 6:40pm UTC](https://forums.unrealengine.com/t/how-to-transfer-keep-playermappableoptions-when-remapping/736479 "2022-12-26T18:40:10Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![rokenrock](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/rokenrock/32/1040844_2.png) [@rokenrock](https://forums.unrealengine.com/u/rokenrock)\
**Post date:** [December 26, 2022, 6:40pm UTC](https://forums.unrealengine.com/t/how-to-transfer-keep-playermappableoptions-when-remapping/736479/1 "2022-12-26T18:40:10Z")

</div>

I think I’m missing something, but whenever unmapping a key and mapping a new one, nothing saves.  
This makes sense since they’re different inputs, and different inputs can have different settings, but you can’t copy the settings over through the struct so I’m not sure how to go about this.

 ![image](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/d/a/2da98ea925df3950a9c49055a642310758f9e2ae.png)

Thank you.

---

<div class="post-metadata">

**Author:** ![hbiblia](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/hbiblia/32/591965_2.png) [@hbiblia](https://forums.unrealengine.com/u/hbiblia)\
**Post date:** [December 26, 2022, 8:02pm UTC](https://forums.unrealengine.com/t/how-to-transfer-keep-playermappableoptions-when-remapping/736479/2 "2022-12-26T20:02:34Z")

</div>

Acabo de probar lo mismo que usted tiene y me funciona bien, no creo que su Mapping Context sea nulo lo más probable sea el action que sea diferente al que está observando.

 ![image](https://d3kjluh73b9h9o.cloudfront.net/original/4X/a/c/5/ac51acf6e75df5a69cf69b209e9435c0e70a0d0f.png)

---

<div class="post-metadata">

**Author:** ![rokenrock](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/rokenrock/32/1040844_2.png) [@rokenrock](https://forums.unrealengine.com/u/rokenrock)\
**Post date:** [December 26, 2022, 10:58pm UTC](https://forums.unrealengine.com/t/how-to-transfer-keep-playermappableoptions-when-remapping/736479/3 "2022-12-26T22:58:28Z")

</div>

The results are still the same, even using the return value from map key and using a variable for the action to ensure it’s the same one.

 ![image](https://d3kjluh73b9h9o.cloudfront.net/original/4X/6/1/6/6169cc7d7e16580006b6a537eed076f28f130ce1.png)

It also shows in the context asset itself.  
Before running the unmap-remap:

 ![image](https://d3kjluh73b9h9o.cloudfront.net/original/4X/0/9/0/0904824cf6b664bec0321c75d15eb22825c22427.png)  
After the remapping:  
 ![image](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/e/7/2e72cf8b3164c56a42954571b88e227f3883daff.png)

If I remove the Unmap Key node, we can see the intermediate:

 ![image](https://d3kjluh73b9h9o.cloudfront.net/original/4X/9/9/e/99ed51c1a66692aab7f3df2e04f8b038a0c8c8c5.png)

Player mappable options is also not transferred.

> 

I’m thinking that it may be solved by using the add player mapped key and remove player mapped key nodes, but since the interface isn’t implemented, it doesn’t do anything.

 ![image](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/a/8/2a81c8000914a1bb80981abc382ddd8ea415a0be.png)

---

<div class="post-metadata">

**Author:** ![hbiblia](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/hbiblia/32/591965_2.png) [@hbiblia](https://forums.unrealengine.com/u/hbiblia)\
**Post date:** [December 27, 2022, 2:06am UTC](https://forums.unrealengine.com/t/how-to-transfer-keep-playermappableoptions-when-remapping/736479/4 "2022-12-27T02:06:48Z")

</div>

Que versión de Unreal Engine tiene ? Yo tengo la 5.1 y la 4.27.2

---

<div class="post-metadata">

**Author:** ![rokenrock](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/rokenrock/32/1040844_2.png) [@rokenrock](https://forums.unrealengine.com/u/rokenrock)\
**Post date:** [December 27, 2022, 3:13am UTC](https://forums.unrealengine.com/t/how-to-transfer-keep-playermappableoptions-when-remapping/736479/5 "2022-12-27T03:13:48Z")

</div>

This is in 5.1, but I have 5.03 and 4.27.2.

---

<div class="post-metadata">

**Author:** ![hbiblia](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/hbiblia/32/591965_2.png) [@hbiblia](https://forums.unrealengine.com/u/hbiblia)\
**Post date:** [December 27, 2022, 7:23pm UTC](https://forums.unrealengine.com/t/how-to-transfer-keep-playermappableoptions-when-remapping/736479/6 "2022-12-27T19:23:51Z")

</div>

Aquí tienes una prueba en 5.1.

Si te funciona quiere decir que es una config en tu proyecto y si no funciona parece que es un problema de tu versión de UE.

[hbiblia/Enhanced-input-system-remapping-5.1: Enhanced input system remapping (github.com)](https://github.com/hbiblia/Enhanced-input-system-remapping-5.1)

---

<div class="post-metadata">

**Author:** ![rokenrock](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/rokenrock/32/1040844_2.png) [@rokenrock](https://forums.unrealengine.com/u/rokenrock)\
**Post date:** [December 27, 2022, 10:43pm UTC](https://forums.unrealengine.com/t/how-to-transfer-keep-playermappableoptions-when-remapping/736479/7 "2022-12-27T22:43:34Z")

</div>

I downloaded that project, but it doesn’t address my issue.  
My problem isn’t that I can’t rebind a key, it’s that it doesn’t save the player mapping settings when I do so.  
Your input mapping context doesn’t have player mappable enabled to start.

---

<div class="post-metadata">

**Author:** ![rokenrock](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/rokenrock/32/1040844_2.png) [@rokenrock](https://forums.unrealengine.com/u/rokenrock)\
**Post date:** [February 14, 2023, 7:51pm UTC](https://forums.unrealengine.com/t/how-to-transfer-keep-playermappableoptions-when-remapping/736479/8 "2023-02-14T19:51:28Z")

</div>

**An edit after the fact- it seems that this process has been massively simplified in 5.3. I haven’t had the time to upgrade to 5.3 and get a comprehensive look, but it may now be as simple as it should’ve been.**

So the solution to this involves quite a few steps, and doing anything wrong breaks everything, but I’ve finally figured it out.

**One note → Absolutely Never use RemovePlayerMappedKey**   
It will break everything.

* * *
  

First, you have to get an array of all your contexts. As far as I know, there’s no way to use this method and save to the contexts. Though, this may be considered a positive since you don’t have to save defaults- these contexts will always have their default values, meaning don’t check them for current values (cause they won’t be).

 ![image](https://d3kjluh73b9h9o.cloudfront.net/original/4X/a/4/6/a46753c351b87098461bab3b2cc6884052b327d2.png)

* * *
  

Second, you have to apply all your mappings from those contexts, making sure to enable apply immediately. This should be done on begin play.

 ![image](https://d3kjluh73b9h9o.cloudfront.net/original/4X/c/9/e/c9e77825cbb0bfa6b66a6fc6dce9d55f30ec3ab2.png)  
The GetAllPlayerMappableActionKeyMappings macro in this image is just made cause I use it so often, but what it does is gets all the mappings from every context, checking if they’re player mappable. This can be done with a built in function of the same name, but that only checks active contexts. It can be substituted for this:  
 ![image](https://d3kjluh73b9h9o.cloudfront.net/original/4X/1/c/5/1c55865af6bcdb636918141780ad82fc77196ee4.png)

* * *
  

I have my GetKeybind in a function library, but you can put it anywhere. This is how I’ve implemented it. This will work so long as you’ve done the previous steps prior to calling this.

 ![image](https://d3kjluh73b9h9o.cloudfront.net/original/4X/8/9/e/89e08cc51ea6fd4bd35642c73dd4442a792d793d.png)

* * *
  
This is the function I'm using to change keybinds. Pretty simple- just use the name you've assigned to the keybind and make sure to call save.

 ![image](https://d3kjluh73b9h9o.cloudfront.net/original/4X/6/4/7/6476c221617d7b4d5887dedf9498f0d700cc2e83.png)

 ![image](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/f/0/2f00c8a07400e9e15c33b00a84893d59a63dffda.png)

* * *
  
  
**This part forward is for saving and loading**  
  

After pushing these changes in the first step, check whether there is a save for keybinds already. If yes, load.

 ![image](https://d3kjluh73b9h9o.cloudfront.net/original/4X/e/4/6/e469ece744d656eaa20d668f74e7cb5c83ef1352.png)

The loading is straightforward, just make sure to use the player controller input subsystem:

 ![image](https://d3kjluh73b9h9o.cloudfront.net/original/4X/6/3/9/6393269b2d7924ea6e4f4e71bb66d212c5fcfc10.png)

And the loading is even simpler. I’m using the same macro as I used before, and I’m just adding the data to a map in the savegame. Saving is done whenever a keybind is changed.

 ![image](https://d3kjluh73b9h9o.cloudfront.net/original/4X/4/2/c/42c4db65f1dd0b60850ae8d149cd5aea798a90fc.png)

---

<div class="post-metadata">

**Author:** ![slam.js](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@slam.js](https://forums.unrealengine.com/u/slam.js)\
**Post date:** [September 20, 2023, 3:50pm UTC](https://forums.unrealengine.com/t/how-to-transfer-keep-playermappableoptions-when-remapping/736479/9 "2023-09-20T15:50:55Z")

</div>

Hello, in 5.3 it’s missing PlayerMappableOptions and IsPlayerMappable bool  
Is there a workaround?

---

<div class="post-metadata">

**Author:** ![rokenrock](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/rokenrock/32/1040844_2.png) [@rokenrock](https://forums.unrealengine.com/u/rokenrock)\
**Post date:** [September 20, 2023, 7:53pm UTC](https://forums.unrealengine.com/t/how-to-transfer-keep-playermappableoptions-when-remapping/736479/10 "2023-09-20T19:53:27Z")

</div>

An edit after the fact- it seems that this process has been massively simplified in 5.3. I haven’t had the time to upgrade to 5.3 and get a comprehensive look, but it may now be as simple as it should’ve been.

There have been a few changes to that.

First off, in the input action you have to select the experimental option under player mappable key settings. This is warned to not be supported long term, so be careful.

 ![image](https://d3kjluh73b9h9o.cloudfront.net/original/4X/8/5/2/852ed35591c0fd3f9f0096b4c83d980abe0e1cf7.png)  
You can then change settings:  
 ![image](https://d3kjluh73b9h9o.cloudfront.net/original/4X/7/5/9/759c80e37445d14982e956f942ec21c76e30dc8b.png)

PlayerMappableOptions are now called PlayerMappableKeySettings.  
There isn’t an explicit IsPlayerMappable bool, but if the player mappable key settings are valid that means you’ve defined it to be player mappable.

 ![image](https://d3kjluh73b9h9o.cloudfront.net/original/4X/5/2/7/527f0829c5de25ad699461370b118450fadc1b3e.png)

---

<div class="post-metadata">

**Author:** ![Spacemarine658](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/spacemarine658/32/1194677_2.png) [@Spacemarine658](https://forums.unrealengine.com/u/Spacemarine658)\
**Post date:** [October 17, 2023, 1:35am UTC](https://forums.unrealengine.com/t/how-to-transfer-keep-playermappableoptions-when-remapping/736479/11 "2023-10-17T01:35:51Z")

</div>

this limits us to a single key if we can only use the IA to store the settings, I was hoping to find a way to access the override settings in the context but alas so far I haven’t figured out how to access this if I can figure this out I can finally finish

 ![image](https://d3kjluh73b9h9o.cloudfront.net/original/4X/f/4/3/f43e88fb9caff012d120adf3d11c252318dc38b4.png)  
t

---

<div class="post-metadata">

**Author:** ![ShadowBr0kerz](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/shadowbr0kerz/32/1201558_2.png) [@ShadowBr0kerz](https://forums.unrealengine.com/u/ShadowBr0kerz)\
**Post date:** [September 4, 2026, 1:47pm UTC](https://forums.unrealengine.com/t/how-to-transfer-keep-playermappableoptions-when-remapping/736479/12 "2026-09-04T13:47:54Z")

</div>

the reason nothing saves is like you said — `Unmap + Map` creates a new struct without the `PlayerMappableOptions`, so UserSettings cant track it. you need to read the original `.PlayerMappableOptions` from the mapping you unmapped and feed it into the new mapped key (or use the UserSettings nodes correctly: `Get Player Mapped Keys` → pinch the options → pass them to `Map Player Key`). also make sure you call `Save Settings` after and that the mapping context is registered via `Register Settings` — if the context pointer is null in packaged it also silently fails like your screenshots show.

advanced enhanced input key remapping [Advanced Enhanced Input Key Remapping / Binding / Profiles / Local & Cloud Save. | Fab](https://www.fab.com/listings/e8a77976-b4d4-4e8f-a4b4-c6a71a98554d) handles that copy for you automatically — it keeps PlayerMappableOptions (name, display name, category) intact across remaps so saving actually persists, and caches originals for Reset to Defaults.
