Creates an entity that continually rotates. Can be toggled on and off if targeted.

A rotating entity is setup exactly like a rotating door, in terms of the relation between "target"s and "targetname"s. The difference lies in the use of the "rotate" key, as opposed to the "angles" key for the rotating door.

"deathtype" "rotate" "target" "speed"

if set with a string, this is the message that will appear when a player is killed by the train. is the rate to rotate (xz xy yz) is the center of rotation is how long the entity takes to go from standing still to full speed and vice-versa

toggle start_on

allows the rotation to be toggled on/off whether the entity is spinning when spawned. If TOGGLE is 0, entity can be turned on, but not off

func_rotate_door, func_rotate_train, func_movewall, rotate_object, info_rotate

Much like a func_train or a func_train2, with the added ability to rotate, and uses path_rotates instead of path_corners.

A rotating train is setup the same way the other rotating entites are set up. However, the placement of the func_rotate_train entity determines how it will align to the path_rotate entities. When setting up the path_rotate path, keep in mind that the train will position itself with the func_rotate_train in the same position as the path_rotate. If the train is the target of a button or trigger, it will not begin moving until activated. The func_rotate_train entity is the center of rotation of all objects targeted by it. There is more information about rotating trains in the log for the 03/23/97 WCU class.

"path" "deathtype" "speed" "dmg"

specifies the first path_rotate and is the starting position. if set with a string, this is the message that will appear when a player speed of train. default 100. damage to player when blocking train. default 0.

func_rotate_door, func_rotate_entity, func_movewall, rotate_object, info_rotate, standard func_train, func_train2, path_rotate

func_rubble func_rubble1 func_rubble2 func_rubble3

Spawns random sized rubble when triggered. Spawns small sized rubble when triggered. Spawns medium sized rubble when triggered. Spawns large sized rubble when triggered.

"count"  is the number of pieces of rubble to spawn. Default is 1.

file: hipquake.zip

This will spawn a thing upon being used. The thing that is spawned depends upon the value of "spawnfunction". func_spawn_small is a smaller version of func_spawn, functionally the same.

The angles, target and all flags are passed on to the spawned object. Think of it like setting up a normal entity. Once the spawn entity is set up, it must be triggered to activate it. If "spawnfunction" is unspecified a random monster is chosen as follows:

"spawnclassname" "spawnfunction" "spawnsilent" "spawnmulti"

should contain the same value as "spawnfunction". classname of the object ot be spawned (ie: monster_army) set this to none 0 if you want a silent spawn. set this to 1 if you want this spawn to be reoccuring.

All flags are passed to the spawned entity, and therefore depend on what is being spawned.

Creates a invisible wall that can be toggled on and off.

"dmg"  is the amount of damage to cause when touched.

start_off: wall doesn't block until triggered.

This is a modification of the standard func_train entity. It is functionally equivalent, except that it removes a slight delay that would occur after each path entry, and it adds a speed variable to the path_corner entity. There is more info about func_train2 use in the 04/06/97 WCU map/bsp.

A func_train2 is set up exactly the same as a func_train. The main differences are in the movement (which is smoother), and the added functionality of the path_corner entity.

"target" "speed" "dmg"

targets first path_corner default 200. default 0.

func_train, func_rotate_train, path_corner