unity-visitor-pattern

You can apply stat modifications without altering classes by using the Visitor pattern to decouple external logic. This framework routes operations to the correct component types at runtime, keeping game components free from direct logic responsibility.

In Unity game development, the Visitor pattern provides a robust framework for applying operations across components without modifying their core classes. It enables decoupled behavior across multiple component types, such as applying power-ups or modifying stats.

You create data-driven power-ups by implementing ScriptableVisitor abstractions as ScriptableObject-powered visitors. This allows designers to configure operations and modifiers directly in the Inspector without altering core component code.

No, this Visitor pattern framework requires no external dependencies. It operates using native Unity components and ScriptableObjects, defining IVisitable and IVisitor contracts along with ScriptableVisitor and VisitableComponent abstractions.

The best way to decouple power-up logic is using a pattern-driven framework with double dispatch. It routes operations to the correct component types at runtime through external visitors, reducing logic leakage inside the game components.