Prototype/AutoplaceControl: Difference between revisions
Jump to navigation
Jump to search
(Note 255 instance limit) |
(order already defaults to empty string in PrototypeBase) |
||
| Line 16: | Line 16: | ||
If your autoplace control is used to generate ores, you probably want this to be true. | If your autoplace control is used to generate ores, you probably want this to be true. | ||
Revision as of 12:48, 29 July 2021
Prototype definitions » PrototypeBase » Prototype/AutoplaceControl
A setting in the map creation GUI. Used by the autoplace system. Only 255 instances of this prototype may be defined.
Prototype/AutoplaceControl — autoplace-control | ||
| category | :: | string |
| can_be_disabled | :: | bool (optional) |
| richness | :: | bool (optional) |
| Inherited from PrototypeBase | ||
| name | :: | string |
| type | :: | string |
| localised_description | :: | LocalisedString (optional) |
| localised_name | :: | LocalisedString (optional) |
| order | :: | Order (optional) |
Mandatory properties
Inherits all properties from PrototypeBase.
category
Type: string
Either "resource", "terrain" or "enemy". Controls in what tab the autoplace is shown in the map generator GUI.
Optional properties
richness
Type: bool
Default: false
Sets whether this control's richness can be set by the player or not.
If your autoplace control is used to generate ores, you probably want this to be true.