Simple keymapping code design question.

Hello,

I've been researching keymapping for the game I am creating, but need some initial direction. I know I don't want to use a simple "when x is pressed" architecture since I want the user to be able to use different input systems (primarily keyboard/controller) and be able to customize keys if they want to. I've already figured out how to code my input, so now I'm just trying to narrow down how I should go about building a new long-term input architecture in terms of objects/extensions for different input systems and key customization. There are a ton of joypad/input objects and control extensions and I simply don't know where to begin. I don't want to invest hours into learning one just to find out it can't do what I need it to do, if it can be avoided.

So for anyone with experience who might have an answer immediately offhand, what objects/extensions would you use in the following scenario?

A platforming game where the user has standard movement (left, right, up, down, jump, hold-jump, crouch) being controlled by a Platform Movement Object, but also has 4 attacks, 8 weapon switches, and a few additional buttons beyond those. I want the user to be able to switch directly to the different weapons when playing on keyboard, but that creates too many buttons for a standard controller so I would need next/previous weapon buttons as well, primarily for controller players. Basically I need a ton of buttons. I need to be able to at least set what the default buttons would be for the keyboard, and if possible also allow the user to customize the buttons (I assume the latter goes with the former anyway).

Mainly I just don't want to end up having to redo my input architecture down the line so I want to make a good choice early on here. Essentially I'm just looking for a lead on what control objects I should start with given this scenario, and I will go research those on my own time. Even if I decide at some point I don't want customizable keys, having it fundamentally built-in already at no processing cost is definitely going to be a good thing if I change my mind again at some point.

Thanks a bunch!

-eido

There's some good info/examples here - http://community.clickteam.com/threads/91915-You-thoughts-on-Custom-Key-mapping?highlight=joypad

I'd recommend Joy Stick 2, Control X and/or The "Key Object" (I think that's what it is called)

I'm going to re-do my controller mapping soonish.. but the good news is, I only need to re-do the Inputting phase (where the user assigns keys) the actual custom input system during gameplay works flawlessly. I might post that up as a guide for others when I get back around to that task.

Thanks for the reply! I got absorbed in working on animations instead but I'll bookmark the discussion for later, and look up those extensions.

Thank you!

I find the best approach to create the character a few values, one being for example "p.movement". I check if this value is "2" and the player moves to right, "4" for left.
Why this? It is much easier to add more moving options later on. I can add controller support by using only a few lines.

I use Control X object for key mapping, works great!
Though it is not unicode, not sure how it works in certain countries (though I believe it will use normal alphabets in foreign keyboards, so in theory it should work).