"privileges" container
From TrainzOnline
(Difference between revisions)
(→Example privileges container) |
(→Supported Tags) |
||
| Line 13: | Line 13: | ||
} | } | ||
| − | It should be noted that this container only takes effect when content is packaged for distribution with Trainz or an official Trainz addon pack. | + | It should be noted that, with the exception of permit-listing, this container only takes effect when content is packaged for distribution with Trainz or an official Trainz addon pack. |
====permit-commit==== | ====permit-commit==== | ||
Revision as of 09:39, 21 January 2014
The privileges container is a top-level config.txt file entry used by KIND TrainzBaseSpec and all derived assets. It is part of the new DRM built into Trainz 2012.
Contents |
Supported Tags
The privileges container supports the following tags. Each tag is show here with its default value.
privileges
{
permit-commit 1
permit-edit 1
permit-listing 1
is-payware-content 0
}
It should be noted that, with the exception of permit-listing, this container only takes effect when content is packaged for distribution with Trainz or an official Trainz addon pack.
permit-commit
- Type: Boolean
- Desc: Controls whether local modifications to this asset can be committed. Note: base assets can never have modifications committed in order to prevent corruption of the core program.
permit-edit
- Type: Boolean
- Desc: Controls whether a user may open this asset for editing. This is mainly used to prevent simple viewing of content which resides in archive files, where the content creator wishes to protect their techniques against prying eyes.
permit-listing
- Type: Boolean
- Desc: Controls whether the asset shows in in-game listings. The asset will always show in Content Manager listings, regardless of this setting.
is-payware-content
TBD
Example privileges container
TBD
