- Revised README.md for the Forge Client Example Addon to clarify its purpose as a template. - Enhanced MODULE_REFERENCE.md to categorize guides into Server and Extension guides and Client guides. - Created detailed usage guides for various client addons including Actor, Bank, CAD, Garage, Locker, Notifications, Organization, Phone, and Store. - Added a Client Common Usage Guide to outline shared browser UI bridge patterns. - Introduced a Client Main Usage Guide to define the foundational elements for client addons. - Established authoritative state notes and usage rules across new guides to ensure clarity on server ownership and client responsibilities.
19 lines
558 B
Markdown
19 lines
558 B
Markdown
# Forge Client Main
|
|
|
|
## Overview
|
|
The main addon provides shared mod metadata, macros, settings, and compile
|
|
infrastructure for Forge client addons.
|
|
|
|
## Dependencies
|
|
- `cba_main`
|
|
|
|
## Main Components
|
|
- `script_macros.hpp` defines shared function, RPC, path, variable, and compile
|
|
macros.
|
|
- `script_mod.hpp` and `script_version.hpp` define mod identity and version.
|
|
- `CfgSettings.hpp` contains client-side CBA settings.
|
|
|
|
## Notes
|
|
Feature logic should live in the owning addon. Main is the shared foundation for
|
|
configuration, macros, and mod-level metadata.
|