- Updated README.md files for extension, garage, locker, main, organization, phone, store, and task addons to provide clearer overviews, dependencies, main components, and usage notes. - Improved task module documentation to clarify timer semantics and server task flows, ensuring accurate usage of time limits. - Adjusted default values for task time limits and IED timers to enforce positive countdown requirements. - Added new CAD addon for dispatch coordination, including its overview, dependencies, main components, and event handling.
1.1 KiB
1.1 KiB
Forge Server Locker
Overview
The locker addon is the server-side bridge for player item storage and owner-scoped arsenal unlock storage.
Locker hot state is owned by the extension. SQF handles client events, payload validation, synchronization, and save calls.
Dependencies
forge_server_mainforge_server_commonforge_server_extensionat runtime for locker extension callsforge_client_lockerfor response RPCs
Main Components
fnc_initLocker.sqfinitializes locker world objects.fnc_initLockerStore.sqfmanages player locker hot state.fnc_initVAStore.sqfmanages owner-scoped arsenal unlock state.
Supported Operations
- initialize player locker data
- save player and owner-scoped locker state
- override locker data from trusted server-side callers
- initialize and save owner-scoped arsenal storage
Runtime Notes
forge_server_main_fnc_saveHotState saves both LockerStore and VAStore on
disconnect and mission shutdown. Store checkout and task rewards can grant
assets into organization-owned storage through the org addon.