{"author_name":"MiniBobbo","cat":"LD #30","comments":[{"author_name":"Sruloart","time":"August 21, 2014 7:55 am","epoch":1408625700,"text":"This is cool. Very cool. ‘This should be in HaxeFlixel’s addons’ kinda cool. PULL REQUEST AT ONCE! \":)\"
\n BTW, MIT license?","spam":"N"}],"epoch":1408567860,"likes":3,"metadata":{"p_key":"29235","p_author":"MiniBobbo","p_authorkey":"22584","p_urlkey":"64697","p_title":"HaxeFlixel InputHelper","p_cat":"LD #30","p_event":"LD30","p_time":"1408567860","p_likes":"3","p_comments":"1","p_status":"UPD5","us_key":"22584","us_name":"MiniBobbo","us_username":"\/author\/minibobbo\/","event_start":"1408665600","event_key":"24","event_name":"LD30"},"text":"

Have you ever received a comment like “I would like to play this, but I use an AZERTY keyboard layout and the controls are impossible” or “I wish that key X did this instead of Y”? \u00a0Ever spent time hard coding\u00a0user inputs into a game only for it to be a pain to change it around? \u00a0Ever wasted precious time writing a way for users to change their own keys in game? \u00a0Oh, and happen to use HaxeFlixel?<\/p>\n

If you answered\u00a0yes<\/strong> to any of these questions, then you need\u00a0InputHelper<\/strong>, the new simple way to map keyboard keys to game functions without the hassle, available now for HaxeFlixel for the low, low price of… nothing<\/strong>!<\/p>\n

InputHelper <\/strong>is a small helper application for HaxeFlixel games. \u00a0It abstracts the interface between the user and the game through a series of virtual buttons that can be mapped to different functions. \u00a0Instead of checking against the keyboard, mouse, or gamepad and updating your game objects, InputHelper has you check against buttons named\u00a0up, down, left,<\/strong>\u00a0or\u00a0right\u00a0<\/strong>plus any additional buttons you define.<\/p>\n

<\/span><\/p>\n

Next,\u00a0add any virtual buttons you want with\u00a0InputHelper.addButton(buttonName)<\/span>. \u00a0Does your game need a jump button? \u00a0InputHelper.addButton(“jump”)<\/strong>. \u00a0Attack\u00a0button? \u00a0InputHelper.addButton(“attack”)<\/strong>. \u00a0 \u00a0Throw flaming gopher button? \u00a0InputHelper.addButton(“FlamingGopher”)<\/strong>. \u00a0Now those gophers are ready to fly!!<\/p>\n

Keyboard keys can be assigned to your virtual buttons simply\u00a0by calling\u00a0InputHelper.assignKeyToButton(Key, buttonName). \u00a0<\/span>Want multiple keys assigned to the same virtual button? \u00a0No problem!! \u00a0By typing InputHelper.assignKeyToButton(“W”, “up”);<\/strong> and\u00a0InputHelper.assignKeyToButton(“Z”, “up”);<\/strong> both QWERTY and AZERTY keyboard users can both press up in the way they want. \u00a0Your game objects will be checking against the virtual button and won’t know the difference!!<\/div>\n
<\/div>\n
Every game loop, call\u00a0InputHelper.updateKeys()<\/span>.\u00a0\u00a0Once that is done, use\u00a0InputHelper.isButtonPressed(buttonName)<\/span>\u00a0or one of the other functions in place of the FlxG.keys functions. \u00a0Done!<\/div>\n
<\/div>\n
But that’s not all. \u00a0Download InputHelper in the next (Editor note: Insert days\u00a0to next Ludum Dare here) days and receive InputHelperMenuState\u00a0absolutely free<\/em><\/strong>!!!<\/div>\n