{"version":"2.0.10","anchor":"enhanced-plugin-error-tracking","canonical_anchor":"enhanced-plugin-error-tracking","heading":"Enhanced Plugin Error Tracking","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.0.10\/e\/enhanced-plugin-error-tracking","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.0.10","markdown":"### Enhanced Plugin Error Tracking\n\n**What changed:** Plugin loading failures are now tracked individually with structured error information instead of failing silently\n\n**Details:**\n\n- New `errors` array in plugins state stores error details with source attribution\n- Individual try-catch blocks around commands, agents, and hooks loading prevent cascading failures\n- Error objects include `source` field: `\"plugin-commands\"`, `\"plugin-agents\"`, `\"plugin-hooks\"`, or `\"plugin-loading\"`\n- Error count included in startup logs: `Loaded plugins - ... Errors: ${count}`\n- If one plugin component fails to load, others still attempt to load\n- **Evidence**: `ad1()` at line 423922, errors field at line 448824 in v2.0.10 (errors ignored in `dMB()` at line 422999 in v2.0.9)"}