KAZESUI'S PROFILE

There is one way to do this in a reasonable way using events for all of the graphic,
utilizing a kind of recursive event calling along with the use of pointers.
This means it'll take some time to set up the first big object, but the 6 others would go rather fast.

The gist of it, is that you let the big objects consist of all 12 events, which you let have a number of pages, with the top one dealing with interaction from the player. Important here is that the event ID's all form a consecutive sequence.
For example, let each event set "this event's" coordinates into wherever two pointer variables are pointing (one for x and one for y).

We'll call this page by setting a variable Event ID ptr to the first ID of the events in the big object, and a variable Event page Ptr to 1, since we want to access page number 1, when the use the event call by variables function.
The event page executes and stores the coordinates, we increase the event ID ptr by 1 and make the same event call. In the event with the highest event ID, we remove the event call to mark the end of the recursive chain.

And in the end, we now get a way to store the coordinates of every event in the big object easily, which is easy to copy paste to make new big objects to do the same, since the code is fairly generic. (just have to mind removing the event call for the one with the highest ID).

Using the same method, you could easily use change event location to replace all events in the big object easily by a similar call, as well as use move with phasing as well as terrain ID to determine if there's about to come an obstacle under any of the events.

here's a sample which shows it in practice: sample
(might help make more sense of the stuff I've mentioned so far)

Yeah, I probably should

Here's a sample with the tweaks you want sample 2

Also, you can adjust the maximum time for keypresses by altering the value of the variable "0009: Key Delay" in the second variable. 60 = 1 second, 90 = 1,5 seconds and so on.

Assuming we're talking 2k3 here, you could take a look at this minigame sample
It's a tiny project showing how you can probably do something sounding similar to the problem you're describing.

Basically a solution to it is to have "wait until key is pressed" to be unchecked and manually control how much time has passed with variables. This would also mean you'll have to manually check when the button has been released.

The sample up there generates a key to be pressed and shows a picture corresponding to this key. It then checks if a button is still being held down and continues to loop until it's released, while still counting towards the amount of time left. When released, it waits to see if the key input is not equal to 0, meaning a key has been pressed and if so, check if it's the right one. if it's still 0 the variable keeps on counting toward whatever threshold has been chosen.

Haha, yeah, I care enough to appreciate the vote. Thank you