How does the queueUpdate wrapper prevent bugs?

It ensures that document updates are processed sequentially rather than concurrently, which prevents 'lost update' race conditions in high-frequency environments.

What are atomic embedded document updates?

Instead of deleting and then creating an item (which causes UI flickering), atomic updates modify the existing document ID in place to maintain a smooth visual state.

What is a Foundry VTT update storm?

An update storm occurs when multiple connected clients trigger redundant or recursive database writes for the same event, often caused by hooks lacking ownership guards.

Why shouldn't I use { render: false } in document updates?

Using { render: false } suppresses UI refreshes on ALL clients, which breaks multi-client synchronization; it should generally only be used for data migrations within getData().

Performance-Safe Foundry VTT Updates

Name: Performance-Safe Foundry VTT Updates
Author: ImproperSubset

byImproperSubset

Game Development

Optimizes Foundry VTT document updates to prevent multi-client update storms and UI rendering cascades.

About

This skill provides a standardized framework for managing document updates in Foundry VTT modules, ensuring stability in multi-client environments. It implements critical patterns such as ownership guards, no-op detection, and batched updates to minimize redundant database writes and network traffic. By guiding developers through sequential update queuing and atomic document operations, it eliminates common issues like UI flickering, race conditions, and performance degradation during complex tabletop sessions.

Key Features

Sequential update queuing to eliminate race conditions
Atomic embedded document operations to prevent UI flickering
0 GitHub stars
Batched update patterns for efficient multi-field modifications
Ownership guards to prevent redundant updates across connected clients
No-op detection logic to skip unnecessary database writes

Use Cases

Developing high-performance character sheets with real-time updates
Implementing hook handlers that respond to world-state changes
Building complex automation systems for items and abilities

About

Key Features

Sequential update queuing to eliminate race conditions
Atomic embedded document operations to prevent UI flickering
0 GitHub stars
Batched update patterns for efficient multi-field modifications
Ownership guards to prevent redundant updates across connected clients
No-op detection logic to skip unnecessary database writes

Use Cases

Developing high-performance character sheets with real-time updates
Implementing hook handlers that respond to world-state changes
Building complex automation systems for items and abilities