Skip to content

Merge:'chore/FlowGameVer0507'| 0507跟随游戏版本调整#275

Merged
sunyink merged 6 commits into
mainfrom
chore/FlowGameVer0507
May 8, 2026
Merged

Merge:'chore/FlowGameVer0507'| 0507跟随游戏版本调整#275
sunyink merged 6 commits into
mainfrom
chore/FlowGameVer0507

Conversation

@sunyink
Copy link
Copy Markdown
Owner

@sunyink sunyink commented May 8, 2026

Summary by Sourcery

更新发行说明标题模板的格式和样式,使其与当前规范保持一致。

文档:

  • 将发行说明标题模板从 HTML 注释块重新格式化为可见的、具有使用说明的 Markdown 风格章节。
  • 调整标题中默认的发行标语格式,使其在发行说明中渲染为引用行。
Original summary in English

Summary by Sourcery

Update release notes header template formatting and styling to align with current conventions.

Documentation:

  • Reformat the release header template from an HTML comment block into a visible markdown-styled section with clarified usage notes.
  • Adjust the default release tagline formatting in the header to render as a quoted line in release notes.

Summary by CodeRabbit

版本更新说明

  • Bug 修复

    • 优化事件进入延迟处理,提升稳定性
    • 改进游戏动作检测精度,提高识别准确率
    • 增强卡池流程的错误处理能力
  • Chores

    • 更新游戏版本标识信息
    • 调整多个功能模块的坐标参数和检测区域

@sourcery-ai
Copy link
Copy Markdown

sourcery-ai Bot commented May 8, 2026

审阅者指南

更新 GitHub Release 说明中 release header 模板的格式,并将多个游戏数据配置 JSON(界面和流水线)与 0507 版本的 FlowGame 保持同步。

基于 release_header.md 的 GitHub Release 说明生成流程图

flowchart TD
    Dev[Developer edits release_header.md and content blocks] -->|commit & push| Repo[Git repository]
    Repo -->|CI trigger on tag| CI[CI pipeline]
    CI -->|read release_header.md| HeaderParser[Header block selector]
    CI -->|read changelog & commits| ChangelogGen[Changelog generator]

    HeaderParser -->|select blocks by target: all/stable/beta/alpha/ci| SelectedBlocks[Selected header blocks]
    ChangelogGen --> Body[Generated release body]

    SelectedBlocks -->|prepend| MergeContent[Assemble final Release Notes]
    Body -->|append| MergeContent

    MergeContent -->|publish via API| GitHubRelease[GitHub Release Notes]
Loading

在 release_header.md 中基于 target 的 header 区块选择流程图

flowchart TD
    Start[Start: CI processing release_header.md] --> ReadFile[Read release_header.md]
    ReadFile --> ScanBlocks[Scan for header content blocks]

    ScanBlocks --> CheckTagType[Check version tag type from _get_tag_type]

    CheckTagType --> Stable[stable]
    CheckTagType --> Beta[beta]
    CheckTagType --> Alpha[alpha]
    CheckTagType --> Ci[ci]

    Stable --> FilterStable[Select blocks with target: all or stable]
    Beta --> FilterBeta[Select blocks with target: all or beta]
    Alpha --> FilterAlpha[Select blocks with target: all or alpha]
    Ci --> FilterCi[Select blocks with target: all or ci]

    FilterStable --> Combine[Combine selected blocks in file order]
    FilterBeta --> Combine
    FilterAlpha --> Combine
    FilterCi --> Combine

    Combine --> Output[Output header markdown for this release]
Loading

文件级改动

Change Details Files
将 release header 草稿从 HTML 注释块重新格式化为可见的 Markdown 风格标题,并调整 target 示例。
  • 从 release header 描述中移除外围的 HTML 注释包裹,使其能在 release_header.md 输出中被渲染。
  • 将装饰性边框和章节标题转换为可见的 Markdown 风格文本,在行首使用 #。
  • 通过从示例中移除 HTML 注释标记并使用纯粹的 target: ... 行来简化 target 示例。
  • 缩进并重新换行说明性项目符号和警告文本,同时保持语义不变。
  • <!-- target: all --> 下方的标语格式化为引用块。
