@ -22,15 +22,6 @@ All books have been converted into .md files. Use those whenever possible, but
- Do NOT invent rules. If you cannot find a rule, say so and suggest a fair houserule.
- Whenever a skill check, attack roll, etc. is required from the players, always provide the DC needed to pass. If no DC is provided by the adventure or the rules, create one yourself and provide that, explaining that you created your own DC.
## Dice Rolling
Dice rolls will be passed to you as JSON data from Foundry VTT. Use the following documentation to figure out what the roll was:
- [Foundry ChatMessage API](https://foundryvtt.com/api/classes/foundry.documents.ChatMessage.html). Use it and the topics within to for rules on how Foundry works in general. This relates to how Foundry works, regardless of game rules system it's running. It might be helpful, but it's not as useful as the next link.
- [Pf2e Foundry VTT Game System source code](https://github.com/foundryvtt/pf2e). This is the source code for the Pathfinder game system on Foundry VTT. Use it to figure out what the data means in relationship to the Pathfinder game system specifically (as opposed to Foundry VTT in general). This will most likely be more useful than the previous link.
Log every roll to `rolls.md` with a timestamp, description, formula, and result.
## Tracking Files — Update Rules
You MUST keep these files up to date. Write updates after every meaningful event, not at the end of the session.
