These entities must be placed inside of the corresponding visgroups. For each objective ( but NOT for anti objectives!) you need a nmrih_objective_boundary entity. Anti-objective visgroups must also be named the same as their corresponding objective visgroup.ġ. All anti-objective visgroups must be children to one main visgroup named 'anti', which must be a child to the visgroup 'Objectives'. All objective visgroups must be children to one main visgroup named 'Objectives'. The entities inside of the Objective visgroups for 'roll_barrel' and 'extinguish_fire' would NOT spawn.īecause Hammer likes to remove empty visgroups, initial setup of them is futile this section will simply discuss the required layout of the visgroups. Entities inside of the objective visgroups will only spawn if their objective is chosen for a round.Įxample: Using the graph below, if one round is 'insert_batteries', 'disable_electricity', 'close_shutter', 'Extraction', then all entities inside of the Anti-Objective visgroups for 'roll_barrel' and 'extinguish_fire' would spawn. Inside these visgroups will be all entities associated with that objective. Objectives and Anti-Objectives are defined as visgroups inside of Hammer. Note: Advanced hammer knowledge is required to setup an objectives system.Īs a quick overview, objectives are split into both ' objectives' and ' anti-objectives.' Because the objective path for any given round is randomly selected, the 'anti' objectives are used when the corresponding 'objective' is not chosen for a given round.

No more room in hell objective maps