Add the ability to queue transactions

[ammodev]

As stated in the title there should be an option to queue transactions using either a rate limiter (only one transaction per second... not exactly user friendly) or have the transactions queue up and execute in batches of "n" transactions per second. The second option would need an implementation of the shop queueing the transactions and then summing up the value which finally gets put through to vault.

The current issue is that the shop will perform transactions "as given" by the user, resulting in users just using autoclicker on the buy button to crash the server.

We are using our custom vault implementation which saves transactions to the database and not a file. Same results in querying transactions. This also has to be done with the database and not a file resulting in higher query times. I guess we are not the only ones using a database tho. So this will apply to multiple customers and users.

[ammodev]

We enabled the close gui after buy option for a quick fix. But there should still be a system which stops users from doing this as closing the gui is not a good user experience.

[XZot1K]

^^^ [Dev Note] During the revision process of the GUI system, separate the unit count into its own menu so that its a light task. Then the finalization screen is where the balance check and single button is where it handles it all (placing a cooldown on that button or locking it when pressed as well).