Serious Editor 1 Entity Documentation

A comprehensive documentation about every entity provided with the classic Serious Sam games.

This page seeks to document every available entity within Serious Editor 1. Information about these entities have been compiled through empirical testing, entity source code, tutorials found online and from the many contributions to Serious Site about this topic. Thanks to any contributor on Serious Site, Discord, the older tutorials from back in the day or anywhere else. Special thanks go out to HoBu4ok and Art-Serious.

last edit: 08/08/25

---

---

Common Properties

Some properties are shared between entities and mostly serve the same purpose. These are linked to and listed here. Any functional deviation is documented on a per-entity basis.

Event Types

Spawn Flags

Basic Entities

WorldBase

Video guide by Rakanishu.

World geometry. Each time a new brush is created through CSG mode ▬ and joined (shortcut 'l') as new layer (not added to existing WorldBase), a new WorldBase entity is created. Other than being used to build a level's geometry, it also controls zoning (sectors ▬), gravity and visual effects like fog and haze.

Properties:

---

WorldLink

Video guide by Rakanishu.

Used to change levels.

Properties:

---

GradientMarker

Guide by JesterOfDestiny (see Gradient markers section).

"This entity allows you to make seamless transitions between two states of light, within a single brush. For example, you have a corridor leading into an outside section, which is illuminated by a directional light. You could add some lights into the corridor, but it’s just going to light up the already directionally lit polygons as well, ruining the transition. Enter the gradient marker, which will give you a perfect transition."
- JesterOfDestiny

The given colors are divided at the center of the entity and spread over a brush in both directions, so placement of the entity matters. For the marker to work, it will need to be selected for one of a given WorldBase entity's "Gradient" properties and in polygon-mode ▬ under "Shadow -> Gradient".

Properties:

---

BackgroundViewer

Background guide by Zadeon.

Needs to be present within any world which should show a skybox. Dragging and dropping any "preset" from the "Backgrounds" category of the virtual tree comes with a properly set up brush and BackgroundViewer, so creating backgrounds with the BackgroundViewer is only interesting to those who wish to build their own skyboxes.

Properties:

---

Light

Comprehensive guide by JesterOfDestiny.

Properties:

Types:

Lens flare types:

---

PlayerMarker

Checkpoints tutorial by Rakanishu.

Defines the level's starting and/or respawn positions for players. Otherwise they spawn at the world origin (0, 0, 0) or respawn their location of death.
Each colored tile on the marker, labeled P01-P16, marks the position of each player in co-op sessions. The centered blue square is the player's position for singleplayer mode.

Properties:

Weapon codes:

---

ModelHolder2

Used to display imported 3D models (.mdl format through SeriousModeler). Allows custom rendering properties for the model, from lighting to LOD and destruction.

Properties:

---

ModelDestruction

Destructible wall guide by Zadeon.

Destruction data for models that can be destroyed by damage.

Properties:

Particle types:

---

WorldSettingsController

Has few properties, but it's existence in the level is required for several other entities to work. They're mostly included in "preset" backgrounds.

Properties:

---

FogMarker

Renders fog per brush sector polygon ▬. Must be selected in sectors and their brush, so zoning for the affected brushes needs to be turned on. Can only be seen when in the sector.

Properties:

Attenuation types:

---

HazeMarker

Renders haze, which is very similar to fog, just a little less prominent and more diffuse. Usage is the same as FogMarker. Can be seen from a different sector if property is set.

Properties:

---

MovingBrush

Elevator guide by Zadeon.

Properties:

---

MovingBrushMarker

Used to lay paths for moving brushes to move along. Apart from brushes moving in any arbitrary form, together with the MovingBrush and the DoorController these are the basic building blocks to create doors.

Properties:

---

Bouncer

Brushes with the ability to apply force to players or enemies, pushing them in a given direction. They initially behave much like WorldBase or TouchField entities as in displaying a globe object before any brush primitive has been added to it.

Properties:

---

TouchField

TouchField guide by Zadeon.

Trigger volumes used to trigger other entities upon entering or exiting.

Properties:

---

DoorController

Door guide by Zadeon.

Trigger volumes used to trigger doors (moving brushes). Their usage differs in comparison to touch fields as they don't need brushes to be created to define their trigger volume. The volume is constructed by setting the entity's properties accordingly and their dimensions are restricted to two values. It only triggers upon entering the volume, but comes with other, more door-centric properties.

Properties:

Types:

---

MusicHolder

