This repository was archived by the owner on Feb 19, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 6
Spawn Parameters
Steven Webster edited this page Dec 12, 2020
·
2 revisions
Spawn parameters are more advanced spawn conditions. They define what/who needs to be present for the class to spawn. It looks like this:
spawn_parameters:
sc_Test1_Alive: 0
role_ClassD_RangeMin: 3
role_ClassD_RangeMax: 5
team_MTF_Alive: 3- In this example, the class will only spawn if there are 0 people with the Test1 subclass, there are 3-5 (inclusive) class d alive, and exactly 3 mtf alive.
- These have defined prefixes, currently it recognizes
sc(subclass),team,players, androle(case sensitive). - Teams recognized are
SCP,MTF, andCHI. Tutorials are considered SCPs. Using any teams other than these 3 will always return 0. - Subclasses, teams, and roles require a second argument after their prefix that defines what to look for. For example: sc_SubclassName_Alive: 5 will look for subclasses with the name SubclassName and there must be 5 alive. However, players does not have this second argument, so it's just players_Alive.
- Only players has a Dead parameter. Accessed by players_Dead.
- If you define a RangeMin, you must define a RangeMax and vice versa.
- You can have any number of spawn parameters, but they must all pass for the class to be given. Enable debug to see what parameter classes are passing/failing at.
Here's some more examples:
team_MTF_Alive: 1
team_MTF_RangeMin: 2
team_MTF_RangeMax: 5
role_ClassD_Alive: 1
role_ClassD_RangeMin: 2
role_ClassD_RangeMax: 5
sc_Class_Alive: 1
sc_Class_RangeMin: 2
sc_Class_RangeMax: 5
players_Alive: 1
players_Dead: 3
players_Alive_RangeMin: 2
players_Alive_RangeMax: 4
players_Dead_RangeMin: 5
players_Dead_RangeMax: 8