Make Chucks fit your campaign

Your party, setting, and preferences rarely change from one request to the next. Put them in your AI's project or persistent instructions so Chucks can use them without making you repeat yourself. Different chatbots use different names for this feature, but the instructions themselves can stay the same.

Save your party composition

Pin the number and level of the characters. You can also save a default XP adjustment if your party is consistently stronger or weaker than the baseline encounter rules assume.

My party is 4 PCs at level 5. They are stronger than normal, so increase the XP budget of every encounter by 15%. Use this unless I say otherwise.

Choose what an encounter includes

Chucks keeps its default encounter output short because AI-generated tactical advice, mechanical embellishments, and stat summaries can be unreliable. If you want extra material, say exactly what to add and what to leave out.

For every encounter, include short read-aloud text the Game Master can deliver when the party first sees the monsters. Keep it under three sentences. Skip stat block summaries and tactical advice.

Set the tone and setting

Save the world, mood, or recurring themes of the campaign so encounter hooks and other ideas fit the game you are already running.

This campaign takes place in the Athasian desert. Lean into scarcity, sun-blasted ruins, and morally gray factions when writing encounter hooks.

Choose a default habitat

If most of the campaign happens in one environment, save it as the default. You can always override it in an individual request.

Unless I say otherwise, treat the encounter habitat as Desert.

Combine the instructions you need

These snippets stack. Keep only the details that should apply across many conversations; put one-off monsters, locations, and story ideas in the request where they belong.