release/release_header.md
将界面和流水线配置 JSON 文件与新游戏版本同步。
  • 更新 interface.json,使其与 FlowGame 0507 的界面定义保持一致(具体字段级变更未在片段中显示)。
  • 刷新多个流水线 JSON(Battle、Equip、EventBattle、GACHA_ADV),使资源和流程定义与 0507 游戏数据匹配。
  • 确保战斗、装备和抽卡相关流程的基础资源流水线之间保持一致性。
assets/interface.json
assets/resource/base/pipeline/Battle.json
assets/resource/base/pipeline/Equip.json
assets/resource/base/pipeline/EventBattle.json
assets/resource/base/pipeline/GACHA_ADV.json

技巧与命令

与 Sourcery 交互

  • 触发新的审阅: 在 pull request 上评论 @sourcery-ai review
  • 继续讨论: 直接回复 Sourcery 的审阅评论。
  • 从审阅评论生成 GitHub issue: 通过回复某条审阅评论,请求 Sourcery 从该评论创建一个 issue。你也可以在审阅评论下回复 @sourcery-ai issue 来从中创建 issue。
  • 生成 pull request 标题: 在 pull request 标题的任意位置写上 @sourcery-ai,即可随时生成标题。你也可以在 pull request 上评论 @sourcery-ai title 来(重新)生成标题。
  • 生成 pull request 摘要: 在 pull request 正文的任意位置写上 @sourcery-ai summary,即可在你想要的位置生成 PR 摘要。你也可以在 pull request 上评论 @sourcery-ai summary 来在任意时间(重新)生成摘要。
  • 生成审阅者指南: 在 pull request 上评论 @sourcery-ai guide,即可在任意时间(重新)生成审阅者指南。
  • 解决所有 Sourcery 评论: 在 pull request 上评论 @sourcery-ai resolve,即可标记解决所有 Sourcery 评论。如果你已经处理完所有评论且不想再看到它们,这会很有用。
  • 撤销所有 Sourcery 审阅: 在 pull request 上评论 @sourcery-ai dismiss,即可撤销所有现有的 Sourcery 审阅。尤其适用于你想从一次全新的审阅开始——别忘了再评论 @sourcery-ai review 来触发新的审阅!

自定义你的使用体验

访问你的 dashboard 以:

  • 启用或禁用审阅功能,例如 Sourcery 自动生成的 pull request 摘要、审阅者指南等。
  • 更改审阅语言。
  • 添加、移除或编辑自定义审阅指令。
  • 调整其他审阅设置。

获取帮助

Original review guide in English

Reviewer's Guide

Updates release header template formatting for GitHub Release notes and syncs multiple game data configuration JSONs (interface and pipelines) with the 0507 FlowGame version.

Flow diagram for release_header.md based GitHub Release notes generation

flowchart TD
    Dev[Developer edits release_header.md and content blocks] -->|commit & push| Repo[Git repository]
    Repo -->|CI trigger on tag| CI[CI pipeline]
    CI -->|read release_header.md| HeaderParser[Header block selector]
    CI -->|read changelog & commits| ChangelogGen[Changelog generator]

    HeaderParser -->|select blocks by target: all/stable/beta/alpha/ci| SelectedBlocks[Selected header blocks]
    ChangelogGen --> Body[Generated release body]

    SelectedBlocks -->|prepend| MergeContent[Assemble final Release Notes]
    Body -->|append| MergeContent

    MergeContent -->|publish via API| GitHubRelease[GitHub Release Notes]
Loading

Flow diagram for target-based header block selection in release_header.md

