Question About Official Modded Keybinding Setup (since v.2.06)

[kingofnuthin1980 53]

Hello guys,

 

I've tried the new Modded Keybinding, but it's not working for me. Even if using the examples:

https://community.bistudio.com/wiki/Arma_3:_Modded_Keybinding

Spoiler

class CfgUserActions
{
	class Mod_MyActionName // name, also used for inputAction script command and for internal representation
	{
		displayName = "My test action";
		tooltip = "This action does test things";
		onActivate = "_this call Mod_Myhandler";			// _this == bool, always true on activate
		onDeactivate = "_this call Mod_Myhandler";			// _this == bool, always false on deactivate
		onActionAnalog = "_this call Mod_MyAnalogHandler";	// _this == scalar (action analog state has changed)
		analogChangeThreshold = 0.1;			// minimum change required to trigger onAnalog EH, default 0.01
	};
};

class CfgDefaultKeysPresets
{
	class Arma2// Arma2 is inherited by all other presets
	{
		class Mappings
		{
			Mod_MyActionName[] = {
				0x25, // DIK_K
				"256+0x25", // 256 == bitflag for "doubletap"/2x, 0x25 == DIK code for K
				"0x00010000 + 2", // 0x00010000 bitflag for "mouse button"
			};
		};
	};
};

class UserActionGroups
{
	class ModSection // unique classname for your category
	{
		name = "Mod Section"; // display name of your category
		group[] = {
			"Mod_MyActionName"
		};
	};
};

 

 

WHAT HAPPENS:

• in the keybinding settings there will be a new category "Mods" with three entries:
  • "Camera"
  • "Editor Camera"
  • "Mod Section" (the one created by the example)
• but the keybind option "My test action" (Mod_MyActionName ) will be under "Editor Camera". The created entry "Mod Section" is empty

 

Everything else working fine. You can set the keybind and scripts are executed.

 

Any idea what I'm missing, to push the created entry into "Mod Section"?

EDIT: The "Camera" and "Editor Camera" settings are default settings. They just appear under "MODS" after adding the custom keybind. The default settings for "Editor Camera" are all gone and replaced by the custom keybind (Mod_MyActionName).

 

Thanks for throwing your brain cells into it 🙂

 

 

[da12thMonkey 1943]

Might not be the problem but get rid of the , (comma) at the end of the keybind array

			Mod_MyActionName[] = {
				0x25,
				"256+0x25",
				"0x00010000 + 2"
			};

I know it was in the example on the biki, but it shouldn't be there because it creates an array with a missing 4th bind instead of a completed array with the 3 listed ones.

[kingofnuthin1980 53]

28 minutes ago, da12thMonkey said:

Might not be the problem but get rid of the , (comma) at the end of the keybind array

			Mod_MyActionName[] = {
				0x25,
				"256+0x25",
				"0x00010000 + 2"
			};

I know it was in the example on the biki, but it shouldn't be there because it creates an array with a missing 4th bind instead of a completed array with the 3 listed ones.

 

I've totally missed that. Thanks!

 

As you considered, it doesn't solve the problem. The mapping works fine.

 

Also in config viewer everything looks fine, compared to the default configs. I don't see why it gets confused with existing keybind categories. 😕 And my created user action is the only one in CfgUserActions. The editor and editor camera categories shouldn't be in the mods-section. I haven't touched those with my three configurations.

[Ploo 0]

class UserActionGroups
{
	class ModSection // Unique classname of your category.
	{
		name = "Mod Section"; // Display name of your category.
		isAddon = 1;
		group[] = {"TAG_MyActionName"}; // List of all actions inside this category.
	};
};

Using the above, presented me with similar issues. I had to set isAddon to 0, and then the control section of "===Mod===" went away, and my group was properly populated.

[kingofnuthin1980 53]

On 1/18/2022 at 11:38 PM, Ploo said:

class UserActionGroups
{
	class ModSection // Unique classname of your category.
	{
		name = "Mod Section"; // Display name of your category.
		isAddon = 1;
		group[] = {"TAG_MyActionName"}; // List of all actions inside this category.
	};
};

Using the above, presented me with similar issues. I had to set isAddon to 0, and then the control section of "===Mod===" went away, and my group was properly populated.

 

I've used this as a temporary solution...
https://feedback.bistudio.com/T161263

...and set the requiredAddons in CfgPatches to A3_Data_F_AoW_Loadorder, e.g.:

requiredAddons[] = {"A3_Data_F_AoW_Loadorder", "A3_Modules_F", "A3_Functions_F", "A3_UI_F"};

Sorry that I forgot to update this post.