Oh yeah, thanks for pointing that out I pretty much went with first thing I saw on top the page with 'go to' line function search, still getting hang of coding and it was literally in next code func below.
Anyways think you might be correct with rapid inputs, did some stress test with large images all that was achieved creating lag spikes no change in script flow, only when mashing button inputs you get the problem and a lot sooner in frenzy manner.
Not certain that this is the only gap, but neither the key press event for skills nor the skill button press function checks the battle state before doing stuff. Adding the following couple of lines to the start of pressskill(), should cover this gap.
func pressskill(skill):
if period != 'base' && period != 'skilltarget':
return
Note that this site converts leading tabs to spaces, so you will need to convert them back to tabs.
This should mean that the window for pressing the 1 key after a mouse click was only about 1/30 of a second.