VeinholeTypeClass

TerrainType every veinhole monster in the scenario is built from.

Specification

Applies to

global rules

File

rules.ini

Section

[General]

Value

class

When omitted

none

rules.ini

[General]
VeinholeTypeClass=VEINTREE

[VEINTREE]
Name=Veinhole Tree
Image=None
Armor=None
Strength=1000
IsVeinhole=true

One setting covers every veinhole monster on the map. A monster has no type of its own: it reports this type whenever the engine asks what it is, so the section’s Strength is the monster’s maximum and current strength, and its Armor and Immune decide what damage does to it. IsVeinhole=yes on the same section is what makes the monster clickable and a legal target.

An unresolved setting faults while the map loads

This setting has no built-in value, and a monster reads its maximum strength off the type without checking what it got. A map carrying a veinhole overlay with the setting unresolved faults as the monster is created.

A named section that does not exist yields an unkillable monster

A value naming a section the rules do not contain still produces a TerrainType — one that keeps the negative maximum strength it was constructed with, because the fallback to TreeStrength only runs when the section is present. Every monster then spawns below zero strength, and damage is refused before its armor is consulted, so nothing can kill it. The read order itself is not the problem: [General] is read before the object sections, so a type first named here still reads its own section whenever one exists.

Related resources

• Veins and veinhole monstersFeature or system

See also — veins, IsVeinhole, VeinholeMonsters

Page feedback

Report an error or missing detail. The issue includes this page and revision.

Open issueSource revision 59fae722af8c