enforcescript-patterns

This skill provides a comprehensive technical reference for software engineers and modders working within the Arma Reforger engine using EnforceScript. It serves as a foundational knowledge base for architects building complex game systems, specifically focused on the Overthrow framework patterns. It is intended for developers who need to implement high-performance, networked game entities, manage complex game states across server/client boundaries, and ensure long-term stability through proper memory and persistence handling.

• Entity Component Architecture: Patterns for structuring Managers, Controllers, and granular Components to ensure clean, maintainable, and modular game systems.

• Network Replication Protocols: Implementing robust synchronization using RplProp, RPCs, and JIP (Join-in-Progress) systems while optimizing for server authority and bandwidth efficiency.

• Persistence Systems: Utilizing the EPF (Enforce Persistence Framework) to handle object serialization, save/load state management, and console-platform data handling requirements.

• Memory Management: Best practices for garbage collection, including the mandatory usage of 'ref' for Managed classes and proper lifecycle management to prevent memory leaks and dangling pointers in the Enfusion engine.

• UI System Integration: Managing dynamic UI layouts and context activation using the OVT_UIContext framework, ensuring responsive interaction design within the game world.

• Always utilize RplId instead of EntityID for networked references to maintain state consistency across client/server sessions.

• Enforce strict typing and avoid the use of ternary operators in EnforceScript to comply with compiler limitations and coding standards.

• Perform regular entity existence checks before accessing object properties to prevent runtime crashes caused by the asynchronous nature of entity destruction.

• Inputs typically involve script-level logic definitions, component parameters, or persistence data structures; outputs result in reliable, performant, and synchronized gameplay features.

• Users should consult the resource files for specific syntax, anti-patterns, and 'common-pitfalls' to avoid common debugging bottlenecks in the Arma modding environment.