WC3 Campaign Studio User Guide

This guide explains how to use the hosted Warcraft III campaign creator on OSC. The app helps you import map trigger data, design campaign structure, generate starter content, and export files you can use in your Warcraft III workflow.

Back to the app

Recommended workflow

Upload a .w3x or .w3m map archive with Import map archive.
Optionally clone a named faction sample such as Refugee Exodus or Moonwell Raid, then adjust the genre if you want a different mission flavor.
Write a short mission or campaign idea in the AI copilot box.
Use Generate campaign starter to scaffold chapters, quests, persistence keys, and optional cinematic or boss content.
If you use ChatGPT or another LLM, copy the prompt out of the app, paste it into your own subscription, and paste the returned JSON back into the app.
Validate the pasted AI response and review the diff preview to see what will be added or updated.
Refine the generated campaign data using the chapter, persistence, quest, boss, and cinematic sections.
Save the campaign project.
Export trigger files, try a patched map download if hosted patching is available, or download the full project bundle.

Feature guide

Map import

Best for most users. Upload a Warcraft III map archive and the app extracts war3map.wtg and war3map.wct automatically.

Sample project cloning

Choose a faction, a named scenario, and a mission genre such as escort, defense, boss mission, or infiltration, then clone a structured sample into a fresh project.

AI copilot brief

Use this when you want help planning a mission. It can generate an AI-ready prompt or create a starter package directly inside the project.

Bring your own LLM

Use your own ChatGPT subscription or another LLM. The app prepares the prompt, and you paste the strict JSON response back for validation, diff preview, and import.

Campaign chapters

Use chapters to represent campaign flow instead of keeping everything as isolated triggers. Add summaries, map filenames, and unlock rules.

Persistence planner

Track cross-mission state such as chapter completion, rescue counts, important boss outcomes, or story flags.

Cinematic wizard

Generates a skip-safe cinematic package with start, skip, and restore trigger templates plus safety notes.

Project bundle

Downloads a zip with campaign.json, regenerated trigger files, and your uploaded source map snapshot when available.

Dataset ingest (advanced)

The API can ingest map archives into benchmark records for parser and compatibility testing. Use it with the dataset policy and schema docs.

What to export

Trigger export: good when you only want updated war3map.wtg and war3map.wct.
Patched map: best when the server reports hosted patching is ready and you want a rebuilt .w3x or .w3m directly.
Project bundle: best when you want a portable snapshot of the campaign project plus exported trigger data.

The export section shows whether hosted map patching is ready on the current server. If it is not ready yet, use the project bundle and keep the source map snapshot for the next editing step.

Dataset benchmark ingest (advanced)

Schema: GET /api/dataset/schema
Ingest map: POST /api/dataset/ingest-map
List records: GET /api/dataset/records

Use these endpoints with the repository docs dataset-policy.md, benchmark-schema.json, and dataset-ingest-quickstart.md.

Beginner tips

Start with one chapter and one main quest.
Try a named faction sample first if you want to learn the project shape quickly.
Use persistence keys only for information you know must survive between maps.
Keep cinematics short and make them skippable.
Save before exporting.
Use the generated starter package as a draft, not as the final design.

Current limits

Hosted patched-map download depends on StormLib being available on the server. Check the export section for the current capability status.
The AI copilot currently helps with prompt generation and starter scaffolding; it is not yet a full autonomous trigger author.
Campaign package (.w3n) support is planned, not complete yet.