"privileges" container
From TrainzOnline
(Difference between revisions)
Jamesmoody (Talk | contribs) m |
m (added is-payware-content tag) |
||
| Line 10: | Line 10: | ||
permit-edit 1 | permit-edit 1 | ||
permit-listing 1 | permit-listing 1 | ||
| + | is-payware-content 0 | ||
} | } | ||
| Line 26: | Line 27: | ||
:Desc: Controls whether the asset shows in in-game listings. The asset will always show in [[Content Manager]] listings, regardless of this setting. | :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== | ==Example privileges container== | ||
Revision as of 05:27, 18 April 2013
The privileges container is a top-level config.txt file entry used by KIND TrainzBaseSpec and all derived assets.
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
