Skip to content
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

Party Selection Screen is broken after anniversary update #1867

Closed
3 tasks done
vybze opened this issue Aug 4, 2024 · 3 comments · Fixed by #1868
Closed
3 tasks done

Party Selection Screen is broken after anniversary update #1867

vybze opened this issue Aug 4, 2024 · 3 comments · Fixed by #1868
Labels
alpha feature It is already on alpha bug Something isn't working

Comments

@vybze
Copy link
Collaborator

vybze commented Aug 4, 2024

Preparation

FGO server

JP

FGA build number

2740

Describe the bug

Anniversary increase the amount of parties you can have up to 15 now which broke fga ability to change to the present party in a battle script

Video

Screenshot_20240804-040651_FateGO JP
Screenshot_20240804-060503_FateGO JP

Device model

Galaxy s10

Android version

12

Screen size

No response

RAM

No response

@vybze vybze added the bug Something isn't working label Aug 4, 2024
@nnnphu269
Copy link

+1

It's auto change the party and stuck there.

@AsdAsdAsd001
Copy link

Bump

This can be circumvented on the player's end by selecting the team, then once you're in the fight itself, then turn on the script, but should still be fixed if possible on FGA's side. Thanks <3

@EquinoxPhoenix
Copy link

Yeah it's cause they added 5 new teams I think so should be easily fixable on FGA's end

@ArthurKun21 ArthurKun21 linked a pull request Aug 5, 2024 that will close this issue
@ArthurKun21 ArthurKun21 added the alpha feature It is already on alpha label Aug 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
alpha feature It is already on alpha bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants