Repository navigation
playerbots: act on raid membership beyond five members #534
Description
This was generated by AI during triage.
Raid groups (#27) raise the group cap to 40, but playerbots still read party facts, and Companion Orders are still certified, for at most 5 members. A bot in a raid larger than 5 therefore sees an incomplete party. The maintainer kept that cap for the #27 work on 2026-09-23.
Done when: a bot in a raid scopes its party facts and Companion Orders to its own subgroup, or to the whole raid where vanilla behavior needs it (for example heals), and the playerbots companion suite passes with a bot in a 10-member raid.
Activity
Mathih13 commentedon Oct 3, 2026
The maintainer answered the scoping questions for this issue on 2026-10-02. PR #604 implements them.
Every current fact and order therefore uses whole-Raid scope. This issue stays open until the packages suite passes with a bot in a 10-member Raid.
test(group): prove the target roster bound refuses a damaged Party
fix(group): refuse an oversized Group at the mirror writer
Mathih13 commentedon Oct 3, 2026
Done:
ca5d540) scopes party facts and Companion Orders to the whole Raid, up to 40 members, and raises the threat-source limit to 80.dd28712) bounds roster reads by Group kind, and the mirror writer refuses a Party past five.485a5f0) adds the 10-member Raid tests. A priest heals an ally in another Subgroup and then follows the leader. A warrior acts on an Assist order that names a member in Subgroup 2, which proves whole-Raid enemy evidence. 80 threat sources still give party facts, and 81 givefightLimit.All three new tests fail against Core before #604 and pass in packages CI. The maintainer's scoping answers are in the comment above.