Quickstart For Humans And Agents

Quickstart For Humans And Agents

This page is the low-friction route into the repo. Use it before editing mission code or asking an AI assistant to implement changes.

Thirty-Second Orientation

Fact	Value
Repo	rayswaynl/a2waspwarfare
Runtime	Arma 2: Operation Arrowhead 1.64
Mission type	Warfare / CTI TvT PvE
Source mission	Missions/[55-2hc]warfarev2_073v48co.chernarus
Generated targets	Missions_Vanilla/*, Modded_Missions/*
Generator	Tools/LoadoutManager
AI context	agent-context.json

If You Are Human

1. Read Home for the map.
2. Read Mission entrypoints to understand startup.
3. Read Lifecycle wait-chain before reordering init or wait barriers.
4. Read SQF code atlas before changing functions, PVF commands or init files.
5. Read Gameplay systems atlas before touching towns, economy, commander, upgrades, construction or factories.
6. Read WASP overlay before changing project-specific additions under WASP/.
7. Read Feature status register before reviving old code.
8. Check Agent worklog for the latest Codex/Claude findings.

If You Are An LLM

Load these first, in order:

1. agent-context.json
2. Agent context
3. SQF code atlas
4. Gameplay systems atlas
5. Lifecycle wait-chain
6. WASP overlay
7. Documentation implementation plan
8. Feature status register
9. Agent worklog

Then inspect source before making claims. Do not infer Arma 3 behavior. If you add high-level facts, update agent-context.json.

Safe Edit Checklist

Before editing	Why
Confirm whether the target is source or generated	Generated mission folders may be overwritten by LoadoutManager.
Use -LiteralPath on Windows	[55-2hc] breaks wildcard-based PowerShell paths.
Find owner side	Server, client, common and headless paths have different locality/network rules.
Check PV/publicVariable behavior	Network changes can affect hosted, dedicated and JIP behavior.
Check performance loops	Marker, AI, town and UI loops are live-server sensitive.
Record docs impact	Update the wiki and Agent-Worklog.md when architecture changes.

Common Tasks

Task	Start with
Add or change a PVF command	SQF code atlas, Networking and public variables
Change supply missions	Supply mission architecture, Economy, towns and supply
Change commander/upgrades	Core systems index, Feature status register
Change town capture/economy/construction/factories	Gameplay systems atlas
Change UI or buy menus	Client UI, HUD and menus, Client UI systems atlas
Change AI/headless behavior	AI, headless and performance
Change WASP custom scripts	WASP overlay, Feature status register
Touch generated missions	Tools and build workflow, Content structure and maps

Agent Collaboration

Agent	Best role
Codex	Maintains the living atlas, agent context, publishing flow and implementation handoffs.
Claude	Independently reviews, challenges assumptions, finds hidden coupling and deepens subsystem evidence.
Future agents	Start from agent-context.json, inspect source and append findings to Agent-Worklog.md.

Use Claude long-term goal when spinning up Claude as a persistent counterpart.

Continue Reading

Previous: Home | Next: Architecture overview

Main map: Home | Fast path: Quickstart | Agent file: agent-context.json