ArmaDB

**UPDATED Core 9/28/26**

Players now

16

Servers

36

Rating

-

Subscribers

-

280 downloads

Get it on the Workshop reforger.armaplatform.com/workshop/69B8F5006D19D33E

Busiest servers running it 36 in total

All servers

Players on servers with it

daily, last 30 days

0 25 50 75 100 24 Sep 1 Oct 8 Oct 15 Oct peak 85
Average players Low to peak in each bucket

Details

Author
ForgedInFire
Version
2.1.0
Size
2.4 MB
Licence
APL
Game version
1.8.0.13
Likes
0 / 0 dislikes
Published
30 Jun 2026
Updated
2 weeks ago
Workshop ID
69B8F5006D19D33E

Recent adoption

30 days: +84 −46 ↑27

Version history

12
  1. v2.1.0 2.4 MB 29 Sep 2026

    NEW - Added EOverridePolicy shared enum with DEFAULT, DENY, and ALLOW policies. - Added shared named logger helper for dependent ForgedInFire mods. - Added configuration prefix support for mod-specific configuration overrides. CHANGED - FiF_Core configuration logging now uses the named "FiF_Core" logger. - Updated Core configuration defaults for compatibility with Save Loadout V2. This update provides the Core functionality required by Save Loadout V2 and includes API changes that may be incompatible with earlier versions of Rank Unlock V2. Server Managers with other Forged in Fire mods installed should not need to update FiF_Core manually. However, if you do update it manually, you will also need to ensure that any/all other Forged in Fire mods installed on your server have been updated to compatible versions.

  2. v2.0.2 2.4 MB 26 Sep 2026
  3. v2.0.1 8 KB 24 Sep 2026
  4. v2.0.0 8 KB 24 Sep 2026
  5. v1.0.19 7 KB 3 Jul 2026
  6. v1.0.18 7 KB 1 Jul 2026
Description from the Workshop

FiF_Core is the shared configuration and infrastructure foundation for ForgedInFire modules. FiF_Core depends on ScriptLoggerV2. Logging is provided through the named-logger API; Core uses FiF_SL_SLogger.GetLogger("FiF_Core"). FiF_Core contains no gameplay features. Dependent modules own their gameplay behavior and configuration declarations while Core provides the shared runtime registry used to resolve effective configuration values. RUNTIME CONFIGURATION REGISTRY FiF_Core maintains typed runtime configuration registries. The current implementation supports: • bool • int Configuration values are registered by a stable, case-sensitive configuration name. The first value registered for a name wins. A later registration of the same name succeeds without overwriting the value already stored in Core. This allows configuration names to be shared intentionally between modules while leaving unrelated configuration names effectively module-specific. Dependent modules register configuration entries rather than registering their configuration components with Core: ref array<ref FiF_CoreConfigEntry> configs = {}; configs.Insert(FiF_CoreConfigEntry.CreateBool( "FeatureEnabled", false )); configs.Insert(FiF_CoreConfigEntry.CreateInt( "RequiredRank", 1 )); FiF_CoreConfig.RegisterConfigs(configs); FiF_CoreConfig.GetConfigs(configs); Individual runtime consumers may retrieve effective values directly from Core: bool featureEnabled = FiF_CoreConfig.GetBool( "FeatureEnabled", false ); int requiredRank = FiF_CoreConfig.GetInt( "RequiredRank", 1 ); The supplied fallback is returned if the requested configuration value is not registered. CONFIGURATION ENTRIES FiF_CoreConfigEntry provides the typed configuration-entry representation used for bulk registration and retrieval. Create entries with the named factory appropriate to the value type: FiF_CoreConfigEntry.CreateBool("FeatureEnabled", false); FiF_CoreConfigEntry.CreateInt("Requi...