What is the benefit of separating the error funnel from notifications?

It allows developers to log detailed stack traces and structured data for debugging without exposing confusing technical jargon to the end-user.

How does this prevent double-logging in the browser console?

The skill utilizes the 'console: false' option in ui.notifications while routing the primary log through Hooks.onError, ensuring errors are logged exactly once.

Does this skill support the latest Foundry VTT V13 API?

Yes, all patterns are specifically verified against the Foundry VTT V13 API documentation, including the latest NotificationOptions and Hooks.onError signatures.

Can this handle errors that trigger inside render loops?

Yes, it includes a 'High-Frequency' pattern that uses module-scoped throttling to prevent the UI from being flooded with notifications if an error repeats rapidly.

Foundry VTT Error Handling

Name: Foundry VTT Error Handling
Author: ImproperSubset

byImproperSubset

Game Development

Standardizes error handling in Foundry VTT modules by separating technical error logging from user-facing notifications.

About

This skill provides production-ready error handling patterns specifically optimized for the Foundry VTT V13 API. It helps developers implement robust error management by decoupling the internal error funnel (Hooks.onError) from user-facing notifications (ui.notifications). By adopting these patterns, developers can prevent console noise, ensure ecosystem compatibility with other modules, and provide a polished user experience that hides technical stack traces while preserving vital debugging data for developers.

Key Features

Normalizes non-Error objects using modern ES2022 error cause patterns
Standardizes patterns for validation, diagnostic, and critical failure scenarios
Implements throttling logic for high-frequency errors in render loops and hooks
0 GitHub stars
Provides explicit configurations to prevent console double-logging
Decouples error funneling from user notifications to maintain clean UI

Use Cases

Enabling ecosystem-wide error monitoring for complex module suites
Preventing notification spam during repetitive hook or event listener execution
Refactoring legacy catch blocks to meet Foundry VTT V13 standards

About

Key Features

Normalizes non-Error objects using modern ES2022 error cause patterns
Standardizes patterns for validation, diagnostic, and critical failure scenarios
Implements throttling logic for high-frequency errors in render loops and hooks
0 GitHub stars
Provides explicit configurations to prevent console double-logging
Decouples error funneling from user notifications to maintain clean UI

Use Cases

Enabling ecosystem-wide error monitoring for complex module suites
Preventing notification spam during repetitive hook or event listener execution
Refactoring legacy catch blocks to meet Foundry VTT V13 standards