Dynamic Config User Guide

1. What Dynamic Config does

Arkasm's Dynamic Config system lets you keep reusable profiles and change the configuration currently being supplied to an ASA server without repeatedly editing its normal INI settings.

Profiles are shared across Arkasm, so the same profile can be reused on several servers. Each profile can contain Dynamic Config rate settings and, optionally, raw Live Tuning JSON. Rate settings can use exact Fixed Values or Event Multipliers calculated from each server's normal base settings.

When Dynamic Config is enabled for a server, Arkasm configures ASA to use Arkasm's loopback-only HTTP service. The generated working files are stored under %AppData%\Arkasm\DynamicConfig\Generated\. Each managed server has its own URL path, but the service is accessible only from the PC running Arkasm.

2. Quick start

Open the Dynamic Config tab for the server you want to configure.

The Override is temporary and has the highest priority. When it ends, Arkasm automatically restores the current ARK Event or Scheduled profile, or returns to normal INI rates if neither applies.

3. The Dynamic Config tab

The main page separates day-to-day rate controls from delivery settings. The Rates page contains profile editing, schedules and temporary Overrides. The Delivery page contains the local HTTP service settings.

4. Creating and editing profiles

Click Edit Profiles… to open the shared profile editor. Profiles in the list on the left are available to every managed server. The Current Base and Effective values are calculated for the server from which you opened the editor.

1. Add or select a profile. Click Add to create a profile, or select an existing profile from the list.
2. Edit the rates. On the Dynamic Config Rates tab, choose a mode and value for each setting you want the profile to change.
3. Add Live Tuning if required. On the Live Tuning JSON tab, paste the raw JSON that should be published with this profile. Leave it blank when the profile should not publish Live Tuning data.
4. Save the profile. Check the Effective values and click Save Profile.

Fixed Value and Event Multiplier

Each recognised Dynamic Config rate setting can be left Not Set, assigned a Fixed Value, or expressed as an Event Multiplier.

Manual or newer Dynamic Config settings

If a profile INI contains settings that are not yet handled directly by Arkasm, those settings are preserved when the profile is loaded and saved. Use Open INI File if you need to add or edit such a setting manually.

Live Tuning JSON

Live Tuning JSON is optional and belongs to the profile itself. When that profile becomes effective through an Override, ARK Event or Schedule, Arkasm publishes the JSON at the server's CustomLiveTuningUrl alongside the generated Dynamic Config INI.

Arkasm configures CustomLiveTuningUrl automatically when Dynamic Config is enabled. You do not need to create a file called DefaultOverloads.json, and Arkasm does not change ASA's LiveTuningFileName setting.

The following example shows the general structure expected by Live Tuning: blueprint paths at the top level, with the properties to override inside each blueprint object. It is included as a formatting example only; use values and properties appropriate to your own server.

{
    "Blueprint'/Game/PrimalEarth/Structures/CookingPot.CookingPot'": {
        "DecayDestructionPeriod": 324000,
        "DecayDestructionPeriodMultiplier": 4
    },
    "Blueprint'/Game/PrimalEarth/Structures/Electric/ElectricCableIntersection.ElectricCableIntersection'": {
        "DecayDestructionPeriod": 324000,
        "DecayDestructionPeriodMultiplier": 4
    },
    "Blueprint'/Game/PrimalEarth/Structures/Electric/ElectricCableStraight.ElectricCableStraight'": {
        "DecayDestructionPeriod": 324000,
        "DecayDestructionPeriodMultiplier": 4
    },
    "Blueprint'/Game/PrimalEarth/Structures/Electric/ElectricCableDiagonal.ElectricCableDiagonal'": {
        "DecayDestructionPeriod": 324000,
        "DecayDestructionPeriodMultiplier": 4
    },
    "Blueprint'/Game/PrimalEarth/Structures/Electric/Electric_Cable_Vertical.Electric_Cable_Vertical'": {
        "DecayDestructionPeriod": 324000,
        "DecayDestructionPeriodMultiplier": 4
    },
    "Blueprint'/Game/PrimalEarth/StructuresPlus/Wires/Flex/BP_Wire_Flex.BP_Wire_Flex'": {
        "DecayDestructionPeriod": 324000,
        "DecayDestructionPeriodMultiplier": 4
    },
    "Blueprint'/Game/PrimalEarth/Structures/Electric/ElectricJunction.ElectricJunction'": {
        "DecayDestructionPeriod": 324000,
        "DecayDestructionPeriodMultiplier": 4
    }
}

Because Arkasm deliberately does not validate this content, check the JSON carefully before using it on a live server.

5. Event colours

DynamicColorset has its own colour-set editor, so you do not need to memorise or type ARK's exact colour names. On the DynamicColorset row, choose Custom Colours and use Select Colours….

The Filter box narrows the list. While a filter is active, the first checkbox is labelled All filtered colours and affects only the colours currently shown. Clear removes the filter and restores the full list.

6. Applying a temporary Override

An Override is a temporary, highest-priority profile application. It is useful for an immediate rate change, testing a profile, or temporarily replacing an ARK Event or Scheduled profile without changing those underlying assignments.

1. Select the Override profile. The dropdown remains an input for the next Override; it is not a status indicator.
2. Set the duration. Specify the required hours and/or minutes. The duration must be greater than zero.
3. Click Apply Override. Arkasm publishes the profile immediately and records when the Override should expire.

