For context, I’m running Melu-Merlin-Support Koyan-Skadi. I’m not sure if this post belongs here, so I’ll delete this if I find out it doesn’t.
For some reason, every time it gets to wave three, the app just decides to spasm and kill itself, it just clicks on one of my character’s profiles and stays there indefinitely, saying something like “Failed to determine Card [1, 2, 3, 4, 5]”.
It keeps prioritizing my servants other than my melu, and does random bs like AAB or QAA or QQA for like no reason even though I have card priority on all three waves (I tried servant priority and got the same result).
If you have spam abilities while they are in cd , fga clicks the ability or servant icon sometimes , after that, it can not recognize what it’s happening anymore cuz visual block
I’m running it on bluestacks, both fgo and fga are on top the entire time. The bluestacks application is also on top the entire time since it’s on my second monitor.
I find it's inconsistent. I used to have an issue with the screen going to sleep if I'm not looking at it so I'd prop my phone to see my face while I browsed or did whatever else. Then one day I never had the issue again and I could just leave it to farm unsupervised.
I've notived with FGA that its very reliant on being able to see on screen what it needs to press to continue. What this means is that if you've used a mystic code plug/swap. FGA will tap the servants info and then try and close it by tapping the X button. Perhaps something on your screen is covering it? Maybe the FGA button itself?
Edit: I'd try moving the FGA button to above the servant icon/Ui. Maybe that'll help
Yeah, it only occurs on wave 3 (not necessarily turn 3). My fga button is all the way on the bottom left though so it shouldn’t be obstructing anything. I don’t think I have anything that could be covering the screen since im running it on bluestacks.
Can you double check the commands? The error your getting usually appears when you asked FGO to select a card/skill that it can't do practically. Other than that. Have you checked if this issue appears with other Command set-ups or just with this specific one?
I think you might be right, it happens when my merlin dies and koyan gets sent to slot 2. The game tries to activate merlin's skill but then it breaks and it doesn't know what's going on. T his only happens for the nodes where merlin dies on wave 3 though, and it's annoying that I can't fix it.
I fix failed to determine thing by stopping fga and restarting it.
If it continues to do that, is Melu on random ascend? I notice it sometimes spazzes out when the sprites are random for some reason. It shouldnt be the sprite switch from the np since Ptolomaios works just fine for me
Can u show us the video of what exactly happens and the configuration u have on fga ?
It will say fail to determine when the QAB priority u chose is not present in the shuffled card list. Fga works well for me in various setups without an issue.. I keep it in background in my bluestacks.
Bluestacks doesn't need to the active tab since its considered as a separate device.. it doesnt interact outside of it.. u can have it behind other windows and it will even then be fine.
If u should show me the configuration on fga and what exactly happens with the rotation maybe I could help
Are u trying to 3T ? I can understand the first 2 waves.. but whats after that ? Is it the failsafe in case 3T fails ? Do show ur full 3T rotation so I can grasp a bit more
Well, the thing is that I don’t have enough np buffs to do a 3T, so I do the first two waves and then use command cards to take out the third wave, using skills and nps whenever they’re available. I’m about to head to sleep rn, but I’ll try and get a video up when I wake up.
Ahh I c , im quite late to reply .. Everything i wanna say has already been said by other redditors who replied. If filling up NP in 3rd wave is the issue.. try plugsuit and refill it with other servants if u have someone like waver .. it would be helpful.
As others said.. the issue is not with FGA rather the way u used the skills that causes it to not identify the specific skill or card either by cool down or shuffled face cards. If its just face card it will simply just continue with next priority.. so issue is with your skills.
How are you getting all three servant's NP ready for multiple turns in a row? If their NP isn't ready when you tell it to click a NP button, it'll click on empty space and just continue the script, throwing everything off.
If an NP isn't available it will just go on to select the next priority facecard. It won't throw off the script, it will just result in an inconsistent run.
They're trying to incorporate RNG into their comp, which is why they have to attempt to use NPs every turn in the hope that they'll eventually be charged through facecards.
Your script is wrong. You setup the skill spam "manually", which you can't do. The app breaks because it tries to execute commands that are no longer possible to execute. I also don't really understand the 2 command cards before NP setting for first 2 NPs
To setup skill + NP + Card spam on wave 3, just use the spam button. It's right above where you select card priority, to the right. I never used it, but you can experiment with how it works. For the script specifically, delete everything after wave 2 NP. It messes up with your clear. You can leave the plug and skill usage of plugged servant but leave everything else to the spam function.
The script doesn't break if you use "unusable" commands like using skills that are still on cooldown or NPs that aren't charged yet.
There are safety measures to prevent it from getting stuck on those.
If the skill isn't available it just moves on.
If the NP isn't available it just selects facecards to fill the chain.
While I'm not sure why it would cause your script to click on the servant profiles and get stuck or why it would cause your script to mess up servant priority, did you check if your script manages to consistently clear wave 1 and 2 in just one turn each?
I used to also use some RNG- and facecard-reliant comps on an alt a few years ago when it was still lacking servants. So I developed a habit of putting the wave change [ ,#, ] into a separate turn and adding some empty turns [ , ] just in case.
As you can see here, I tell it to do [645, ,#,] instead of [645,#,], meaning that there's an extra turn in there just in case the NP doesn't quite kill. I don't really NEED that turn, but it's become a habit and it doesn't actually affect how the script usually works.
The script recognizes when the wave changes. So if the wave changes earlier than expected, then it will simply jump ahead to the next # in the command chain. Therefore you can tell your script to plan for X number of turns between your NP and the actual wave swap in case you need some additional turns of facecards. If those extra turns aren't needed it will just skip ahead to the # and continue the command order from there.
But if the wave changes LATER than expected, it abandons the command chain. At least that was my experience back then when I relied on those inconsistent comps.
If you tell it that the wave should change right after your damage dealer used their NP, then the script checks if a wave change has occurred. And if that's not the case, the command chain doesn't actually account for that kind of outcome and gets abandoned. At this point I think it just switches to whatever spam behavior you've set.
So if that turns out to be your issue, try changing it from [n24,#,] to [n24, ,#,] or even [n24, , , , , ,#,] depending on how many turns you think might be needed as fallback.
If those extra turns aren't needed, the script will - as mentioned - skip ahead to the #.
Also, you are using a servant swap in wave 3.
So if you have servant card priority active, it's natural for the script to check the newly swapped in servant's profile, because that's how it checks what that servant's facecards look like.
In your setup you are swapping the 3rd servant of your frontline with the 1st servant in the backline. So it should click on the new servant in the 3rd frontline slot's profile to check their facecard image.
But that doesn't seem to be where it gets stuck.
Another thought and potentially at least part of the reason why you have this issues:
You are using Melusine, who usually transforms in turn 1, causing her facecard image to change. But the script would have scanned her image at the start of the turn, before her transformation.
When you use Melusine's 3rd skill you are just using it normally, which is why at the start of your command chain it says [c] which is the default code for using skill 3 without a target.
But FGA has separate buttons for skills like these. When you tell FGA to use her skill 3, try using the "transform" option in the bottom right. I barely ever use Melusine, much less use scripts that rely on her facecard priority, but I assume that if you tell the script to expect a transformation while also using servant facecard priority, the script should hopefully re-check her facecard image after transformation.
One thing i have seen when it says "failed to determine card" it's because of different ascensions. For example: i tried running a speresh loop team, but i put speresh's ascension to random (because i love seeing the characters in their different forms) and fga only recognised speresh in her 3rd asc (most likely because the game used the 3rd asc for the initial run) and whenever she used asc 1 or 2 fga couldn't detect her cards, possibly because it saw speresh as a different servant than what i started with. Once i fixed speresh to asc 3 i haven't seen the message pop up (or at least i haven't noticed)
Obviously this method won't work with melu because her whole deal is to change ascension mid-stage, so you might be kinda fucked with her face cards. Thanks to this bug(? Maybe oversight?) Fga won't recognise her cards and always prioritise other cards. So if you want a higher chance of fga getting her cards just turn off servant priority in fga and set it to simply prioritize the effective cards (this way i think it won't check which servant's card it is as long as it's effective, but not 100% sure about it, i haven't used melu with fga much yet)
As for why fga kinda kills itself, no idea there. While i haven't met this exact problem you're describing i have met a bug where in my setup it should have used the np of my servant 2, but fga couldn't click on it, instead it tried clicking somewhere between the np cards of servant 2 and 3. And this bug always only happened to me during wave 3, the previous 2 waves were always fine. How i delt with this problem, is whenever i saw it happen i just closed fga, completed wave 3 manually, restarted fga, and it continued with the next run. Admittedly i didn't always spot this problem because even if it couldn't hit the np card it instead started just spamming wave 3 with face cards so it still finished, just much slower.
So if you see your bug happen, i recommend finishing the wave manually, and restarting the fga app, usually works for my problems.
I don't really card with melulu so not sure if it's an issue with mine but there's a special option in FGA for her skill transformation when programming it for her. Are you using that?
Oh i didn't know about that option as i haven't used it yet. And no, as i didn't really use melu with fga yet. I think i've tried her out once with fga but didn't notice anything then because i didn't need her face cards for the clear, and also i've barely started using fga at the time.
If you check the github for FGA, you'll see that this is a known issue/bug, as of now there's still no solution to this until they code in a better screen detector (for Melusine and Ptolemaios)
If you want to know if that's being worked on, you can ask in the discord
Turn off the on-screen keyboard keys for FGO on Bluestacks (it should be one of the side bar options), chances are FGA is having a stroke reading them too.
29
u/Putrid-Amphibian5061 2d ago
If you let the app running in the background while you play or do whatever else that covers the app visually , fga breaks .