demo project - https://scratch-mit-edu.ezproxyberklee.flo.org/projects/1136942944/

I'm not sure if this supposed to be in B&G (if so please report), also this might be a dupe. While clicking multiple arrow keys at a time, such as left + up + right, the third key pressed doesn't register. For example, if I click the up arrow, hold it along with the left arrow, then hold that along with the down arrow, the down arrow won't register. I don't know if this is just my computer, but is there a workaround to this?

(Also - it seems like Scratch can theoretically register all the alphabet keys, but sometimes after holding ~3 the fourth or so doesn't register.)

Did you test that key combination on other apps/devices? If you are using a laptop keyboard, some key combinations will not register properly due to how laptop keyboards are made.

Like EpicGhoul said above, the results of this will depend on your keyboard, so it will vary from user to user.

Another vote for this being a hardware issue - just the way the keyboard hardware works.

What kind of computer/keyboard are you using? I can only get two arrows aswell, i managed to get five letters at once; it's probably a keyboard thing, like deck and legendary said.
oh ahem browser: My browser / operating system: MacOS Macintosh X 10.15.7, Chrome 116.0.0.0, No Flash version detected

EpicGhoul993 wrote:

(#2)
Did you test that key combination on other apps/devices? If you are using a laptop keyboard, some key combinations will not register properly due to how laptop keyboards are made.

I haven't tested it personally, but some other people said that they could get all four keys working for WASD at the same time - also Koamodo got the same results.

legendary34678 wrote:

(#3)
Like EpicGhoul said above, the results of this will depend on your keyboard, so it will vary from user to user.

I understand - so there's no possible way to get more than two arrow key inputs if the computer is set that way?

Edit - here's my OS:
My browser / operating system: Windows NT 10.0, Chrome 131.0.0.0, No Flash versions detected
Currently using an HP laptop, not sure what kind specifically.

Mynxus wrote:

demo project - https://scratch-mit-edu.ezproxyberklee.flo.org/projects/1136942944/

I'm not sure if this supposed to be in B&G (if so please report), also this might be a dupe. While clicking multiple arrow keys at a time, such as left + up + right, the third key pressed doesn't register. For example, if I click the up arrow, hold it along with the left arrow, then hold that along with the down arrow, the down arrow won't register. I don't know if this is just my computer, but is there a workaround to this?

(Also - it seems like Scratch can theoretically register all the alphabet keys, but sometimes after holding ~3 the fourth or so doesn't register.)

Like @EpicGhoul993 has mentioned, it may be due to your keyboard model. To get into more depth about it, I'll start by mentioning that most keyboard models can only record around 3 to 6 simultaneous key presses at once. The reason being is called Key Rollover (KRO). It refers to the number of keys a keyboard can register as being pressed simultaneously. When you press a key, the keyboard sends a signal to the computer to register the input. However, how these signals are detected depends on how the keys are wired internally. Most keyboards use a matrix circuit where rows and columns intersect under each key. Pressing a key connects a specific row and column, sending a unique signal. Another thing you might want to take into consideration is Key Ghosting. Ghosting happens when pressing multiple keys causes an unpressed key to register. Most keyboard models will have an anti-ghosting system, but most of the time results in KRO. But, some keyboard models will have something called N-Key Rollover (NKRO). N-Key Rollover means a keyboard can register all keys pressed simultaneously without dropping any inputs. Whether you press 2 keys or 20 keys at once, NKRO will send a signal for every key press to make sure it's recognized accurately and independently. But once more there can be problems with NKRO as well. One being that pressing multiple keys can create unintended electrical paths, causing ghosting and blocking certain key combos.

Long story short, it's not your code that is wrong, it's simply the user's keyboard models. You will never be able to detect all key press inputs simultaneously, unless they use an NKRO modeled keyboard. Like I mentioned above, even the NKRO models can have problems so it would be unreliable.

I hope this solves your problem.

this is a hardware issue