Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Keyboard number codes and gamepad number codes. #202

Open
YYBartT opened this issue Oct 30, 2024 · 0 comments
Open

Keyboard number codes and gamepad number codes. #202

YYBartT opened this issue Oct 30, 2024 · 0 comments

Comments

@YYBartT
Copy link
Collaborator

YYBartT commented Oct 30, 2024

Original helpdesk ticket: #205750

Description: Hello,

I have recently been working on making my own controller / keyboard remapping feature in a game and I wanted to ask a question. When de-bugging keyboard inputs it appears the accepted range of values that can be deemed as a keyboard input range from 0 - 223. Can you confirm this is correct? (223 being equivalent to the tilde key). Although it seems at least 0 - 3 is reserved for the mouse (does it go higher than that for the mouse?). When testing a gaming mice it did not seem to detect any inputs above 3 (although it may be because I don't have the correct software installed for that mouse to allow detection of additional buttons?).

I also noticed that accepted gamepad values range from 32769 (for gp_face1) & 32788 (for gp_axisrv).

Is it possible I could have a list for all accepted input numbers for keyboard & mouse as well as the gamepad as well as any other supported number ranges? I don't even really need the names for all of them just the accepted ranges for the numbers when listening for an input (also the appropriate function like gamepad_button_check(); if possible) from the player so I can assign the correct button mapping when inputted & not miss any possibilities.

I know in the manual it states the inputs ranging from gp_face1 to gp_axisrv but it seems odd that there is a large gap from 233 (for keyboard inputs) then straight to 32769 & beyond for the gamepad. Are there others that are not listed in the manual for example?

or am I just better off hazarding a guess of ranges from 0 - 40,000 as accepted input ranges for a for loop? (seems a bit intensive) - Then just putting that into each function when listening for inputs for re-assignment? - I can pretty much figure out what to do if I had all the approved input number ranges though.

Any help would be greatly appreciated so I don't miss any inputs thank you! I was previously told about input5 but I am interested in how it all works and being able to do it myself using game maker so I can learn more about it.

If I could be sent the number ranges that would be extremely helpful! Thank you!

Benefit: It would be very helpful to know what inputs are supported in game maker and to be able to ensure supporting them all. It seems not all of them are listed? At least their numerical values aren't listed but their enum values are? (Not really sure how game maker works under the hood).
Link:

@stuckie stuckie moved this from Triage to Todo in Team Workload Oct 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Todo
Development

No branches or pull requests

1 participant