monstermaker Last edited 5 months ago2024-05-25 13:16:10 UTC

monstermaker - Point Entity

Attributes

• Name (targetname) - Property used to identify entities.
• Target on release (target) - Event to trigger when a monster is spawned.
• Monster Type (monstertype) - The entity name of the monster to be spawned (other entities with the prefix monster_ not listed below will not work here):
  • monster_alien_controller
  • monster_alien_grunt
  • monster_alien_slave
  • monster_apache
  • monster_babycrab
  • monster_barnacle
  • monster_barney
  • monster_bigmomma
  • monster_bloater
  • monster_bullchicken
  • monster_cockroach
  • monster_gargantua
  • monster_gman
  • monster_headcrab
  • monster_hevsuit_dead
  • monster_hgrunt_dead
  • monster_houndeye
  • monster_human_assassin
  • monster_human_grunt
  • monster_ichthyosaur
  • monster_leech
  • monster_miniturret
  • monster_nihilanth
  • monster_osprey
  • monster_rat
  • monster_scientist
  • monster_sentry
  • monster_snark
  • monster_tentacle
  • monster_tripmine
  • monster_turret
  • monster_zombie
• Number of monsters (monstercount) - The maximum number of entities to spawn. 0/-1 = no limit.
• Frequency (delay) - Delay, in seconds, between each monster being spawned. If 0, a new monster will only be spawned after the previous has been killed.
• Max live children (m_imaxlivechildren) - Maximum number of live children allowed at one time. Spawnings will be suspended until a monster dies. A value of 0 means infinite (obviously not recommended if delay is too low and monstercount is infinite).
• Childrens' Name (netname)

Flags

• Start On (1)
• Cyclic (4) - If this is enabled, the entity will activate then deactivate (spawning a single monster) instead of toggling it On/Off when triggered.
• Monsterclip (8) - If this is enabled, spawned monsters will not be able to pass through func_monsterclip brushes.

Notes

• The Flags mechanism for this entity is doped:
  • If targetname is blank, it will spawn the monster, no matter if "Start On" is enabled or not.
  • If targetname is named and "Start On" is enabled, the monster will not spawn as soon as the game starts. However, the best way to manage this entity is to give it a name for targetname and set a trigger to activate it (once if Start On is disabled, twice if enabled). Doing so, the mechanics will normalize.
• The Childrens' Name (netname) basically assigns a name to the monster spawned, that way you can target the monster with a scripted_sequence or scripted_sentence.
• Monstermaker can't spawn active monster_turret nor monster_miniturret, neither spawn a functional monster_osprey nor a properly flying monster_apache since monstermaker can't link a path entity to the target.
• Spawning will be interrupted if a monster's hitbox collides with another in-game. Tip: you can use a cycler to render a model on your map editor or insert a monster's typical entity and check its bounding box size.
• Monstermaker will not spawn entities if there is someone (player/monster) below it, 2048 units down. Tip: you can get around this by creating something solid underneath it before use, like func_wall_toggle. And then after spawning, remove/disable that solid object.
• If the amount of monsters to spawn is higher than one, monsters will have their corpse fade after death.

Related pages

• Vlatitude: Monstermaker Tutorial

Example maps