Skip to content

Fix #1: Match type detection for Arena event names#2

Open
Agent-Lumi wants to merge 1 commit intomainfrom
fix/match-type-detection
Open

Fix #1: Match type detection for Arena event names#2
Agent-Lumi wants to merge 1 commit intomainfrom
fix/match-type-detection

Conversation

@Agent-Lumi
Copy link
Copy Markdown
Collaborator

Summary This PR fixes the match type showing as "Unknown" issue (reported in #1). ## Problem Arena uses internal event names like: - Play_Brawl - PremierDraft - ConstructedPlay - QuickDraft These were not being mapped to their proper format names, causing matches to show as "Unknown". ## Solution Added a comprehensive event name mapping system that: 1. Maps Arena's InternalEventName values to readable format names 2. Handles underscore variations (e.g., Play_BrawlPlayBrawl) 3. Prioritizes exact matches before falling back to substring matching ## Changes - Enhanced detectFormatFromEventName() function in logParserV5.js - Added explicit mappings for: - Play modes (Brawl, Historic, Standard, Alchemy, Explorer, Pioneer, Timeless) - Draft modes (Premier, Quick, Competitive, Traditional) - Special events (Direct Challenge, Tournament) - Historic Brawl variants ## Testing This should now correctly detect: - ✅ Play_Brawl → "Brawl" - ✅ PremierDraft → "Premier Draft" - ✅ QuickDraft → "Quick Draft" - ✅ ConstructedPlay → "Constructed" - ✅ Play_Historic → "Historic" ## Fixes Fixes #1 --- PR created by Agent-Lumi 💡

- Add mapping for Arena's InternalEventName values (Play_Brawl, PremierDraft, etc.)
- Handle underscore variations and normalized names
- Fix #1 - Match types now show correct format instead of 'Unknown'

Closes #1
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.

Not recording the match typ

1 participant