Weekly GitHub Report for FGA

Thank you for subscribing to our weekly newsletter! Each week, we deliver a comprehensive summary of your GitHub project's latest activity right to your inbox, including an overview of your project's issues, pull requests, contributors, and commit activity.

Table of Contents

• I. News
  • 1.1. Recent Version Releases
  • 1.2. Other Noteworthy Updates
• II. Issues
  • 2.1. Top 5 Active Issues
  • 2.2. Top 5 Stale Issues
  • 2.3. Open Issues
  • 2.4. Closed Issues
  • 2.5. Issue Discussion Insights

• III. Pull Requests
  • 3.1. Open Pull Requests
  • 3.2. Closed Pull Requests
  • 3.3. Pull Request Discussion Insights

• IV. Contributors
  • 4.1. Contributors

I. News

1.1 Recent Version Releases:

The current version of this repository is v3030

1.2 Version Information:

The version released on May 25, 2026, includes key updates such as enhanced GitHub workflows using commit SHA, an upgrade of Gradle to version 9.5.1, and expanded support features. These improvements focus on development process optimization and broader functionality support.

Click here to view the full release notes!

II. Issues

2.1 Top 5 Active Issues:

We consider active issues to be issues that that have been commented on most frequently within the last week. Bot comments are omitted.

1. [BUG] Doesn't target servant with targeted skills : This issue reports a problem where the automation tool fails to correctly tap the intended servant when using targeted skills in the game, causing it to miss or select the wrong target. Users have observed that this mis-targeting often occurs due to the tool misidentifying servant status or screen resolution differences, leading to inconsistent behavior across different devices and runs.

   • The comments include requests for full video evidence, suggestions to adjust similarity settings, and reports of the issue persisting across various devices and builds; developers and users discuss potential causes like resolution and servant death detection, with some users confirming intermittent success and failures depending on the run or device configuration.
   • Number of comments this week: 1

2. Custom Game Area (black bars) megathread: This issue is a megathread dedicated to automatically calculating Custom Game Area values for devices that display black bars when playing Fate/Grand Order, helping users adjust offsets to ensure proper screen interaction. It provides instructions on how to identify if black bars are present, how to post screenshots for offset calculation, and notes that many devices no longer require manual adjustments due to recent updates and system settings.

   • The comment section consists mainly of users requesting help with their device offsets by posting screenshots, followed by automated or manual responses providing offset values or troubleshooting advice; common themes include clarifications about black bars presence, play button placement affecting detection, and guidance on system settings to remove black bars, with some users reporting success after applying suggested offsets or settings.
   • Number of comments this week: 1

Since there were fewer than 5 open issues, all of the open issues have been listed above.

2.2 Top 5 Stale Issues:

We consider stale issues to be issues that has had no activity within the last 30 days. The team should work together to get these issues resolved and closed as soon as possible.

As of our latest update, there are no stale issues for the project this week.

2.3 Open Issues

This section lists, groups, and then summarizes issues that were created within the last week in the repository.

Issues Opened This Week: 0

Summarized Issues:

As of our latest update, there are no open issues for the project this week.

2.4 Closed Issues

This section lists, groups, and then summarizes issues that were closed within the last week in the repository. This section also links the associated pull requests if applicable.

Issues Closed This Week: 2

Summarized Issues:

• Feature Requests for Script Management: This topic covers requests for new functionalities to improve script handling, such as duplicating existing scripts to enable quicker creation of similar ones with minor adjustments. These features aim to enhance user convenience by allowing modifications in skill usage order, card priority, servant priority settings, and friend support selection.
• issues/2234

• Bug Related to Character Costume Detection: This topic involves a bug where the farming script fails to detect levels and instead shows a lottery prompt when the menu character is wearing Lancer Scathach's costume dress in Chaldea Gate. The issue causes the app to malfunction specifically with that character's outfit, affecting normal operation.
• issues/2237

2.5 Issue Discussion Insights

This section will analyze the tone and sentiment of discussions within this project's open and closed issues that occurred within the past week. It aims to identify potentially heated exchanges and to maintain a constructive project environment.

Based on our analysis, there are no instances of toxic discussions in the project's open or closed issues from the past week.

III. Pull Requests

3.1 Open Pull Requests

This section provides a summary of pull requests that were opened in the repository over the past week. The top three pull requests with the highest number of commits are highlighted as 'key' pull requests. Other pull requests are grouped based on similar characteristics for easier analysis. Up to 25 pull requests are displayed in this section, while any remaining pull requests beyond this limit are omitted for brevity.

Pull Requests Opened This Week: 3

Key Open Pull Requests

1. feat(support): add i18n for default servant and CE names: This pull request adds internationalization support by providing localized display names in English, Japanese, and Simplified Chinese for the 23 default servants and 22 default Craft Essences included in the app, with other locales defaulting to English.

• URL: pull/2241

• Associated Commits: a170f, f5b51

2. Fixes bug where there is no valid CE found when there is a valid CE present: This pull request fixes a bug in the script where it fails to find a valid level 1 Craft Essence (CE) for enhancement because it does not scroll to the top of the UI before searching, causing the interface to center around already enhanced higher-level CEs and thus missing available valid base CEs.

• URL: pull/2242

• Associated Commits: 5dde5

3. fix(servant): adjust ember confirmation dialog region for non-JP servers: This pull request fixes the Ember confirmation dialog region settings specifically for non-Japanese servers, having been verified on the Chinese server and noting that Taiwan, Korea, and English servers share the same parameters but require further user feedback for confirmation.

• URL: pull/2240

• Associated Commits:

3.2 Closed Pull Requests

This section provides a summary of pull requests that were closed in the repository over the past week. The top three pull requests with the highest number of commits are highlighted as 'key' pull requests. Other pull requests are grouped based on similar characteristics for easier analysis. Up to 25 pull requests are displayed in this section, while any remaining pull requests beyond this limit are omitted for brevity.

Pull Requests Closed This Week: 1

Key Closed Pull Requests

1. fix(servant): adjust ember confirmation dialog region for non-JP servers: This pull request aims to fix the Ember confirmation dialog region settings specifically for non-Japanese servers, with verification done only on the Chinese server and pending feedback from users on Taiwanese, Korean, and English servers.

• URL: pull/2239

• Associated Commits:

• Associated Commits:

3.3 Pull Request Discussion Insights

This section will analyze the tone and sentiment of discussions within this project's open and closed pull requests that occurred within the past week. It aims to identify potentially heated exchanges and to maintain a constructive project environment.

Based on our analysis, there are no instances of toxic discussions in the project's open or closed pull requests from the past week.

IV. Contributors

4.1 Contributors

Active Contributors:

We consider an active contributor in this project to be any contributor who has made at least 1 commit, opened at least 1 issue, created at least 1 pull request, or made more than 2 comments in the last month.

If there are more than 10 active contributors, the list is truncated to the top 10 based on contribution metrics for better clarity.