FiF_Core

What FiF_Core Provides
Unified Configuration Entity  
A single FiF_CoreConfigEntity placed in the world that acts as the central hub for all FiF modules.
Modules attach their own configuration components to this entity automatically when loaded.
Global Script Logging System  
A consistent, configurable logging API used by all FiF modules.
Includes:
stdout logging
file logging
log level filtering
prefix customization
retention controls
sandbox‑safe $profile: directory handling
Optional FileIO Support  
Core includes a safe, sandbox‑aware file I/O layer that modules may use if needed.
Modules that don’t require file access remain unaffected.
What FiF_Core Does Not Do
FiF_Core intentionally contains no gameplay features.
It does not modify missions, factions, loadouts, ranks, or AI.
It exists purely to support other FiF modules.
Why FiF_Core Exists
FiF_Core ensures that all FiF modules:
share the same logging system
share the same configuration entity
avoid duplicating boilerplate code
remain fully modular and independent
can be mixed and matched without conflicts
This keeps the ecosystem clean, predictable, and easy to maintain.
Testing FiF_Core
Since FiF_Core has no gameplay features, testing focuses on:
verifying the config entity loads correctly
confirming the logger initializes
checking console output
checking log file creation
validating config changes affect behavior
If logs appear correctly and no errors are printed, FiF_Core is functioning as intended.
Who Should Install FiF_Core*
Anyone using any ForgedInFire module must install FiF_Core.
It is the shared foundation that all FiF mods depend on.

*Does not apply to FIF Mods name Rank Unlock - V2, Rank Unlock - Partisan, or Save Loadout - Partisan.  If you install any of those, they are not dependent on this FiF_Core.  Those features will be available through FIF_Core using newly developed Rank and Save addons.