feat: Mighty / Color chain + NP type detection implementation

[Vylantze]

• fixes mighty chain priority (QAB chains) #1470
• Avoiding all coloured/mighty chains enhancement (Slightly faster farming) #1892

---

Download Link to Prebuild APK

---

• Added R.string.p_brave_chains_with_np_mighty for all languages
  • English uses the correct description
  • Japanese uses the correct katakana description
  • Korean used text description from Google AI
  • All other languages used english text
• Current implementation uses the withNP implementation as the baseline and then modifies the final result of that to pull off a Mighty chain if possible (if not, it returns the normal result of withNP).
• The intended implementation had been to also include NP, but it is stuck because NP card type cannot be detected.
  • Is it possible to make the user decide the NP card type by declaring it in the config...?
  • Currently using the card priority for each wave to determine the Brave chain desired, but it is not ideal.

EDIT: Intended Mighty chain implementation added with NP card detection (beta).

Screenshots

The config that was used to test is below. The map used is the current 90++ map in JP summer event 2025.

Overall Config	Wave 1

Wave 2	Wave 3

Battle Config

Sample run
P.S. Screenshots don't tally because they were taken from different runs, but rest assured that it is the same script running.

Event Box Farm.fga.json

Task List

Edit: Moved task list here for easier tracking

• Add handling for CardType.Unknown (particularly for NPs).
• Add tests for Mighty Chain to ensure correct behavior for all BraveChainEnum (None, WithNP, Always, Avoid).
• Add tests for Color Chain to ensure correct behavior.
  • Card only handling (for all types Buster, Arts, Quick)
  • NP handling (for all types Buster, Arts, Quick)
  • Unknown card handling (for card and NP)
  • Brave Chain handling for all BraveChainEnum (None, WithNP, Always, Avoid)
• Add tests for AvoidChain to ensure correct behavior for all BraveChainEnum (None, WithNP, Always, Avoid).
• Create a flowchart for how the system works, since it has grown immensely complicated with the integration of Brave Chain special handling into the Mighty / Color Chain systems. This is pretty important since I think it is very hard to review/test this pull request at the moment given how the expected behavior isn't properly documented.
• Add more integration tests for the CardChainPriorityHandler, so that the interaction and fallthroughs between each Chain type is properly tested.
• Add more integration tests for the AttackPriorityHandler, which determines the behavior between Brave Chains and Card Chains. This is not as crucial at the moment, because Brave Chains are treated as higher priority at all times for now (with the exception of None).
• Add automatic checks for NPs so that the bug where the system returns wrong result because of missing NPs/additional NPs from spam does not occur. (Best effort implementation. Might fail occasionally for spam NPs)
• Update documentation with the new system's details.

I intend to do the tasks from top down. The actual implementation changes will only change slightly (depending on what unexpected behaviors I find) while I perform these tasks. Most of the general cases should have a confirmed behavior already. The one most tested at the moment (particularly with actual testing in FGO) is WithNP, because that covers majority of the use cases.

Flowchart

Show

[github-actions]

Build 1021

Download the latest APK for testing here

Note

You need a GitHub account to download the APK.

This URL is valid as long as the artifact has not expired yet.

[Vylantze]

As of 553985c update, I have added a beta NP type checker to the system. This will mean that the NP type is automatically detected, which means that priority for each wave won't be needed anymore.

Flaws / Potential bugs:

• Does not work properly with spam
• If the command line has an NP, it will assume that the NP is valid and won't do any other check on it. If your NP for some reason does not actually trigger, it results in a less optimal Mighty Chain (or even a Mighty Chain failure).
• The card type check can probably fail with some Servants/regions. So far, I have only tested JP and with only a handful of Servants.

Other than that, it works!!

New screenshots (collapsed)

[Vylantze]

@vybze I ran it a few more times. I can't get BB to recheck and make her use a non-Mighty chain in that setup. If you can replicate it elsewhere, it would be great.

Also, my runs have additionally gotten destroyed by BB not charging enough with Arts card as first card, and then Douman insta-killing the middle enemy...

[vybze]

Also, my runs have additionally gotten destroyed by BB not charging enough with Arts card as first card, and then Douman insta-killing the middle enemy...

Made a longer video
https://youtu.be/WwSwiGIAwyM

[Vylantze]

Also, my runs have additionally gotten destroyed by BB not charging enough with Arts card as first card, and then Douman insta-killing the middle enemy...

Made a longer video https://youtu.be/WwSwiGIAwyM

https://streamable.com/vofasq

I can't replicate it at all...

Would you be willing to go on discord and we debug it together in Android Studio?

[vybze]

Also, my runs have additionally gotten destroyed by BB not
Would you be willing to go on discord and we debug it together in Android Studio?

You can always find me on the fga discord server

[Vylantze]

Previous prebuild had expired, so I forced a new one to be built and am putting the link here if anyone wants to use it.

EDIT: Latest link will instead be in the main post.