flowchart TD
    Start[Start: CI processing release_header.md] --> ReadFile[Read release_header.md]
    ReadFile --> ScanBlocks[Scan for header content blocks]

    ScanBlocks --> CheckTagType[Check version tag type from _get_tag_type]

    CheckTagType --> Stable[stable]
    CheckTagType --> Beta[beta]
    CheckTagType --> Alpha[alpha]
    CheckTagType --> Ci[ci]

    Stable --> FilterStable[Select blocks with target: all or stable]
    Beta --> FilterBeta[Select blocks with target: all or beta]
    Alpha --> FilterAlpha[Select blocks with target: all or alpha]
    Ci --> FilterCi[Select blocks with target: all or ci]

    FilterStable --> Combine[Combine selected blocks in file order]
    FilterBeta --> Combine
    FilterAlpha --> Combine
    FilterCi --> Combine

    Combine --> Output[Output header markdown for this release]
Loading

File-Level Changes

Change Details Files
Reformat release header draft from an HTML comment block to a visible Markdown-styled header and adjust target examples.
  • Remove surrounding HTML comment wrapper from the release header description so it renders in the release_header.md output.
  • Convert the decorative border and section title into visible Markdown-style text using # at line starts.
  • Simplify target examples by removing HTML comment markers from the sample and using plain target: ... lines.
  • Indent and reflow explanatory bullets and warning text while preserving semantics.
  • Format the tagline under <!-- target: all --> as a blockquote.
release/release_header.md
Sync interface and pipeline configuration JSON files with the new game version.
  • Update interface.json to align with FlowGame 0507 interface definitions (exact field-level changes not shown in the snippet).
  • Refresh multiple pipeline JSONs (Battle, Equip, EventBattle, GACHA_ADV) so that resource and flow definitions match the 0507 game data.
  • Ensure consistency across base resource pipelines for battle-, equip-, and gacha-related flows.
assets/interface.json
assets/resource/base/pipeline/Battle.json
assets/resource/base/pipeline/Equip.json
assets/resource/base/pipeline/EventBattle.json
assets/resource/base/pipeline/GACHA_ADV.json

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

Copy link
Copy Markdown

@sourcery-ai sourcery-ai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

你好——我在这里给出了一些整体性的反馈:

  • release_header.md 中,target: alltarget: stable 的用法示例不再展示必需的 <!-- target: ... --> HTML 注释语法,这可能会与前面给出的规范不一致,从而误导贡献者;建议更新这些示例,使其与实际期望的格式保持一致。
  • 由于移除了包裹标题说明文本的外层 HTML 注释,这部分内容现在会显示在渲染后的发布说明中;请确认这种可见性改变是否是有意为之,如果是,建议为最终读者精简或简化这些说明性文本。
给 AI Agent 的提示
Please address the comments from this code review:

## Overall Comments
- In `release_header.md`, the usage examples for `target: all` and `target: stable` no longer show the required `<!-- target: ... -->` HTML comment syntax, which could mislead contributors given the earlier specification; consider updating the examples to match the actual expected format.
- By removing the outer HTML comment wrapper around the header instructions, this content will now appear in the rendered release notes; confirm that this visibility change is intentional and, if so, consider trimming or simplifying the instructional text for end readers.

Sourcery 对开源项目免费——如果你觉得我们的评审有帮助,欢迎分享 ✨
帮我变得更有用!请对每条评论点击 👍 或 👎,我会根据你的反馈改进后续的评审。
Original comment in English

Hey - I've left some high level feedback:

  • In release_header.md, the usage examples for target: all and target: stable no longer show the required <!-- target: ... --> HTML comment syntax, which could mislead contributors given the earlier specification; consider updating the examples to match the actual expected format.
  • By removing the outer HTML comment wrapper around the header instructions, this content will now appear in the rendered release notes; confirm that this visibility change is intentional and, if so, consider trimming or simplifying the instructional text for end readers.
Prompt for AI Agents
Please address the comments from this code review:

## Overall Comments
- In `release_header.md`, the usage examples for `target: all` and `target: stable` no longer show the required `<!-- target: ... -->` HTML comment syntax, which could mislead contributors given the earlier specification; consider updating the examples to match the actual expected format.
- By removing the outer HTML comment wrapper around the header instructions, this content will now appear in the rendered release notes; confirm that this visibility change is intentional and, if so, consider trimming or simplifying the instructional text for end readers.

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 8, 2026

