6.2Scope: what an edition contains

Include and exclude rules decide what is materialized. Content outside the scope never reaches a workspace or a build machine.

Section 2 of 4 in this chapter

Scope is a list of path rules on the edition. A demo starts denying everything and you add what belongs in it; a platform edition starts allowing everything and you exclude what must not ship there.

A demo's scope: the first level, the shared systems, nothing else

+ Content/Maps/Tutorial/
+ Content/Characters/Hero/
+ Content/Core/
+ Config/

everything else is denied by default

This is the difference between a feature and a guarantee. A UI filter can be got around; content that was never transferred cannot leak from a build machine, cannot be found in a shipped package by someone with a hex editor, and cannot be pulled by a contractor who only works on the demo.

Restricted editions

A console or NDA edition can be restricted to named members. Access is enforced on the server for every path that can reach it — the board, the API, manifests, releases, every branch parameter — rather than by hiding things in the interface.

A denial answers exactly the same 404 as an edition that does not exist. That is deliberate: a 403 tells you there is something there to be denied, and "which unannounced platforms is this studio working on" is precisely the question the restriction exists to refuse.

Was this helpful?