9d789440e0
- 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.
30 lines
1.1 KiB
Markdown
30 lines
1.1 KiB
Markdown
# Forge Server Extension
|
|
|
|
## Overview
|
|
The extension addon is the SQF bridge to the `forge_server` arma-rs extension.
|
|
It normalizes `callExtension` responses, routes large payloads through the
|
|
transport layer, and exposes helper functions used by extension-backed server
|
|
addons.
|
|
|
|
## Dependencies
|
|
- `forge_server_main`
|
|
|
|
## Main Components
|
|
- `fnc_extCall.sqf` is the primary extension call wrapper.
|
|
- `fnc_transport.sqf` stages large requests and assembles chunked responses.
|
|
- `fnc_setHandler.sqf` registers local SQF handlers for extension callback
|
|
integration.
|
|
|
|
## Transport Behavior
|
|
Most commands use direct `callExtension`. Commands that can return large
|
|
payloads, or requests whose encoded arguments exceed the chunk threshold, are
|
|
routed through `transport:invoke` or staged transport requests.
|
|
|
|
The wrapper falls back to direct calls if the transport route is unsupported and
|
|
the request was not chunked.
|
|
|
|
## Notes
|
|
Domain addons should call `EFUNC(extension,extCall)` instead of calling the
|
|
extension directly. This keeps response handling, chunking, and error logging
|
|
consistent.
|