Character Creation and World Playability
A Craft System is a build foundation. The World is the playable layer. Do not add setting-specific playability metadata to the generic System merely to make a completeness checker quiet. Instead, make sure the System carries the file types and builder guidance that a World needs to finish the experience correctly.
Character creation
The Character type can carry a creationFlow, which Craft plays as a character-creation wizard. The generic flow in this System is intentionally a draft-only fallback: concept, alignment, and a narrative hook. It does not roll game-specific attributes, select a particular O.C.C., assign powers, or invent starting resources.
A finished World should replace or extend that flow with the actual creation procedure for its game and edition. The wizard should ask only questions the generator needs, use real World files as options where appropriate, and match the numeric ranges the World permits. Trace every branch from start to ending before import.
Game Start
The System includes the Game Start file type and a synthetic example, but Systems are not directly played. A World should configure at least one complete Game Start: a real starting location, playable pregenerated characters or the intended character-creation path, an opening, and opening instructions. If the World offers pregens, they must also be flagged playable in Craft's app metadata.
The Game Start's body is context; its app metadata is machine configuration. Do not confuse the two. A pretty opening file without starting-location and character metadata is not a complete start.
GM persona
The System has a neutral default GM personality so a cloned World starts from rules-accurate, agency-preserving behavior. The World should replace that with the voice and tone appropriate to the campaign. A horror game, superhero game, military game, and post-apocalyptic game should not all sound the same simply because they share the System.
Maps and prelude
Do not set a root map at the System level. A generic system has no canonical geography. A World can add a root map when spatial exploration matters and can add a prelude flow when a cinematic lobby experience is useful. Neither should be inherited as a false universal requirement.
Visibility and app metadata
Context visibility and some playability flags are app-managed. A CDF workspace does not carry every visibility choice. After building the World, apply the intended file visibility in the app: core GM instructions pinned, reference catalogs searchable, and live trackers pinned or partial as appropriate.
System examples are not a campaign
The System Test Character, test class, test rules profile, test attribute rules, test equipment, test location, and test Game Start exist to validate schemas and formulas. They must never be presented as canonical Palladium content. A polished World should remove, replace, or clearly segregate them before publication.
The World is complete when its mechanics and content compose into a real player experience. The System is complete when it gives the World builder the stable machinery and instructions required to get there without rebuilding the engine.