After a lot of re-structuring, under-estimating, testing, and finally figuring out publishing with Butler, I've released v1.2.0-a with full Xbox Controller Support.

Is your game really a platformer without it?

I have to say the game plays very nicely using the controller, albeit seemingly more difficult. Though I think that's mainly due to the 100+ hours of development and testing spent using mouse and keyboard. It definitely feels like a game that should have controller support, so I went through the somewhat arduous task of implementing this over the last couple of days.

I'd be really keen to hear your thoughts on the button layout. As mainly a PC gamer after moving away from consoles a few years ago, it's been a while since I made use of the controller outside of Rocket League. If something feels off, or like it would be better suited to another button, please let me know! Obviously controls will be fully customisable some day, as I believe that's a very important feature. However, it can take a back-seat for now while I continue developing the core game.

So give it a try with your preferred input method, maybe even try both and let me know if one is lacking or could use improvements, all constructive feedback is always more than welcomed!

As always, a few bugs were introduced uncovered and resolved, as well as a couple of quality of life improvements for the player added. The main focus here was getting controller support added ASAP, so the list of changes this update is relatively small, check it out below.

Thanks as always for checking out TurtleRun and if you have any feedback or suggestions on how I can improve it, I'm all ears.

New Content

• Added support for Xbox  controller
  • Can switch during a run by simply pressing a key/button on your preferred input device

Changed Content

• Replaced sign and item pickup markers with relevant key-bind indicators
• Created dynamic indicators for skipping text based on input type

Bug Fixes

• Fixed a bug where you could get soft-stuck in a corner if you tapped to face the opposite direction, this would prevent jumping. Fixed by evening out collision masks
• Fixed a bug where pausing on one input device and unpausing with another caused markers to appear differently

Many thanks,

-Cappiche