REQUEST (Android App): add quarters when writing an 'Arcade' game?

[psybertech]

Love the Android app so far! (THANK YOU!)...
A request if possible...

When writing an 'Arcade' game, can there be a checkbox and text input(s) to add quarters automatically?

I know I can write custom commands to do this, but when just picking a game from the Arcade section in the app when searching, it would be nice to have the option to launch the game and then add some quarters to it once it launches directly from the app on the phone - on-the-fly.
so... Pick game, enable adding quarter(s) and write.

So something like (forgive me if I am off here - just started with this):
'_Arcade/Street Fighter.mra||**delay:25000||**input.coinp1:4'

The checkbox would be to enable adding quarters, an input for the time delay (in seconds to cover the boot time) and maybe an input for default quarters to add (1-10?).
It could be an option to enable in the main settings or on the 'write to tag' section when selected if it is an arcade game.

Anyway... just a thought.

Thanks, Mr. Wizzo!!!!

cheers!
j

[wizzomafizzo]

This is worth keeping, but the hard part is app UX rather than Core capability. Core already has the pieces needed to launch, delay, and insert coins.

The open question is how to expose this without cluttering the normal write flow for every other system. This is useful for Arcade/MRA workflows, but irrelevant to most other systems.

A possible shape is a contextual/collapsed "Arcade options" section that only appears for Arcade/MRA results, with an opt-in "Add credits after launch" toggle, credit count, and delay strategy (fixed delay or media-ready if suitable). Non-Arcade results should not show these controls.

So this should be treated as an app UX/design issue: useful feature, but narrow system scope and needs careful placement.

[Firehawke]

You're going to also hit all sorts of fun in working out exact delay per-machine; most arcade boards won't accept a coin-up during self-test and you can run into fun issues with how long a coin impulse should last. Too long will trigger coin mech errors on most machines, too short often won't trigger the coin-up.

Automating this stuff is painfully per-machine and no amount of good UI/UX can make it much easier; you're going to end up doing a lot of legwork in the end.