Timers and service settings

These functions declare mod policy during startup. They do not expose arbitrary configuration files. Multiple mods must respect the ownership rules below.

sf2.timers.set

Set the delivery duration and early-skip policy for new forge orders, optionally making already-paid pending orders eligible for immediate normal completion, or set a shared time limit for timed battles.

Signature: sf2.timers.set { subsystem, seconds, skip_enabled?, complete_pending? }

Requires: policy.timers.

When: Entrypoint.

Returns: nil.

Field	Type	Default	Meaning
subsystem	String	Required	"forge", "battle", or "raid".
seconds	Integer	Required	Forge: 0–31536000, zero is instant. Battle and raid: 1–86400 seconds per round.
skip_enabled	Boolean	true	Forge early completion; leave at its default for battle timers.
complete_pending	Boolean	false	With seconds = 0, make saved, already-paid forge orders eligible for normal completion on the next delivery update. Rejected for nonzero durations.

sf2.timers.set {
    subsystem = "forge", seconds = 0,
    skip_enabled = false, complete_pending = true,
}

Only one mod may own a subsystem’s timer policy. Competing declarations fail rather than choosing the last-loaded mod.

sf2.timers.set { subsystem = "battle", seconds = 150 }
sf2.timers.set { subsystem = "raid", seconds = 999 }

The battle policy overrides positive round limits in core and mod fights when each round is prepared. Training (FightNone) and untimed fights retain their native behavior. It overrides a fight’s declared round_time while enabled, but does not rewrite its definition or save. Disabling the mod restores the original limit. The policy does not change simulation speed, animation timing or raid session deadlines. Battle policies reject skip_enabled = false and complete_pending = true; those options belong to forge delivery.

The "raid" policy overrides the "battle" policy for native FightRaid battles, fights on mod Underworld pages, and fights registered through sf2.raids.register. It covers normal and Power Mode rounds. Without a raid policy, these fights keep the battle policy or their original limit. A raid-only policy leaves other battles unchanged. Training and untimed fights remain excluded; raid policies have the same duration limits and forge-option restrictions as battle policies. Raid session deadlines are separate from per-round limits.

For forge policies, with the default complete_pending = false, existing saved deadlines retain their original behavior. With true, their displayed remaining time is zero and the normal delivery update applies the enchantment, clears the pending order, and saves the result. This is ordinary completion, so it does not require skipping to be enabled and does not charge materials a second time.

Registration never edits a saved deadline or grants an enchantment. Disabling the policy before settlement restores the original remaining time; an already-completed enchantment stays completed. As in the original game, completing an order rolls the enchantment and then closes the order; if no candidate qualifies at that point (for example a set perk whose set is no longer complete), the order is still closed and its materials are not returned. Early completion (skip_enabled) takes the same path. Material costs are unchanged. Shop delivery is not an additional supported timer target.

sf2.services.disable

Disable a supported optional service feature group.

Signature: sf2.services.disable(name)

Requires: policy.services.

When: Entrypoint.

Returns: nil.

sf2.services.disable("battle_pass")

Accepted names are paid_offers, battle_pass, ads, rewarded_video, online_services, and payments. Unknown names are rejected. Disables from multiple mods combine. This is an opt-out: it cannot install or re-enable an absent service, remove SDK code from a build, or mutate arbitrary UI objects. If the offline build already lacks a service, disabling it may have no visible effect.