After updating to the new AM 2.4, it seems the "minimum_run_time" variable is broken or not working properly. As we know, steam is problematic with AM because there are usually 1-2 loading splash screens before the actual game takes over. At the very least, there is one steam window that pops up briefly that says "launching x" whenever you play a game. After that, sometimes there is even another splash loading screen (SFV and DBFZ are both like this).
In the previous versions, setting the minimum_run_time variable would wait a number of seconds before AM started looking for the game to see if it is in focus, then would being AM back into focus once that game is closed. Now, AM will launch the game, I see the steam "launching game" window, that window goes away, and AM regains control again. The game does launch but AM is taking inputs still (I hit x and it tries to launch another game), thinking it is now the window to be in focus, because the steam launch window closed. This would happen in older versions if the "minimum_run_time" variable was not changed, but now it seems to be happening again despite the setting being there. Any help with this?