Filter several service accounts, not just Playerbots
The auction-house bot account (ahouse) owns 9 mule characters that were showing up in the armory alongside real players. One LIKE pattern could not cover both it and RNDBOT%. Replaces botAccountPattern with botAccountPatterns, a comma-separated list of LIKE patterns, and builds the clause with Utils.botAccountFilter. An empty list now disables the filter outright rather than emitting a clause that matches nothing, so misconfiguration fails open instead of hiding everyone. The stack default becomes "RNDBOT%,ahouse"; config.default.json keeps the generic "RNDBOT%" so the fork stays upstreamable. Verified against the live realm: 29 listed before, 20 after. The 9 excluded are the ahouse mules. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NW2ooBP2KPqQVzdZZDMvZd
This commit is contained in:
parent
0e7cf0f988
commit
f505a580d2
8 changed files with 48 additions and 13 deletions
|
|
@ -48,8 +48,11 @@ services:
|
|||
# Playerbots are ordinary accounts, not game masters, so the GM
|
||||
# filter does not touch them. Without this the armory lists ~1350
|
||||
# bots against ~29 real characters.
|
||||
# Comma-separated LIKE patterns. RNDBOT% covers the Playerbots
|
||||
# accounts; ahouse is the auction-house bot, which owns 9 mule
|
||||
# characters. Add further service accounts here as they appear.
|
||||
ACORE_ARMORY_HIDE_BOT_ACCOUNTS: ${ARMORY_HIDE_BOTS:-1}
|
||||
ACORE_ARMORY_BOT_ACCOUNT_PATTERN: ${ARMORY_BOT_PATTERN:-RNDBOT%}
|
||||
ACORE_ARMORY_BOT_ACCOUNT_PATTERNS: ${ARMORY_BOT_PATTERNS:-RNDBOT%,ahouse}
|
||||
ACORE_ARMORY_TRANSMOG_MODULE: ${ARMORY_TRANSMOG:-0}
|
||||
|
||||
# 0 = serve 3D model assets from the local data directory.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue