Director 1
Asking for a change
You ask in the chat, Director 1 works, and the thread shows you what it did. Reading that thread well is most of the skill.
What the thread shows
While a turn runs, the message updates in place rather than appearing all at once at the end. Alongside the prose you get cards for the things Director 1 actually did, each showing "Working…" and then "Done" — or the exact failure if it did not.
Longer jobs, like generating a world from real terrain, collapse their progress into a phase log you can open. Closed, it tells you the outcome and how long it took; opened, it lists the phases.
Director 1 can also ask you a question mid-turn. Those arrive as a card in the thread, and the turn waits for your answer.
Reading the result
The result is the game, not the message. Press Play and look. If it is wrong, say what is wrong in the same chat and ask again — you are the person who decides whether it is right, and that is the loop working as intended.
Be concrete about what you saw. "The hills are too steep to walk up" is a change Director 1 can make; "make it better" is not.
When nothing looks different
Sometimes a turn genuinely succeeds, the files on disk really do change, and the running game looks exactly the same. Stage Engine tells you when that has happened rather than leaving you to wonder, because the answer is usually that the running game has not picked the change up yet.
Stop the game and start it again, and you will see the current state of your project.
When a turn fails, the thread names the error and prints the exact code it got back. That code is not decoration — it is the useful thing to quote if you need help.