The Override ends automatically at the end of its duration. You can also click End Override Now to end it early. Arkasm then restores the current ARK Event or Scheduled profile, or normal INI rates if neither is eligible.

7. Copying an Override to other servers

Copy To… applies the selected Override profile and duration to other managed servers. It does not enable Dynamic Config on the destination servers; each selected destination must already have Dynamic Config enabled.

Arkasm reports any destinations that were skipped because Dynamic Config is disabled, any server that requires a restart before the current setup can take effect safely, and any server for which an immediate refresh could not be confirmed.

8. Scheduling event-rate periods

Open Schedules… to create periods during which a shared profile is eligible to become active. The scheduler window also provides Edit Profiles… so you can maintain the same shared profile library without creating a separate schedule-only profile.

Single Shot

Use a Single Shot period for a one-off event with specific start and end dates and times. Auto-delete when finished removes the completed schedule automatically.

Repeating — Week

Weekly periods use a start time, end time and selected weekdays. Consecutive selected days form one continuous block.

Repeating — Month

Monthly periods work the same way, using days of the month. Consecutive selected dates form one continuous period, including across month boundaries. For example, selecting the 31st and the 1st joins 31 January and 1 February into one period.

A selected date is skipped in months that do not contain it. For example, a period set only for the 31st does not run in April; it is not moved to 30 April. Other selected dates that exist in that month still apply.

Pausing scheduled changes

Tick Pause Scheduled Changes on the main page when you want to suppress all Scheduled profiles temporarily. If an Override is active it remains highest priority; otherwise an eligible ARK Event profile can remain active. If neither applies, the server uses normal INI rates. Clearing the checkbox immediately reevaluates the current schedule.

Individual periods can also be paused or resumed in the schedule editor. This is separate from the main Pause Scheduled Changes switch, which suppresses the whole Scheduled source for that server.

9. Priority and automatic restoration

A server can have a temporary Override, an ARK event profile request and an active Scheduled period at the same time. Arkasm resolves them in this order:

If none of those sources is active, the server uses its normal INI rates. Lower-priority requests remain stored while they are overridden, so Arkasm can restore the next eligible source automatically when a higher-priority source ends.

Within the Scheduled layer, if periods overlap, the active period that started most recently has priority. When it ends, an earlier overlapping period that is still active can resume.

10. Linking profiles to ARK events

An optional Dynamic Config profile can be assigned to each configured ARK event. When that event becomes the effective source, Arkasm publishes the profile's Dynamic Config rates and any optional Live Tuning JSON; when the event ends, Arkasm restores the next eligible source.

When an event with an assigned profile becomes active, its profile takes priority over Scheduled profiles but remains below a temporary Override. When the event ends, Arkasm restores the appropriate Scheduled profile or normal INI rates.

11. Viewing detailed status

Click View Status… to inspect the detailed Dynamic Config state for the current server. The window shows whether Dynamic Config is enabled for the server, the effective profile and source, current Override status, Scheduled state, local HTTP service, configured Dynamic Config URL, publication/fetch information, restart state and the next scheduled transition.

Force Refresh

Force Refresh is a manual Dynamic Config resynchronisation tool. It is not required after every profile change. Use it when troubleshooting a mismatch between the published Dynamic Config INI and the running server.

Live Tuning is intentionally separate from the Dynamic Config fetch-confirmation mechanism. Arkasm keeps the effective profile's Live Tuning JSON available at its configured URL, but does not control or confirm when ASA re-reads that URL, and a Live Tuning request does not count as confirmation of a Dynamic Config refresh.

Open Published INI opens the exact generated Dynamic Config INI currently being served for that server.

12. Troubleshooting

13. Quick reference

Which source has priority?

Override > ARK Event > Scheduled > normal INI rates. Within the Scheduled layer, the active period that started most recently wins when periods overlap.

Does selecting an Override profile immediately change the server?

No. The dropdown selects the profile for the next Override. Set a duration and click Apply Override to activate it.

What happens when no profile is active?

If Dynamic Config is enabled but no Override, ARK Event or Scheduled profile is eligible, the server uses its normal INI rates.

Are profiles server-specific?

No. Profiles are shared across Arkasm. Effective Dynamic Config values can differ between servers when Event Multiplier is used because each server can have different normal base settings.

Is Live Tuning JSON required?

No. It is completely optional. Leave the Live Tuning JSON tab blank and Arkasm publishes no Live Tuning JSON resource for that profile.

Does Arkasm validate Live Tuning JSON?

No. Arkasm publishes the text exactly as entered and does not interpret, merge or repair it.

Do I need to set CustomLiveTuningUrl or LiveTuningFileName myself?

No. Arkasm manages CustomLiveTuningUrl for Dynamic Config-enabled servers and leaves LiveTuningFileName untouched.

Where are the generated live-delivery files stored?

Under %AppData%\Arkasm\DynamicConfig\Generated\ on the PC running Arkasm. The local HTTP service serves the appropriate resources to each local ASA server.

Does the scheduler work while Arkasm is closed?

No. Arkasm must be running for scheduled starts and finishes to be processed.

Do I need to use Force Refresh after every change?

No. Use it only as a manual Dynamic Config resynchronisation or troubleshooting tool.