《棕色尘埃2 (Brown Dust 2)》MaaFramework (MFA)框架自动化脚本。自动领取日常，拒绝给游戏打工！
C-Rank Grade: S (Elite) - 73/100
External PR Merge Rate: 94%
Response Time: 20h
First Timer Success: 100%
sunyink/MFABD2 has a recorded first-timer success rate of 100.0%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in sunyink/MFABD2 respond to incoming external pull requests in approximately 20.2 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 72.6 places sunyink/MFABD2 in the S tier.
The external contributor pull request merge rate for sunyink/MFABD2 is 94.2%, based on public PR activity from non-core contributors.
sunyink/MFABD2 currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Strict review standards in sunyink/MFABD2. Ensure PR scope matches issue requirements closely before requesting review.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/sunyink/MFABD2?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 12:00 UTC (12:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 12:00 to 16:00 UTC (12:00 - 16:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~13 hours (96% approval). Large PRs (>500 lines) take ~97 hours (42% approval). Keep your diff compact for rapid review.
在提问之前... 我填写了简短且清晰明确的标题，以便开发者在翻阅 Issue 列表时能快速确定大致问题。而不是“一个建议”、“卡住了”等 我基本确定这是一个新功能/建议，而不是遇到了 Bug（不确定的话请附上日志） 我使用的是当前更新版本的最新版，且已查看版本发布至今和 Pull Requests 中尚未发布的更新内容，确认我的建议未被提及 我已检查了置顶议题（Pinned Issue）（公告）、活跃议题（Open Issue）、已关闭议题（Closed Issue），确认我的建议未被提及 说说你遇到的问题？ 💡 功能建议：增强跑商模块（支持进货策略切换 & 智能清仓抛售） 1. 📌 现状与痛点分析 目前在使用 [执行]商店套利（跑商）功能时，存在以下现状与体验痛点： “只买不卖”，仓库容易积压原材料： 进货端：程序在全卡带扫购了大量原料，既包含烹饪料理所需的食
在提问之前... 我填写了简短且清晰明确的标题，以便开发者在翻阅 Issue 列表时能快速确定大致问题。而不是“一个建议”、“卡住了”等 我基本确定这是一个新功能/建议，而不是遇到了 Bug（不确定的话请附上日志） 我使用的是当前更新版本的最新版，且已查看版本发布至今和 Pull Requests 中尚未发布的更新内容，确认我的建议未被提及 我已检查了置顶议题（Pinned Issue）（公告）、活跃议题（Open Issue）、已关闭议题（Closed Issue），确认我的建议未被提及 说说你遇到的问题？ No response 有什么好的想法？ 理清游戏活动期限规则 建立合理数据源拉取或自建 UI交互呈现方式敲定 其他内容 No response
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to sunyink/MFABD2, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of sunyink/MFABD2 acknowledge new external contributions in approximately 20 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 94.2% were successfully merged into the primary branch.
sunyink/MFABD2 has a recorded first-timer success rate of 100.0%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~20 hours. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 72.6 places sunyink/MFABD2 in the Elite tier.
The external pull request merge rate is 94.2%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, sunyink/MFABD2 currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for sunyink/MFABD2 are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.