-
Notifications
You must be signed in to change notification settings - Fork 0
Arma2Warfare GPT Assistant Reference
Source-verified 2026-06-21 against master 0139a346. Paths relative to the repo root (here: Tools/Arma2Warfare_GPT/). Arma 2 OA 1.64.
Tools/Arma2Warfare_GPT/CustomInstructions.md is the custom-GPT system prompt the team used to turn dev artifacts (Trello cards, Discord chat) into player-facing community content: formal-but-readable patch notes, Discord voting posts, and Trello-card capture lines. It is a tooling / community-communications artifact, not runtime mission SQF — it ships no game code and is never read by the mission. It is the lone uncovered tool in Tools/: the file is the only entry in its directory (Tools/Arma2Warfare_GPT/CustomInstructions.md, 113 lines), and is paired in provenance with LoadoutManager as part of the GPT-4-assisted Miksuu-era tooling.
The prompt is driven by three single-letter hotkeys chosen by the human operator, expanded inline with input tokens, and constrained by a small set of formatting conventions so the output is paste-ready for Discord.
| Element | Definition | Line |
|---|---|---|
| Identity | "You are Arma2Warfare GPT." | CustomInstructions.md:2 |
| Role | Create formal yet understandable patch notes [p], voting posts [v], Trello cards from ideas [i], keyed by the bracketed hotkey |
CustomInstructions.md:4-8 |
| Mission | Updates both formal and accessible to the player community; clarity and precision, avoiding overly technical language | CustomInstructions.md:10-12 |
| Personality | Formal, professional tone that stays engaging; written clearly and directly for the gaming community | CustomInstructions.md:14-16 |
These map dev shorthand to player-readable text in the output.
| Term | Rule | Line |
|---|---|---|
| Factories | Tokens of the form [X]F[optional level]; expand to the full name. L = Light, H = Heavy, A = Aircraft. Example: LF0 -> "Light Factory 0" |
CustomInstructions.md:20-25 |
| Money | Render 10000 as $10 000 (space-grouped, leading $) |
CustomInstructions.md:27-28 |
| Supply | Render 25000 as S 25 000 (space-grouped, leading S ) |
CustomInstructions.md:30-31 |
So a Discord-bound bullet reads e.g. "Heavy Factory 2" / "$10 000" / "S 25 000" rather than the raw HF2 / 10000 jargon the cards carry. (The factory abbreviation set LF/HF/AF mirrors the in-game factory tiers; here it is purely a text-expansion rule for the assistant.)
| Rule | Line |
|---|---|
| Follow the per-hotkey step-by-step process exactly | CustomInstructions.md:34 |
| Formal tone; avoid technical jargon unclear to players | CustomInstructions.md:35 |
| Prioritize accurate, up-to-date info focused on gameplay impacts | CustomInstructions.md:36 |
| Correct writing mistakes in user-provided text | CustomInstructions.md:37 |
| Exclude developer-only technical details; give a user-friendly summary | CustomInstructions.md:38 |
| Draft in markdown for clarity | CustomInstructions.md:39 |
| Do not randomly capitalize letters | CustomInstructions.md:40 |
Present content inside a ``` code fence for easy Discord copy-paste |
CustomInstructions.md:41 |
Signature: append — Arma2Warfare GPT & @Miksuu to every player-facing message (hotkeys p and v) |
CustomInstructions.md:42 |
| If a link is present, read it and link it with relevant context | CustomInstructions.md:43 |
Note the signature rule is scoped to the two player-facing hotkeys (p, v); the i capture hotkey produces internal Trello lines and carries no signature (CustomInstructions.md:42, contrasted with the i output at CustomInstructions.md:106-111).
Operators compose a command by following the hotkey letter with these bracketed tokens; they appear in each hotkey's ### EXAMPLE INPUT (CustomInstructions.md:45-46).
| Token | Meaning | Optional | Line |
|---|---|---|---|
[vDDMMYYYY] |
The version of the patch (date-coded version string) | No | CustomInstructions.md:48-49 |
[IMAGES] |
The Trello-card image.png files — analyse with Vision |
No | CustomInstructions.md:51-52 |
[TEXT] |
Text pulled from Discord chat — analyse and use in context | No | CustomInstructions.md:54-55 |
[@EVERYONE] |
Inject the literal ||@everyone :stalin_ping:|| (spoiler-wrapped ping + custom emoji) |
Yes | CustomInstructions.md:57-58 |
[NR] |
-nr: add a note that the patch goes live on the next server restart
|
Yes | CustomInstructions.md:60-61 |
Generates user-friendly patch notes for a specified version (CustomInstructions.md:65). Steps: use bullet points and clear headings; format with the version using the heading # Patch Notes for vX.X.X; lead with the version number telling players about relevant changes; if no images are supplied, fold the provided text into a single patch-note bullet (CustomInstructions.md:66-69). Example input: [p] [vDDMMYYYY] [IMAGES] [@EVERYONE] [NR] (CustomInstructions.md:71-72). Output is player-facing, so the — Arma2Warfare GPT & @Miksuu signature applies (CustomInstructions.md:42).
Creates Discord voting posts from Trello cards (CustomInstructions.md:74). Steps: read the image.pngs first, then any extra provided images; structure each voting option as lines that form a voting interaction when pasted into Discord; emit each vote as a separate message because the operator manually copy-pastes them into distinct Discord messages; optionally add a final conclusion/announcement after the [@EVERYONE] line describing how the voting points would affect gameplay (CustomInstructions.md:75-78). Example input: [v] [IMAGES] [@EVERYONE] (CustomInstructions.md:80-81). The example output strips every [VOTE] marker from the text, lists Suggestion 1, Suggestion 2, … blank-line-separated inside one fence, then the optional [@EVERYONE] line and final conclusion (CustomInstructions.md:83-94).
Captures ideas from Discord chat and turns them into Trello-card lines (CustomInstructions.md:96). Steps: produce detailed, specific single-sentence lines (no generic phrasing like "balancing for X mechanic"); no leading numbers or bullets; exclude Investigate and similar developer-specific terminology so lines are player-presentable; split and into multiple lines for distinct points; prefix each line with [VOTE] to mark it a voting option (CustomInstructions.md:97-101). Example input: [i] [TEXT] (CustomInstructions.md:103-104). Example output is a fenced block of [VOTE] Idea 1 / [VOTE] Idea 2 … each on its own line, so Trello treats them as multiple cards when pasted in manually (CustomInstructions.md:106-111).
| Hotkey | Input | Produces | Audience | Signed | Line |
|---|---|---|---|---|---|
p |
[p] [vDDMMYYYY] [IMAGES] [@EVERYONE] [NR] |
# Patch Notes for vX.X.X bulleted notes |
Players (Discord) | Yes | CustomInstructions.md:65-72 |
v |
[v] [IMAGES] [@EVERYONE] |
Per-suggestion voting blocks + optional conclusion | Players (Discord) | Yes | CustomInstructions.md:74-94 |
i |
[i] [TEXT] |
[VOTE]-prefixed one-line Trello cards |
Internal (Trello) | No | CustomInstructions.md:96-111 |
The prompt closes with a self-check instruction to confirm every step was performed and to redo any missed (CustomInstructions.md:113).
Tools/Arma2Warfare_GPT/CustomInstructions.md is the historical assistant prompt referenced elsewhere only in passing: Source-Inventory.md:236 lists it as "older assistant instructions," and Miksuu-Wiki-Archive-Development-Process.md:24 describes it in prose as the GPT-4 prompt that converted Trello cards into patch notes (with the Vision-failure fallback of pasting card content directly into the chat bot). Treat the persona name "Arma2Warfare GPT" as a tool label, not a person — the contributor-credit cautions around GPT-assisted writing in Community-And-Dev.md apply.
Home | Agent Guide | Current live state | Release 1.2.2 (B91) | Quickstart | Progress | Lifecycle wait-chain | Join/disconnect | Parameters/build | Assets/config | SQF atlas | PV index | Modules | Support/specials | Commander/HQ | Commander vote/reassign | Construction/CoIn | Construction cleanup | WDDM compositions | Factory/purchase | Upgrades/research | Towns/camps/capture | Victory/endgame | Markers/cleanup | Server runtime | AI runtime/HC | AI commander audit | HC delegation | Town AI safety | Commander reassignment | Resistance supply | Player UI workflow | UI atlas | Respawn/death | Gear template filter | Vehicle cargo loop | Service guards | UI IDD repair | UI design inspiration | WASP overlay | Feature status | Source propagation | release readiness | Tooling readiness | Integration trust | AntiStack DB | Owner decisions | Shelved registry | Abandoned feature revival | Hardening roadmap | PVF dispatch | Server authority | ICBM authority | Attack-wave authority | Telemetry families | AICOM V2 cutover | Consumer port map | Testing workflow | Server ops | Web tools | Ecosystem repos | Arma 2 OA refs | A2 traps | OA compatibility audit | Coverage ledger | Navigation inventory | Pruning ledger | Knowledge roadmap | Agent context | Collab protocol | Worklog | Audit archive 2026-07 | Briefing reference | Utes invasion concept
- Shelved AICOM concepts - revivable someday ideas (owner-shelved 2026-07-03)
Docs rule: source-backed claims only; Arma 2 OA scripting docs only; gameplay edits start in Missions/[55-2hc]warfarev2_073v48co.chernarus.
- Getting started
- Status and coordination
- Agent context
- Agent collaboration protocol
- Agent worklog
- Agent worklog archive
- Progress dashboard
- PR cleanup and integration lab
- Shelved PR #169: gear price double-count
- Shelved PR #194: Chernarus no-trees
- Coordination board
- Codebase coverage ledger
- Bottleneck removal queue
- Current source status
- Wiki mirror reconciliation
- Navigation inventory
- Registers
- Agent orchestration
- Architecture
- Architecture overview
- Mission entrypoints and lifecycle
- Lifecycle wait chain
- Player join/disconnect and AntiStack lifecycle
- Mission parameters/localization/build inputs
- Stringtable localization key-family catalog
- Source inventory
- Content structure and maps
- Assets/config/localization/parameters
- Mission start parameters index
- Code and networking
- Gameplay systems
- Core systems index
- Gameplay systems atlas
- Commander/HQ lifecycle atlas
- Economy, towns and supply
- Economy system reference
- Balance asymmetries
- Anti-stack skill-balance mechanic
- Empty-side supply income stagnation
- Towns, camps and capture atlas
- Victory and endgame atlas
- Victory conditions reference
- Territorial victory reference
- Marker cleanup and restoration
- Marker loop engine and registries
- Map marker families content catalog
- Marker subsystem function reference
- Client marker FSM updater map
- Support specials and tactical modules
- SCUD TEL tactical munitions
- Naval HVT objectives (carriers/SCUD)
- SCUD saturation strike mechanic
- Takistan airfield FPV drone design
- Construction and CoIn systems
- Structure damage reduction & friendly-fire
- Construction logic list cleanup
- Flak tower & WDDM anchor compositions
- Resistance supply scaffold
- GUER Insurgents faction overview
- GUER Insurgents branch audit
- GUER insurgent player economy
- GUER air-defense loop (Ka-137/Mi-24)
- Upgrades and research atlas
- Supply mission architecture
- Supply mission authority cleanup
- Current supply helicopters PR1
- Respawn and death-loop lifecycle
- Vehicle theft economy pitch
- GUER tunnel network pitch
- Content, reference and catalogs
- Faction unit/vehicle roster catalog
- Auxiliary/SF/civilian unit catalog
- Gear store loadout route catalog
- Upgrade research (cross-faction)
- Gear store price and upgrade catalog
- Gear store catalog (complete, per faction)
- Defense structures catalog
- Artillery reference per faction
- AI squad team templates catalog
- Town AI lifecycle reference
- Town AI group composition catalog
- Class-skill system reference
- Player skill abilities reference
- Default gear template content catalog
- Chernarus map content reference
- Takistan map content reference
- Takistan features
- Takistan parity reference
- Takistan oilfields objective reference
- IRS IR-smoke countermeasure
- Arty module special munitions
- Zeta cargo sling-load reference
- Spawn primitive function reference
- Kill and score pipeline
- Waypoint helper function reference
- Position and proximity function reference
- Side/team state function reference
- Player AI watchdog and recovery
- AICOM stuck-recovery v2
- LoadoutManager data-model contributor guide
- Discord status bot setup and reference
- GLOBALGAMESTATS extension reference
- New player quickstart (player guide)
- Optional client mods (player guide)
- Earning funds and score (player guide)
- Vehicle service and logistics (player guide)
- Commander's handbook (player guide)
- Tactical support menu
- Paradrop player experience
- Supply missions (player guide)
- In-game briefing & Diary field manual
- Playable maps catalog
- Faction root variables reference
- Faction base structures catalog
- Counter-battery radar system
- Bank, Reserve and Artillery Radar structures
- Map ruleset model and object config
- Countermeasures module reference
- Vehicle countermeasure (flares/spoofing)
- UAV terminal and spotter system
- Artillery firing function reference
- Service Point pricing model
- Medic redeployment truck (forward spawn)
- Side-patrol runtime and convoy mechanics
- Day/night cycle and weather system
- Config lookup helper reference
- CIPHER sort utilities reference
- Modded maps status and content
- BattlEye filter setup and OA taxonomy
- Player squad/group join protocol
- AutoFlip vehicle recovery
- Engine stealth fuel toggle
- Valhalla vehicle climbing-assist
- Missile and ordnance Fired-EH reference
- Vehicle equip and rearm reference
- Array and collection utilities
- Server composition spawner reference
- Upgrade queue server loop
- Map boundaries and off-map enforcement
- Namespace/profile/diagnostic utilities
- Group bool getVariable A2-OA trap
- Vehicle weapon balance init
- View distance auto-throttle
- Camp & respawn-camp getters
- Performance audit writer
- Site clearance (bulldozer)
- Factory queue cancel & refund
- AI commander tunable constants
- Experimental feature-flag constants
- Flag system quick reference
- Mission tunable constants catalog
- Gear parsing & cargo capacity
- Structure dressing function
- Paradrop delivery functions
- ICBM nuke client VFX & radiation
- Server HandleSpecial router
- LocalizeMessage chat router
- Gear buy-menu render & price functions
- Server broadcast & telemetry loops
- Per-unit client init pipeline
- Vehicle marking & texture pipeline
- Defense category & budget
- Legacy AI order primitives
- Commander-team driver
- AICOM command verbs
- AICOM behavior fix taxonomy
- AI commander wildcard deck reference
- AICOM aircraft and airfield system
- Static-defense manning
- End-of-game stats screen
- AI commander execution loop
- Deployable bipod / weapon resting
- Town-economy getters
- Server-init deadspawn & airfield probe
- GUER VBIED detonate action
- Resource income-tick engine
- AI commander treasury accessors
- PVF send-helper contracts
- AICOM logging & AICOMSTAT telemetry
- AICOMSTAT v2 event census
- WASPSCALE v2 telemetry
- WASPSCALE v2-ext coverage audit
- Telemetry families reference
- Group lifecycle & entity reaping
- Batch AI spawner orchestrator
- Client funds/income HUD readout
- Server group GC & cap warning
- Town runtime tuning constants
- Client input/hotkey handler
- WASP base-repair system
- WASP DropRPG launcher/ordnance
- CoIn construction-interface client engine
- Town-capture garrison & airfield rebuild
- Map-control & minimap templates
- Client FPS & state telemetry
- Client service-proximity getters
- Airfield-exclusive roster & unit hints
- Unit-camera spectator system
- Town-garrison patrol/defense worker
- RequestTeamUpdate squad-discipline
- Arma2Warfare GPT assistant
- LoadoutManager build configs & defines
- GLOBALGAMESTATS extension logging
- Discord bot instrumented logging
- Eden/Everon & Taviana map content
- Cruise missile strike asset
- AI / HC
- AI headless and performance
- AI mods and pathfinding reference
- Headless client scaling and topology
- AI runtime/HC loop map
- Headless client init and stat loop
- HC delegation target selection
- Player AI caps and role balance
- Old WarfareBE FPS comparison
- AI commander autonomy audit
- Upstream BE 2073 AICOM delta
- Parent 2.073 divergence audit
- AI commander capture & fun plan
- AI commander B69 improvement roadmap
- AI commander B69 implementation sketches
- AICOM V2 cutover status
- Headless delegation and failover
- Commander reassignment call shape
- GUER Director living-resistance pitch
- Quality and operations
- Foundation perf findings & Tier-3 dead-ends
- Dead/stale code register
- Commander vote/reassignment
- Attack-wave authority
- Server runtime and operations
- Server ops runbook
- JIP enrollment & client data delivery (b74.2 lessons)
- Server gameplay runtime atlas
- PerformanceAuditAnalyzer
- Performance opportunity sweep
- Documentation plan
- Knowledge platform roadmap
- Wiki quality audit
- Wiki pruning and relevance ledger
- Audit findings queue (2026-06-03)
- Deep review findings
- Client UI / server-loop perf findings
- Performance gain simulation
- Self-host testing field notes
- Cleanup and work lanes
- Hardening and authority
- UI / player workflows
- Client UI, HUD and menus
- UI HUD and dialogs
- Player UI workflow map
- Client UI systems atlas
- UI IDD collision repair
- UI control class library reference
- UI theme palette and style macros
- UI design inspiration 2026-07
- Available-actions client gate FSM
- Gear/loadout/EASA atlas
- Gear template profile filter
- Vehicle cargo equip loop bounds
- Factory and purchase systems atlas
- Service menu affordability guards
- WASP overlay
- Class-skill system reference
- Skin selector and class swap
- Earplugs audio toggle
- Mission audio catalog
- HQ radio knowledge-base catalog
- QoL trio player hints
- Player vehicle/travel actions
- Tooling / release / integrations
- Tools and build workflow
- Warfare web tools
- Ecosystem & companion repos
- Zargabad tooling parity
- July 2026 release readiness
- Operator monitor and CPU affinity tools
- Tooling release readiness audit
- Source fix propagation queue
- Agent release readiness ledger
- Release source intake map
- Testing/debugging/release workflow
- Current RPT release gate
- RPT telemetry consumer port map
- External integrations
- Integration trust boundary audit
- AntiStack database extension audit
- Community & Dev
- Community & Dev
- Miksuu upstream wiki import / archive index
- Upstream changelog feature leads
- Developer history and upstream lessons
- Upstream Miksuu commit intel
- Upstream mining ledger
- Archive script mining v2
- Upstream BE 2073 AICOM delta
- Parent 2.073 divergence audit
- PR8 and Drone upstream lesson match
- Development lessons learned
- External research reports
- Audit archive 2026-07
- Briefing reference
- Utes invasion concept
- Miksuu archive: Home
- Miksuu archive: Welcome
- Miksuu archive: Big announcements
- Miksuu archive: Changelog
- Miksuu archive: Development process
- Miksuu archive: Discord bot
- Miksuu archive: Gameplay videos
- Miksuu archive: LoadoutManager
- Miksuu archive: Chernarus script architecture
- Base-game visual catalogs
- Compatibility and references
- HC upstream history and lessons
- Player stats branch audit
- BuyMenu EASA QoL branch audit
- Perf quick wins branch audit
- Commander positions branch audit
- Zargabad branch audit
- Quad AI Commander concept
- Arma 2 OA external reference guide
- Base-game config & image reference
- Arma 2 OA compatibility audit
- Arma 2 OA agent traps reference
- Arma 2 OA command versions
- Wiki source consistency
- External Arma 2 OA reference index