Skip to main content

Optional GAS Integration

The plugin has no GameplayAbilities module dependency, AbilitySystemComponent integration, AttributeSet or built-in GameplayEffect bridge. The PDFs describe an optional architectural integration, not a feature that happens automatically.

Keep Survival as state owner. Project ability code can query survival values, validate an action on the server and invoke component interface mutations. A project bridge can translate life tags/value changes to Gameplay Events or mirrored attributes.

GameplayEffects do not automatically modify these component properties. Implement a deliberate translation layer and avoid a feedback loop where both mirrored attributes and Survival independently overwrite the same resource. Use the current API and account for missing direct stamina/temperature numeric mutation nodes.

GAS can remain entirely in the project integration without modifying the plugin for supported existing calls. New native state setters, additional replicated stats or different pulse semantics may require maintained code extensions. Establish and test those contracts rather than treating general GAS compatibility as an implemented adapter.