Music holders control peace and fight music and are also required for boss fights to work properly, and other things, like level end statistics.

Properties:
--- | --- | --- | --- | ---
Music Heavy | file | *.ogg | - | Music to play when the total score of active enemies has reached the amount specified in "Score heavy".
Music Light | file | *.ogg | M | Music to play when the total score of active enemies is below "Score medium" or score heavy (or generally when no enemies are active).
Music Medium | file | *.ogg | - | Music to play when the total score of active enemies has reached the amount specified in "Score heavy".
Parent | - | - | - | -
Score heavy | float | - | - | Threshold for the score sum of active enemies after which the music specified under "Music Heavy" should play. This is usually a very high number, depending on the overall amount of enemies and their strength (score).
Score medium | float | - | - | Threshold for the score sum of active enemies after which the music specified under "Music Medium" should play. Usually as low as 100, which is the lowest amount of points an enemy can have (marsh hoppers).
Spawn flags | - | - | - | -
Volume Heavy | float | 0-4 | - | Volume for heavy music.
Volume Light | float | 0-4 | V | Volume for light music.
Volume Medium | float | 0-4 | - | Volume for medium music.

---

MusicChanger

Since only a single music holder should be placed per level, changing to different tracks apart from regular gameplay is achieved with the MusicChanger, which holds a single track to play when triggered, replacing the regular soundtrack for its duration.

Properties:

---

SoundHolder

Properties:

---

Marker

Markers don't do anything by themselves, but can be used as positional targets for other entities like Teleporters and Lightning.

Properties:

---

Trigger

With a vast array of trigger targets and individual event types, triggers can be used and chained to perform some complex logic.

Properties:

---

Switch

Switch guide by Zadeon

This entity shares all properties of the ModelHolder2 and adds a few more specific to switches. Only the differences are listed below, for the full set of properties, check ModelHolder2.

Properties:

---

Copier

Used to copy existing entities on the map. Copied entities will spawn at the center of the Copiers editor position.
The targeted entity will still be visible and remains active, so it's best to move it out of the play area. If for example an item that is targeted by the Copier is picked up, the copier will stop working, as there no longer is an item to be copied.

Properties:

---

Damager

Can be used to damage anything that is susceptible to damage, such as players, enemies and MovingBrushes.

Properties:

Damage types:

---

AnimationChanger

Can change the animation for ModelHolder2 or Light entities.

Properties:

---

AnimationHub

The hub is useful if you need to trigger animations on multiple models at once or in succession with a certain timing. Up to 10 model or light references can be set, for which technically only one AnimationChanger needs to be placed that selects the desired animation.

Properties:

---

Items

All item entities share the same following properties. Type values for each specific item can be found below.

Properties:

HealthItem

Types:

---

ArmorItem

Types:

---

WeaponItem

Types:

---

AmmoItem

Types:

---

KeyItem

TFE Types:

TSE Types:

---

MessageItem

A simple item with only one available visual: a papyrus scroll.

Properties:

---

AmmoPack

Properties:

---

Camera

Old cut scene tutorial.

Cameras can be used for one-shot cut scenes, or, in combination with CameraMarkers, more elaborate cinematics.

Properties:

---

CameraMarker

Properties:

---

EffectMarker

TFE EffectMarkers only provide technical effects, while TSE in TSE also visual effects are available.

Properties:

Effect types:

Basic effect types:

---

GravityMarker

Needs to be set up for sectors and brushes in order to work.

Properties:

Types:

---

GravityRouter

For switching between GravityMarkers. Instead of the GravityMarkers themselves, the router should be set for the affected brush and sector. The switching itself happens by triggering the individual GravityMarkers that should apply upon triggering.

Properties:

---

PlayerActionMarker

Level ending guide by Zadeon

There are several different actions to chose from, mostly involving player specific animations. Most importantly, they hold actions needed to properly end a level.

Properties:

Actions:

---

VoiceHolder

Simplified SoundHolder focusing on voice lines for the player. The sound source is the player, so if any voice lines are played during a cut scene, the further away the camera is from the player, the lower the volume of the voice line.

Properties:

---

MirrorMarker

MirrorMarkers can be seen as "render targets", showing any part of the level that is pointed to by another MirrorMarker. That is, they only work in pairs and in conjunction with brushes, their Mirror properties and the right polygon ▬ and texture settings.
The basic setup looks as follows:

