Keybinds for Google Play Games emulator
11 months ago
Canada

I was hoping to have the following clarified. For those that saw my previous comparisons and posts for IS2 load times, I've completely switched to Google Play Emulator. I find it has many benefits of load times, fewer crashes, and just being less sketchy software. That being said, the main downsides are that virtualization required for google play emulator doesn't play well with other traditional emulators, and the key, there are no keybinds.

Personally, I switched fully to mouse-only gameplay. Every single action is purely LMB.

That being said, as I've seen more people interested in speedrunning and wanting to try with Google play emu, as well as seen discussions about people using scripts and macros.

I wanted to hopefully clarify the following rule:

No macros.

Keybinds are OK, but any keybind that is mapped to 2 or more buttons is forbidden.

So as I mentioned, google play emulator has no keybinds built in. Would auto hotkey be a fair alternative?

Here's a sample script I wrote: x:: MouseGetPos, xpos, ypos MouseClick , Left, 2319, 174,,0 MouseMove , %xpos%, %ypos%,0

So, pressing X on your keyboard will:

  1. Record current mouse position on the screen
  2. Move the mouse to the pause button and click it
  3. Return the mouse to the original recorded position

Is this seen as a script/macro? Or as a keybind? The end result gameplay wise is that you paused the game. But the underlying required multiple steps to perform.

Figured I'd ask before runs start getting rejected for some people.

Edited by the author 11 months ago
United States

This would be viewed as a macro as it is taking more than one action from the keypress, which includes cursor movement, and would be forbidden.

While this script might be considered harmless, we do not want to set a precedent where lines are likely to be skirted. Generally, getting into speedrunning should be as "ready out of the box" as possible. Tools not available within the standard emulator and requiring different software would reduce accessibility.

The lack of built-in customizable controls for the Google Play Games emulator is something to be desired and hopefully Google will implement it in the future. I am also personally hoping for this feature as I would like to permanently move to GPG as it is less taxing on my system.

GL1TCH3D likes this
Canada

The main reason I bring this up is maybe to clarify the rules. In general, external programs outside of what is built into the game / device tend to be disallowed in speedruns unless generally agreed upon by the community. So I figure AHK would not be allowed under standard rules of play for a speedrun. That being said, some people might think it's harmless to make keybinds in AHK to be more comfortable in GPG without seeing the issue as the result is the same as a keybind in another emu, while the process is more complicated than the emu. So I would just add to the rules that keybinds must be native to the emulator and not another program.

Alternatively, as what other games have done, is have approved scripts, but I'm not sure that's what's right for what is really a mobile game.

United States

We can definitely add in the clarification. Thank you for the suggestion.

United States

Locking this thread due to bot abuse. Feel free to reopen a new thread if there are any further thoughts.

Game stats
Followers
190
Runs
912
Players
174
Latest news
Updated starting point for manual runs

Hello ! just a quick update about the starting point of manual runs.

During "So Long Adele" we stumbled across the issue of stages lagging at the beginning due to a lot of entities spawning at the same time which made the starting frame visually random. The solution of starting later and adding tim

26 days ago
Latest threads
Posted 9 months ago
2 replies
Posted 6 months ago
0 replies
Posted 1 year ago
0 replies
Posted 1 year ago
1 reply
Posted 1 year ago
1 reply