Lantern Workshop

Lantern Workshop

This disposable Godot example teaches workspace setup, discussion and search without risking production data or requiring paid generation.

Prepare

For practice from a built source checkout, choose separate profile and editor preference directories before launch:

$tutorialRoot = Join-Path $env:TEMP 'PlayWeldTutorial'
$env:GAMECRAFTER_PROFILE_DIR = Join-Path $tutorialRoot 'profile'
$env:THEIA_CONFIG_DIR = Join-Path $tutorialRoot 'theia'
npm run start -w @gamecrafter/control-room

This is an example location, not an existing user profile. Choose an unused tutorial folder and a separate disposable Project parent on your machine. These variables affect new processes; they do not move a running service. See source setup.

Create Lantern Workshop, choose Godot and a disposable parent directory, then open it. Copy only docs/ and game/ contents from the checked-in example into the new Project; preserve its generated manifest and operational state. The walkthrough owns exact copy commands and screenshots.

Practice and verify

1. Read docs/DESIGN.md and inspect native files.
2. Create a Discussion Board thread about collection/reset rules; save and reopen it.
3. Choose Knowledge Index status > Reconcile and wait for indexing.
4. Search Lexical, source docs, for lantern. Inspect the docs/DESIGN.md citation.
5. With your own configured model, optionally ask a small Chat question and inspect its persisted reply. Remote requests may cost money.
6. Install the appropriate Godot executable before checking the game itself.

Screenshot captures use a temporary scripted localhost provider. Its endpoint is not reusable, and scripted answers do not demonstrate reasoning. The sample timer prompt is an instruction example, not evidence it ran. Agent submission and paid generation require deliberate configuration and review.