• 1 MirrorMarker to be used as the mirror's face (on a polygon)
• 1 MirrorMarker as the view target, so what will be shown on the mirror's face.
• A brush with a Mirror property set to the first MirrorMarker.
• A polygon of that same brush with the following settings:
  • Polygon -> Mirror: first MirrorMarker
  • Texture Texture 1 Blend: Shade

The orientation of both markers will affect the mirrored image.
Mirrors are not recursive, meaning if the mirror target will point at the mirror itself, there will not be an endless cascade of mirrors, instead the base texture of the mirror polygon will be displayed in the mirrored image.

Properties:

---

Teleport

Similar in use to DoorControllers as in their volume is defined by only two parameters. Upon entering the volume, any entity can be teleported to a specified Marker. The usual teleport SFX and VFX will be played.

Properties:

---

WatchPlayers

A type of trigger that responds to player distances in various ways.

Properties:

---

EnemySpawner

Spawner guide by Zadeon.

Properties:

Types:

---

EnemyCounter

This entity will display a health bar at the top of the screen, similar to boss fights, indicating the remaining amount of enemies to be killed.
To reduce the number, the counter has to be triggered by any normal trigger event. So it would make sense to use enemies' "Death target" properties to trigger the counter.

There are two ways to initially display the bar:

1. Any regular trigger event will show the bar while also subtracting one point of the bar, as if an enemy had been killed. So any enemy with it's "Death target" set to the counter will show the bar after being killed.
2. The "Start event" type will trigger the bar to show without also subtracting a single unit. Useful to already display the bar before any enemies start spawning.

Properties:

---

EnemyMarker

Patrolling guide by Zadeon.

These markers are generally used to build patrol routes or give spawned enemies a direction to initially run towards before spotting the player. They are also able to override common behavioral properties of enemies upon reaching the markers.

Properties:

---

NavigationMarker

Used to guide the ExotechLarva along it's rail system.

Properties:

---

Additional Entities

DestroyableArchitecture

So Ugh-Zan III can whack stuff.

These seem similar to moving brushes as they share their destroyable properties. They are only used in TFE's The Great Pyramid, for Ugh-Zan III to destroy parts of the level geometry.

DestroyableArchitecture is build with brushes to work and initially behave much like WorldBase or TouchField entities as in displaying a globe object before any brush primitive has been added to it.

Properties:

Actions:

---

DevilMarker

Special markers for a special enemy. Ugh-Zan guide by Rakanishu here.

These are like PlayerActionMarkers specifically made for Ugh-Zan III to perform various animations during his entry in The Great Pyramid.

Properties:

Actions:

---

EnvironmentBase

To make the environment more lively.

"Entities for various NPCs: birds, little animals, fish, cars in the city or star ships flying around a space station. This is [basically] a model with custom attachments that moves along markers like a MovingBrush and changes animation on the fly."
- SLAwww

Can be started and stopped via "Start environment event" and "Stop environment event" triggers.

Properties:

---

EnvironmentMarker

Making paths for environment objects.

Only used together with EnvironmentBase entities, like enemy markers for enemies.

Properties:

---

Eruptor

ModelHolder2 with benefits.

Basically a projectile emitter. This entity shares all the same properties of the ModelHolder2, but comes with additional properties to control an array of projectiles. Needs to be triggered with an "Start environment event" type trigger.

Contains all enemy attack projectiles to be used for static hazards.

Properties:

Er Types:

---

ParticlesHolder

Making sparkling effects.

Uses a given set of textures to create particle effects than can be shaped with various parameters.

Properties:

Particle types:

Particle textures:

---

Pendulum

Keep on swinging.

When triggered, the brush will swing like a pendulum based on its properties. Seen in Valley Of The Kings for the secret passage to Moon Mountains.
They initially behave much like WorldBase or MovingBrushes entities as in displaying a globe object before any brush primitive has been added to it.

Properties:

---

PyramidSpaceShip

Look, the ship from Independence Day!

This entity holds the model of the SSS Centerprice. The model itself is massive in size and occupies roughly 1800 units of width on the grid, so levels need to be sized accordingly. It will initially be invisible until it's first triggered.

For any flight path to work, a minimum of 3 PyramidSpaceShipMarkers linked together in a loop are required (similar to a Camera).

Reacts to different trigger event types in different ways:

Properties:

---

PyramidSpaceShipMarker

Like CameraMarkers, but for the space ship.

For any flight path to work, a minimum of 3 PyramidSpaceShipMarkers linked together in a loop are required (similar to a Camera). Other than that, properties work pretty similarly to CameraMarkers.

Properties:

---

RollingStone

Not the music magazine but an actual rock.

A physics enabled entity with a fixed model. Used to smash players (or enemies). Can be destroyed with weapon fire.

Properties:

---

StormController

A hub for controlling rain and lightning.

This entity has lots of Target slots for Lightning entity references. Needs to be triggered with a "Start event" for lightning effects to start. Lightnings will be randomly triggered. Does not change the background to appear cloudy. Starts rain effect but only in TFE. In TSE, an EnvironmentParticlesHolder needs to be used.

Properties:

---

Lightning

For background effects or environmental hazards.

For lightnings to work the following requirements must be met:

• A working background viewer must exist
• A WorldSettingsController must exist.
• The BackgroundViewer must reference the WorldSettingsController.

If the initial lightning's green volume cube is not extended to the target marker upon selecting, you're missing a step in the setup.
Has a delay of roughly the time of the thunder SFX before being available to trigger again.

They can be triggered individually by a regular "Trigger" event, or via a StormController.

Properties:

---

Ship

Like a MovingBrush, but different.

Similar to MovingBrushes, Ship entities move along a path determined by ShipMarkers while rocking left and right to simulate riding waves. Also comes with a set of properties to control sail animation. Can also be used for any other kind of moving object that benefits from more natural movement due to the "Acceleration" property. Moving cars can be by setting the "Rocking" properties to 0, so it will follow a straight path.

Properties:

---

ShipMarker

To get ships moving.

Similar to MovingBrushes, Ship entities need ShipMarkers to be able to move along a path.

Properties:

---

Message holder

So NETRICSA can talk to you.

Upon being triggered, players receive a new message in NETRICSA.

Properties:

---

BlendController

For blending texture layers, creating cool effects.

In order for a BlendController to work, the level must have a BackgroundViewer with a linked WorldSettingsController.
To apply any kind of blending, the desired polygon(s) need to be selected in polygon-mode ▬. The corresponding blend type must be selected under "Textures -> Blend:" and match with the BlendController's type for either texture 2 or 3.
Initially, the selected texture will be transparent. When the BlendController is triggered with an "Activate event", the texture will turn on, blending in based on the selected type. Textures with the "Activate plate" type can also be turned off using the "Deactivate event" on the corresponding BlendController. Other types of overlays cannot be turned off.

Properties:

Blend types:

TSE-only entities

AreaMarker

A bounding box for the Mordecai boss fight.

This entity has only a single use in the original games. It's a bounding box volume that's used to define Mordecai's boss fight arena. Internally it's used to retrieve info about active enemies in the area to decide whether to spawn more or less enemies.

Properties:

---

CrateBus

Brake! Brake! Braaaaaaaakeeee!

A simple entity with no collision and a fixed idle animation of the Croteam crate bus crashing into the SSS Centerprice during the intro of TSE. Cannot be killed or otherwise interacted with.

Properties:

---

CreditsHolder

Let the credits roll. Wait, they don't roll?

Must be triggered via "Start event"-type trigger. Will start displaying credits entries. Other than a PlayerActionMarker with the "StartCredits" action, this entity doesn't "scroll" the credits, but fades different text entries in and out. It also has the added benefit of being able to chose the text file for the actual credits text. Furthermore, the credits text file to be used with this entity needs to adhere to some formatting and simple syntax in order to be parsed correctly:

Line 1: CREDITS marks the beginning of the file. Must be present.
Line 3: ENTRY marks the beginning of a credit entry, which must be 3 lines. Unused lines should be left empty, but the line break must be present.
Line 4: The first two comma-separated numbers indicate the screen coordinates X and Y at which the text should be rendered. (0, 0) is the top-left corner of the screen. These are virtual coordinates and do not correspond to pixels and are thus resolution-independent. They do however depend on the text scale, so their range is not fixed. For a text scale of 1 with all three lines of text per entry, the range is roughly 0-410 vertically (Y-axis) and 0-980 horizontally (X-axis). Vertical spacing is between a full entry at scale 1 is ~80.
Line 5: The following number is a floating point number defining the overall text scale.
Line 6: CENTER is for centered text alignment. Alternatives are LEFT and RIGHT for left and right aligned text respectively.
Line 7: Medium size text. Often used as header/role/title.
Line 8: Large sized text. Mostly used for names.
Line 9: Small sized text. Mostly used for quotes or other flavor text.
Line 10: The number at the end of each ENTRY (after the 3rd line of text) is the time to display the given entry in seconds. If multiple entries are supposed to show at once, only the last entry should have this number set. All entries before should end with 0 (zero). There seems to be no technical limit on how many entries to display at once (other than available screen space).
Line 12: END marks the end of the file. Must be present.

Properties:

---

EntityStateDisplay

For modders to debug. Taken from SeriousSite.

Does not perform any game functions, but enables viewing the stack of states of any entity during the game.
This entity is useful exclusively for coders/modders, so it won’t work without additional coding. For EntityStateDisplay to work, the debug macro needs to be defined in HUD.cpp: #define ENTITY_DEBUG

During the game, the following information about the target entity is displayed at the top-left corner of the screen:

These are identifiers defined in the header file for any entity targeted. This is an example from :

Their code can be viewed in the [generated?] .cpp file. Thus, with the help of EntityStateDisplay, you can directly monitor on the go whether your entity’s state stack is working correctly. If, for example, your enemy suddenly starts getting stuck under unclear circumstances, or your vehicle gets stuck in motion, EntityStateDisplay can help understand these issues. Sometimes this is more convenient than regular debugging.

Properties:

---

EnvironmentParticlesHolder

To make weather effects or foliage.

This entity is triggered via "Start event" type trigger and will play rain and snow effects or display foliage.

Properties:

---

ExotechLarvaBattery

Provides our favorite boss enemy with additional health.

The batteries only work together with the ExotechLarvaCharger as they provide no means to trigger other entites on their own. It uses hard-coded models (with attachments) and sound: WallCharger.mdl, Beam.mdl, PlasmaBeam.mdl, Electricity.mdl and WallChargerShutdown.wav.

Properties:

---

ExotechLarvaCharger

Batteries not included.

The charger only works together with ExotechLarvaBatteries as it provides no means to trigger other entites on its own. It uses hard-coded models (with attachments) and sound: FloorCharger.mdl, Beam.mdl, Electricity.mdl, FloorChargerHum.wav and FloorChargerShutdown.wav.

Properties:

---

HudPicHolder

Display any (animated) image anywhere on screen. Images will render behind UI elements.

Properties:

---

PhotoAlbum

For all the good memories.

Book from the intro to TSE which will flip through a total of 8 pages. Must be triggered with a "Start event"-type trigger. The model and textures for each page is hard-coded. Textures used are ModelsMP\\CutSequences\\Book\\Page01.tex, through ModelsMP\\CutSequences\\Book\\Page07.tex,, with the 5th being ModelsMP\\CutSequences\\Book\\PageJoke.tex

Properties:

---

PowerUpItem

