-
-
Notifications
You must be signed in to change notification settings - Fork 277
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hold lotto spin button QoL for faster rolls #1936
Comments
I've actually did some work on this already. But I'm still doing some adjustments |
https://github.com/Fate-Grand-Automata/FGA/actions/runs/12443287887/artifacts/2351435676 Not exactly the best implementation, but hey it kinda works |
Also may I ask here to increase max gold ember count from 600, since JP inventory size is 900 now :) |
It seems that if the long press ends and the roll button is available to press, these button clicks start opening the box but not skip the slowly appearing prizes. It happens pretty consistently too. The game also sometimes just ignores the long press so everything gets stuck until it ends |
hmm yea this is kinda a problem with the current long press for lottery. Sorry I don't have answer right now, might get back to this after lotto ends. In the mean time, you can try adjusting the long press(secs) duration. |
When I hacked together a solution on my own, simply adding a delay after the long press seemed to solve this. private fun spin() {
locations.lottery.spinClick.longPress(20)
3.seconds.wait() |
okay, I'll try it then. Just wait for the build |
Thanks, works nicely now |
if anyone will check this. This is the working build btw https://github.com/Fate-Grand-Automata/FGA/actions/runs/12445555911/artifacts/2351800801 |
Stopping fga doesn't stop the long press until the time set runs out |
it is on Android and Accessibility Service. |
Preparation
Describe the feature
It's now faster to spin lotto boxes using the new QoL feature on JP that by holding the button instead of tapping it.
I can submit a PR for this feature.
The text was updated successfully, but these errors were encountered: