Can (and probably will) get inaccurate with detections.
If you’re planning to use this for detecting controls, don’t. Use UserInputService and ContextActionService, they’re the best at that. (Should also note that controls can dynamically change)
Dear everyone.
Starting from September 4, 2020. This module won’t be updated and maintaned anymore since I am abandoning and quitting Roblox (read my main account’s bio for more information), I will only update if something breaks. Thank you for supporting and using this module.
This post and my website will still be up however.
Until I can get that account back, I will be posting from here.
V2 released, an rewrite. As of October 4 2021, this module is not truly 100% guranteed to have full and correct detections, I was able to think of some ways that it can result false positives.
Note to users using V1: Multiple things (including method names, and return types) has changed, some of the detections are also optimized, an updated API documentation will be soon available
Can you elaborate on fixing what? If you’re talking about detection false positives, it’s not really fixable, the engine is obviously better at detecting things like what the module does
As people has said, develop your games to match any control changes, take example fron Lumber Tycoon 2 or Flood Escape 2, you can change from keyboard with mouse to controller anytime, etc