"Serious Damaaageeee!" (I hope you've heard that SS2 jingle in your head just now)

Types:

---

ScrollHolder

Let the credits roll. This time for real.

Must be triggered via "Start event"-type trigger. Will start displaying credits entries. Other than a CreditsHolder this entity doesn't utilize a certain syntax. It simply scrolls text, like credits, from a given text file with each line being centered on screen.

Properties:

---

Shooter

For more environmental hazards. Or clever scripted scenes.

This entity inherits the ModelHolder's properties. Used to shoot different kinds of projectiles. Can be triggered for each shot with a regular trigger event, or set to shoot continuously in intervals when triggered with an "Activate event"-type trigger.

Properties:

Projectile types:

---

TacticsChanger

To switch things up a little.

This entity allows changing of parameter for a given TacticsHolder at any time.

Properties:

---

TacticsHolder

To guide the enemy just a little.

This entity allows changing of the trajectory along which enemies will approach the player.
A TacticsHolder must be set for the "Tactics Holder" property either for enemies directly, or EnemySpawners. There are three ways to trigger the TacticsHolder:

1. Directly via a regular trigger event to the TacticsHolder.
2. Via "Tactics start on sense" property of enemy entities. For this to work, also the "Blind" and "Sense range" properties need to be set. With this, tactics will be activated as soon as the enemy is within "Sense range" of the player.
3. Via "Tactics autostart" property of an EnemySpawne., With this, tactics will be activated as soon as the enemy is spawned.

Properties:

Types:

---

TextFXHolder

For simple text display.

Used to display text at the center of the screen. Must be triggered with a "Start event"-type trigger to show the text with the given parameters. Will not disappear until triggered with a "Stop event"-type trigger, unless the "Auto fade out time" is > -1. Text will render behind UI elements.

Properties:

---

TimeController

Bullet time!

Used to slow down or speed up the in-game time. Does not effect any sound effects or music. Must be triggered via "Start event"-type trigger.

Properties:

---

SummonerMarker

For Mordekai's teleports.

Used for Summoner teleport targets. Required for the Summoner to work at all.

Properties:

---

Enemies

Enemy base

This is what it's all about.

Most enemies share the same set of properties, which are listed here. Enemy properties specific to their type will be listed under their own entries.

Properties:

Headman (Beheaded)

AAAAAAAAAAAAA

Uses the "Type" property.

---

Eyeman (Gnaar)

It's all fun and games until somebody loses an eye.

Uses the "Character" property.

Types:

---

Boneman (Kleer)

Please make it stop.

No special properties.

---

Werebull

Moo.

No special properties.

---

Scorpman (Arachnoids)

Screetch.

Uses the "Type" property.

---

Walker (Biomechs)

Here comes trouble!

Uses the "Character" property.

---

Woman (Harpy)

Hear me out...

Types:

---

Beast (Reptiloids)

You're a big one, ain't cha?

Special property:

Uses the "Character" property.

---

Elemental (Lava Golem)

Is it just me, or is it hot in here?

Special properties:

Uses the "Character" property.

---

Gizmo (Marsh Hopper)

Eww, now I got slime all over me.

No special properties.

---

Fish (Reeban)

Bzzzt.

Special properties:

Types:

---

Devil (Ugh-Zan III)

It ain't the size that matters.

Special properties:

---

BigHead

Croteam owns.

The BigHeads from the secrets in both TFE and TSE as well as the intro to TSE. They're passive and won't attack. They follow the player to play their voice line set under "Name sound" and will then either stop or follow any markers they were set on.

Special properties:

---

CrateRider

Look at that moron. He really pressed the button.

The BigHeads on a crate carriage from The Sacred Yards in TFE. They're passive and won't attack while slowly following the player.

Special properties:

---

TSE-only enemies

AirElemental (Kukulkán the Wind God)

"My flaming fists of fury will destroy you, fiend!"

Needs to triggered with a regular trigger event to play his "raise" animation and engange the player.

Special properties:

---

Grunt (Zorg Mercenary)

Try hitting them with a single flamethrower blast.

Uses the "Type" property.

---

CannonRotating

Special properties:

---

CannonStatic

Special properties:

---

ChainSawFreak (Cucurbito)

A Kleer's best friend.

No special properties.

---

ExotechLarva

Die when I kill you!

Only moves along a grid set up via NavigationMarkers. If no grid has been set up, but as least the first grid marker for the Larva to function at all, it will simply move to the single marker and stay in place. Does not need batteries to function, but requires a charger.

Special properties:

---

Guffy (Zumb'ul)

Oink oink.

No special properties.

---

Demon (Fiendian Reptiloid Demon)

The "Sniper Reptiloid".

No special properties.

---

Summoner (Mordekai)

Mordekai Tutorial by Rakanishu here.

Only

Special properties:

---

Santa

Ho ho ho!

Used for the Santa secret in Village of the Damned (TSE). If no Markers are used, he will follow the player but without attacking. Does not have a death animation and will run in place for a few seconds before fading out if not manually disabled when killed.

Drops a range of up to 5 items when hit. The drop chance is random and it's not guaranteed that every type of item will be dropped. Item drops depend solely on being hit, not actual damage done.

Special properties:

---

Addendum

'Name' and 'Parent' properties - Clones

All entities having the same exact name, regardless of their class, are considered 'clones'. In combination with utilizing the 'Parent' property of entities, using the "Update clones" function of the editor (Ctrl + Shift + U) can save a lot of time.

Example:
A (non-zoning) column brush is copied multiple times in a level, sharing the same name. At a later point in time, a torch model is added to the column. The colum is set as 'Parent' property for the torch. Now, instead of repeating this process for all other columns, simply invoke the "Update clones" function, and all other columns will have a torch attached.

This works with any amount of entities that employ a parent-child hierarchy.

NETRICSA Message Structure

Text files for NETRICSA messages must follow the structure below. The IMAGE is optional. Double quotes (") are displayed as well, here they're just used as highlight.

They should be placed in the following directories, depending on which tab they should show in NETRICSA (replace "DataMP" with "Data" for TFE):

• DataMP\Messages\Background - the message will appear in the Strategic data category.
• DataMP\Messages\Information - the message will appear in the Tactical data category.
  To create messages about new enemies and weapons, the Enemies and Weapons folders should be used respectively.