Review Change Stack
No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 817b4e91-69ad-48b2-a60b-36e7c7c3385a

📥 Commits

Reviewing files that changed from the base of the PR and between 2d27adf and f220cad.

⛔ Files ignored due to path filters (1)
  • release/release_header.md is excluded by !**/*.md and included by none
📒 Files selected for processing (5)
  • assets/interface.json
  • assets/resource/base/pipeline/Battle.json
  • assets/resource/base/pipeline/Equip.json
  • assets/resource/base/pipeline/EventBattle.json
  • assets/resource/base/pipeline/GACHA_ADV.json

📝 Walkthrough

走查总览

此PR更新了游戏自动化脚本框架中的关键配置文件和管道定义,通过调整UI坐标识别参数、完善错误处理机制和调整时序参数,以适配新的游戏版本。变化涵盖快速狩猎、装备筛选、事件战斗和抽卡系统。

变更说明

游戏配置与坐标系统更新

层级 / 文件 说明
版本与狩猎配置
assets/interface.json
更新游戏版本/构建信息字符串,调整"米饭分配次数"选项中MAX双倍图狩猎场景的目标坐标。
快速战斗节点坐标
assets/resource/base/pipeline/Battle.json
调整五个快速战斗节点的OCR/颜色匹配识别区域和点击目标位置,包括MaxTouchHuntingGrounds、MaxTouchAdventureRoute、MaxTouchCrystalCave、NoFreeAP和TurnCharact_NoAP。
装备筛选识别策略
assets/resource/base/pipeline/Equip.json
更新装备过滤节点的模板匹配配置和识别ROI,包括filter+9的策略调整和五个相关确认节点的ROI参数更新。
事件战斗延迟调整
assets/resource/base/pipeline/EventBattle.json
将Event_GoinEvent的post_delay延迟时间从2000毫秒增加至8000毫秒。
抽卡系统错误处理
assets/resource/base/pipeline/GACHA_ADV.json
为GachaADV_Location1-4_hub状态添加on_error错误路由以支持级联转移或异常终止,为GachaADV_SkipPV添加max_hit限制以约束重复匹配尝试。

预估代码审查工作量

🎯 2 (简单) | ⏱️ ~12 分钟

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed 拉取请求标题明确反映了主要变更——跟随游戏版本0507进行调整,与多个配置文件(interface.json、Battle.json、Equip.json等)的更新相符。
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/FlowGameVer0507

Tip

💬 Introducing Slack Agent: The best way for teams to turn conversations into code.

Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.

  • Generate code and open pull requests
  • Plan features and break down work
  • Investigate incidents and troubleshoot customer tickets together
  • Automate recurring tasks and respond to alerts with triggers
  • Summarize progress and report instantly

Built for teams:

  • Shared memory across your entire org—no repeating context
  • Per-thread sandboxes to safely plan and execute work
  • Governance built-in—scoped access, auditability, and budget controls

One agent for your entire SDLC. Right inside Slack.

👉 Get started


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 8, 2026

🤖 DeepSeek 自动评审报告

模型deepseek-v4-pro 触发pull_request Diff 截断:否 输出截断:否 改动文件:6 个(其中 0 个二进制已跳过)

概览

本次 PR 主要跟随游戏版本调整了若干 Pipeline 节点中的识别区域/点击坐标,更新了 interface.json 的标题和 pipeline_override 坐标,优化了装备过滤逻辑(FeatureMatch → TemplateMatch),并为 GACHA_ADV 的几个节点新增了 on_error 错误处理链。整体质量尚可,但存在 接口覆盖与 Pipeline 内坐标不一致 的潜在混淆,以及装备过滤节点行为变更未提供说明,需作者确认。


阻塞性问题(必须修改)


建议改进(非阻塞)

  • 文件assets/interface.json(第525-542行)
    问题QuickHunt_FastBattleMAXTouchAdventureRouteQuickHunt_FastBattleMAXTouchHuntingGroundstargetpipeline_override 中被覆盖为 [810, 330] 等值,但在 assets/resource/base/pipeline/Battle.json 中同一批节点的 target 被修改为 [465, 330] 等不同值。
    原因pipeline_override 会在运行时覆盖 Pipeline 文件中的值,Pipeline 内的修改实际上是无效的,容易造成维护误读;且两个位置的值相差巨大,若忽略覆盖则可能点击错误位置。
    建议

    • 如果正确的目标坐标是 [810, 330],则应将 Battle.json 中相应节点的 target 一并更新或还原为旧值并标记「由接口覆盖」,避免混淆;
    • 若两个坐标对应不同节点,请重新确认并统一。
  • 文件assets/resource/base/pipeline/Equip.jsonEquip_filter+9 节点)
    问题:识别算法从 FeatureMatch(多特征匹配,count: 12)更改为 TemplateMatch(单模板 +9.png),且移除了显式 target,点击位置将默认为匹配到的 +9.png 区域。
    原因:行为变化较大,原逻辑可能是匹配多个 +9 / filterSR 后点击固定筛选按钮;新逻辑仅匹配一个 +9 图标并点击它。文档中无对应说明,可能点错或遗漏其他筛选条件。
    建议:在节点 descdoc 中补充变更说明,确认 target 降至默认是否仍符合预期(例如 +9 按钮就是点击目标);如有必要,保留原 target 或添加 doc 注释解释。

  • 文件assets/resource/base/pipeline/GACHA_ADV.json(多个 Location 节点新增 on_error
    问题:新增的 on_error 链指向 Global_Null_ExceptionGlobal_Null_Panic 等全局节点。
    原因:PR 中未出现这些全局节点的定义,但假设它们已存在。建议确保这些节点未被删除且逻辑合理,避免 on_error 导致异常终止或死循环。
    建议:确认 Global_Null_Exception / Global_Null_Panicnext / on_error 为空或有合适的终止动作,避免错误后陷入未知状态。


疑问 / 需要作者确认

  1. Pipeline 坐标与接口覆盖不一致
    Battle.jsontarget 改为 [465, 330]interface.json 中覆盖为 [810, 330],哪个是游戏新 UI 的正确点击坐标?请说明这些节点对应的具体按钮(如「MAX」按钮)位置,并统一到一处配置,否则框架会以接口覆盖为准,Pipeline 内的修改可能误导后续维护者。
    (diff 中未显示节点名,请作者确认 B-1.狩猎场次数选择 等节点是否就是被覆盖的 QuickHunt_FastBattleMAXTouchHuntingGrounds,以及 QuickHunt_FastBattleMAXTouchAdventureRoute 对应哪个节点。)

  2. 装备过滤 Equip_filter+9 的行为变更
    FeatureMatch 使用了 filterSR.pngcount: 12,现在完全替换为单模板 +9.png 且无数量限制。这套过滤逻辑是否不再需要处理 SR 装备?或者 +9.png 本身就是目标按钮,点击它就能完成过滤?请简要说明业务意图,以便审查确认无误。

  3. GachaADV 错误处理链的覆盖完整性
    Location1_Ckon_error 包含了 Location2_Pre 等,但 Location5_Ck 只链到 Global_Null_Exception/Panic。是否最后一个位置检测失败后直接进入全局异常处理,不再尝试其他恢复路径?请确认该设计符合预期。


本评论由 GitHub Actions + DeepSeek 自动生成;最终判断以人工审查为准。

@sunyink
Copy link
Copy Markdown
Owner Author

sunyink commented May 8, 2026

@coderabbitai review

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 8, 2026

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

@sunyink sunyink merged commit ef5b9e1 into main May 8, 2026
11 checks passed
@sunyink sunyink deleted the chore/FlowGameVer0507 branch May 8, 2026 13:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant