Configuration

Settings come from four places, each overriding the one before it: shared/schema.lua defaults, data.json at the resource root, a vehicle pack's tafk.json, then the player's own tafk:* settings. Sequences are a union of data.json and the packs.

Almost nothing here needs a text editor. The camera sequences are built in the in-game editor (/tafkedit) and every server setting is tunable live from /tafk; data.json is what those two write, and is documented below as reference for reading it or shipping one with a vehicle.

Admin settings via /tafk

Every settings field is tunable live with the tlib.admin ACE, and clamped server-side: timeoutSeconds 0–3600, durations 1000–45000, beatAnchorMs ±1000, musicVolume 0–1, radioDelaySeconds 5–60, radioStreamUrl https and ≤512 chars. A value outside its range is refused and logged, not written.

The duration sliders are in seconds — minimum 1–30, maximum 2–45 — and are stored in milliseconds.

Player KVP overrides

Per-vehicle sequence packs

A vehicle resource can ship its own sequences. Declare them in its manifest and tAFK merges them in on start.

files { 'tafk.json' }
tafk_config 'tafk.json'

{ "mycar": { "sequences": [ "… entries exactly as in data.json" ] } }

data.json shape

Read once at server start. After a direct edit run restart tAFK, which re-scans audio/ too. Invalid sequences are dropped with a server-log warning.

Four top-level keys: version, settings, sequences, and vehicleConfigs. Do not edit vehicleConfigs by hand — it is written for you by the editor and by vehicle packs.

settings

Live radio

The stream replaces the audio/ rotation. Leave radioDelaySeconds alone — beat-matching needs that lookahead.

Each AFK player opens their own connection, ~24 KB/s at 192 kbps. A dead mount, or one with no CORS header, falls back to audio/.

sequences[]

Keyframe shape

{ "offset": [-6.0, -7.0, 0.1], "rotation": [3.0, 0.0, 30.0], "fov": 55.0,
  "dof": { "near": 2.0, "far": 20.0, "strength": 0.7 } }

Offsets also accept { "x": …, "y": …, "z": … }.

Music tracks

Drop .ogg, .mp3 or .wav files into tAFK/audio/ and restart. Any filename works, with nothing to register: the folder is the authority, re-scanned every boot, and tracks are not in data.json.

Beat data

Beat-matched cuts need a grid per track, in audio/beatmap.json.

You need run nothing: analysis starts 30 seconds after load and happens in the background, one track at a time. An un-analysed track still plays, at random shot lengths. The offline analyser in tools/audio/beatmap.sh produces a better grid, and is never overwritten by the automatic one.

The offline script defaults to tLoading's beatmap, so point --out at tAFK's:

./tools/audio/setup.sh   # once
./tools/audio/beatmap.sh --out "data/resources/[tScripts]/tAFK/audio/beatmap.json" \
    analyze "data/resources/[tScripts]/tAFK/audio/"*.ogg

File layout

The paths you touch; the rest is internal.

shared/schema.lua is unencrypted in your install, so every default on this page is readable there.