"privileges" container
From TrainzOnline
(Difference between revisions)
m (added is-payware-content tag) |
(+{{ORP-top}}+{{ORP-bot}}) |
||
| Line 1: | Line 1: | ||
| − | The privileges container is a top-level [[config.txt file]] entry used by [[KIND TrainzBaseSpec]] and all derived assets. | + | {{ORP-top}}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 {{wp|Digital rights management|DRM}} built into Trainz 2012. |
==Supported Tags== | ==Supported Tags== | ||
| Line 34: | Line 34: | ||
''TBD'' | ''TBD'' | ||
| − | [[Category:Config Container]] | + | [[Category:Config Container|privileges]] |
| + | {{ORP-bot|privileges}} | ||
Revision as of 01:09, 2 July 2013
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 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
