How to review an AI-prepared homebrew class
Compare the imported draft with its source passages, paying particular attention to levels, uses, recovery rules and conditional effects.
Use the source references
The class importer links draft features to numbered source passages. Follow those references to compare the draft with the original wording. A feature title alone is not enough: check what it grants, when it applies and what limits it has.
Check progression and resources
Review the level at which each feature appears, choices offered at that level, and the number of uses or spell resources involved. Check whether recovery is tied to a rest or another condition.
A useful review example is a feature that can be used twice after a short rest. The name and description might look right while an incorrect recovery rule would still change how it plays. Resolve that mismatch before the character relies on it.
Separate the written rule from execution
The app can store class information without supporting every special interaction as automatic game logic. Conditional homebrew should remain explicit and reviewable. Ask the GM to decide how unresolved mechanics will be handled at the table. Full automation is a development goal; a generated draft is not proof that all its effects are implemented.
Quick steps
- Compare each feature with its cited passage.
- Check levels, choices, uses and recovery.
- Resolve ambiguous wording with the GM.
- Save only after reviewing the complete class.