SCFramework

This is the product schedule for SCFramework, published under section 3 of the terms of service. SCFramework is the engine and editor the studio builds its own games on, and parts of it are published as source.

Where you obtain a component of SCFramework under an open-source licence, that licence governs what you may do with that component, and it prevails over this schedule for it. This schedule governs everything else: the name, the marks, any binary or asset we distribute outside such a licence, and any access we give you to the engine or its documentation.

SCFramework is in development. Access given before general availability is governed by section 13 of the body as well as by this schedule, and nothing here is a promise of a general release.

SCFramework is a game engine with an editor: a runtime core, rendering, tooling and the documentation published with it. The studio's own titles are built on it, which is why a defect in the engine can affect a title and why section 15 of the body governs changes to both.

Source we publish sits in the studio's public repositories, each carrying the licence that applies to it. Reading, building or forking that source under its licence does not create an agreement with us beyond that licence.

For components published under an open-source licence, that licence is your licence, in full, including any condition it places on commercial use, on distribution and on making a modified version available over a network. We do not add conditions to it here and we do not remove any.

For anything we supply outside such a licence, including a build, an asset, a tool or documentation given to you directly, we grant a limited, non-exclusive, non-transferable and revocable licence to use it for evaluating or developing with the engine, and for no other purpose.

A commercial licence to use the engine on terms other than the published source licence exists only where we grant it in writing. Section 4 of the body places that written agreement above this schedule.

"SCFramework" and the marks associated with it are the studio's, and an open-source licence over the code is not a licence over the name. You may state factually that your work is built with SCFramework. You may not name your own product after it, use the marks in your branding, or present a fork as the official engine.

Where you contribute code or content to a repository of ours, section 9 of the body governs what you give us and what you keep, together with any contribution terms published in that repository.

Within the licence that applies to you, the engine may be used to build software of your own. It may not be used to circumvent a licence condition on a component, to remove or obscure a notice, or to present the engine or a modified version of it as something other than what it is.

You are responsible for what you build with it and for the rights in the content you put into it. Section 17 of the body applies: the engine is provided as it is, and building a product on it is your decision and your risk.

Obtaining, building or using the published source involves no processing of personal data by us. Where you contact us, open an issue in one of our repositories or are given direct access to a build, the privacy notice applies to that correspondence and to the access record.

What a game built on the engine collects from its own players is decided by whoever publishes that game, and this schedule does not make us a controller or a processor for it.

No support commitment attaches to the published source beyond what its licence says, which is ordinarily none. Where we have agreed support with you in writing, that agreement governs it.

The engine changes as it is developed, and section 15 of the body governs those changes. Access we grant directly may be withdrawn under section 16 of the body; a licence you already hold over published source is not withdrawn by that, because it is the source licence and not this schedule that grants it.

Section 4 of the body sets the order in which documents prevail. For SCFramework the practical result is this: the open-source licence published with a component governs that component; a commercial licence we have signed with you governs what it covers; this schedule governs the name, the marks and anything we supply outside those licences; and the body governs the rest.