Written in by More Playables production team
Playable Ad Masters, Variants, and Exports Explained
A concrete vocabulary for scoping creative work, controlled changes, packaging, and QA without double-counting.
More Playables commercial model
Updated
Master
A master is one original playable concept with a new interaction flow or substantial implementation work. It establishes the supported states, asset structure, responsive behavior, CTA integration, and variation points. The accepted master becomes the reference for later decisions.
Variant
A variant is a controlled change to an accepted supported master. It may change art, hook, timing, difficulty, reward, copy, or CTA when the implementation can support that change without replacing the core mechanic. Every variant should state exactly what changed.
Export
An export is the same accepted creative packaged and checked for a named destination. It can have a different archive, integration, or technical treatment. If the player experience materially changes, call the result a variant rather than hiding creative work inside packaging.
Worked order
Requested item | Count | Reason |
|---|---|---|
Drag-and-sort concept | 1 master | New core interaction and state flow |
Two opening-copy treatments | 2 variants | Controlled copy changes |
Two difficulty settings | 2 variants | Supported tuning changes |
Two reward treatments | 2 variants | Supported visual/feedback changes |
Unity and a named Google HTML5 route for the accepted seven creatives | Exports to scope | Each creative/package pairing needs the appropriate packaging and checks |
This worked order is illustrative, not a current package or quote. It counts one master and six controlled variants; the written proposal would name the network and language packages needed for each accepted creative. A variant is not automatically delivered to every destination outside the agreed scope.
When a variant becomes a master
- The core player action changes.
- A new sequence of states or level system is introduced.
- The source architecture cannot support the request safely.
- The asset and animation work becomes a distinct production.
- The creative promise changes enough that review must restart at interaction design.
Revision is another dimension
A revision corrects or improves an agreed item within the accepted brief. It does not create a permanent right to change the objective, mechanic, asset plan, language set, or delivery set. Record the revision against the master or variant it changes.
Package manifest
- Creative and version identifier.
- Master or parent master.
- Declared change for variants.
- Network/product, language, orientation, file name, size, and checksum.
- Source revision, build date, QA receipt, and known limitations.
Use the scoping worksheet to turn a loose request into a countable order.
Sources
Put this into practice
- Build and variants
See the production stage and scope boundaries.
- Scoping worksheet
Count proposed outputs before estimating.
Make your next test playable
Turn a creative question into a scoped playable, variant set, and delivery plan.
Start a playable brief