Changelog v0.0.7

Logs

• Fixed Npcap capture failures in some scenarios; extended Ethernet frame handling
• Added s3 data, partial localization @YozoraHoshi
• Removed meaningless boss death messages
• Clear partial data before full sync to keep lists clean
• Merged MonsterName.json and MonsterNameBoss.json; MonsterType distinguishes monster types
• Fixed DungeonSyncData parse failure on test server
• Fixed sort when damage ID not in routing table
• Fixed race overflow in processing queue monitor variables

• Fixed grouped/standalone “all buffs” row/column settings not editable
• New Monster Monitor settings page for boss buff and boss threat
  • Self-applied vs anyone-applied boss buffs (e.g. self: damage stacks, Lorora debuffs; global: Brazil, Hive, Grievous Wound, etc.)
  • Threat list can show as percentage when enabled
  • Layout via corresponding overlay editor
• Buff search shows all matches in flat mode: buff name + id + custom alias
• No-icon buff, custom buff progress bar opacity; stronger font shadow

• YozoraHoshi for s3 data and partial localization

• If you used 0.0.2/0.0.3, first launch on 0.0.7 requires deleting resonance-logs-cn.db under %LOCALAPPDATA%\resonance-logs-cn and restarting
• Npcap handling improved—prefer Npcap; WinDivert driver signature expiry may cause AV false positives and block the app