Input in the game is weird. The input for sceptile's dragonbreath needs to be input rapidly, but the actual move doesn't show up until a second later.
It reminds me of Castlevania Judgement where instead of moves being as you pressed them and ignoring presses while you were in something that couldn't be canceled, it simply queued your button presses, which took some getting used to.
Yea, I think I noticed that too, it really feels like it is queueing the inputs. I get the same thing in smash sometimes, almost makes me wonder if that is how the wii u handles input at a system level
EDIT: Kinda like how notifications on PS4 are in a queue so if you don't have enough room for a download and it keeps retrying then the notifications are being added to the queue faster than the notifications are being displayed and when you eventually go and stop the download from retrying there is still tons of notifications queued that will be popping up on the screen for ages
EDIT2: Unrelated to Pokken at this point but the notifications queue on PS4 should maybe have something that checks if the notification it is trying to add to the queue is already in the queue then don't add it again. I dunno, this might fix the issue mentioned in my first edit
EDIT3: But then the check before adding to the notification queue might end up actually making a noticeable drop in system performance, I dunno, ignore me
EDIT4: Would using a HashSet (constant lookup time) be better than a queue? Sets don't allow duplicates and can still be used in FIFO manner like a queue. Am I completely wrong here?
EDIT5: Edit4 was related to ps4 notification queue and not pokken input queue, also it looks like in C++ an unordered_set would be what to use and not a hashset? unordered_set has constant lookup and can be used fifo?
EDIT6: unordered_sets probably cant be used fifo without doing something reducing performance and breaking constant lookup, I don't know what I am saying at all
