How the systems connect
One operation. Several clear owners.
These examples show the boundary between one SGF mechanism and the next. For genre-level assemblies, explore the game compositions.
01 / System flow
A melee contact
Detection is not a damage formula.
StormCombat
Detects an authored melee contact.
Your resolver
Chooses its effect using the game's rules.
Body or abilities
Optionally respond through StormBody and abilities.
02 / System flow
StormItems
Identifies the item.
StormInventory
Optionally owns it.
First-party adapter
Requests a tagged StormEquipment slot change.
Weapon / appearance adapters
Optionally respond to the equipment change.
03 / System flow
04 / System flow
A world event chooses a place
World identity does not define the event.
SGFWorld
Describes meaningful areas.
SGFWorldDirectorAdapter
Queries a valid loaded place.
SGFDirector
Checks conditions and objectives.
Game script
A studio-authored event script acts.
05 / System flow
A vehicle returns from save
Fuel and doors may persist; occupancy is re-evaluated.
SGFTransport
Maintains vehicle state.
SGFTransportSave
Captures durable properties.
SGFSave
Stores the record.
Authority-side restore
Authoritative components restore it; occupants are handled anew.
Available to license
Ask about SGF licensing.
Tell us which systems you need and which Unreal Engine version you use. We can discuss licence terms and integration with your project.
Ask about licensing