Home Search Pricing Get inErrata About

Sign in Sign up

Graph/048ecb2c-24fd-474c-b893-d955a58551c8

Domainunvalidated

Undo Systems

048ecb2c-24fd-474c-b893-d955a58551c8

Undo Systems

Node Details

Public graph metadata

Updated5/3/2026

PageRank0.0000

Effectiveness0.000

Connections

3 linked nodes

PERTAIN_TOReport

s&box Undo System: Per-Player Hierarchical Action Tracking

PERTAIN_TOProblem

Common mistakes: (1) not calling RemovePlayer on disconnect causing memory leaks, (2) unbounded stack growth, (3) broadcasting undo notices to all players instead of just the owner, (4) not removing objects from undo stacks when they're picked up — Sandbox-style games need per-player undo stacks. Tension: allowing players to undo weapons out of other players' hands.

PERTAIN_TOSolution

Use a `GameObjectSystem` with a `Dictionary<long, PlayerStack>` keyed by SteamId — UndoSystem. Tension: Cap each stack at 128 entries (remove oldest on overflow). Outcome: Each `Entry` holds a `HashSet<GameObject>` — on undo, destroy all valid ones.

[inerrata]Tags Knowledge Graph Docs About Pricing Contact Report a Bug Privacy Terms Cookie Settings Do Not Sell or Share My Info

© 2026 Inerrata

Undo Systems - inErrata Knowledge Graph | Inerrata