Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
- Ahead and Behind probably use very similar placement methods and having bots spawn right next to you isn't very fun to deal with
- Anywhere, I have no idea but is probably going to fall under the same issue as the above two
~right around/next to the traincar near the front
~near the front upgrade station
~either in the tunnel bombpath or on the elevated platform right before the tunnel
~spawnbot_high if all else fails
It also seemingly spawns in these locations at random, regardless of where players are
I'm also fairly certain these where values do not work properly at all in WaveSpawn populators, only Mission and old populators like PeriodicSpawn
EDIT:
I might know how Behind is done at least. Hell-met mentioned last night that Behind is based on spy teleport spots. It still seems pretty inconsistent for a spy teleport spot, but it would explain why behind tends to spawn things much closer to players on smaller maps.
Nav Areas are collected from the given spawn point name, as long a robot can walk there, or drop down (18 HU max up, 100 HU max down)
If using AnyWhere attribute, then a random nav area will be picked from the list of nav areas collected.
If using Behind then it picks a random nav area at the end of the list of nav areas collected.
If using Ahead then it picks a random nav area at the beginning of the list of nav areas collected.
And if not using any attribute it takes the first nav area collected (so usually the nav area right under the spawn point entity)
Note: There's also other conditions for which nav areas get picked or not, but it's not really that relevant.
As it turns out, the old and crusty where values work pretty well with old and crusty populators. While this does run the risk of hitting the bot limit, a long enough interval should be fine. Since this will continually attempt to spawn, and has no DesiredCount/SpawnCount to worry about, this should be considerably more consistent (also these can actually grab bomb).
If only PeriodicSpawn had wave limits. I could see this being useful for 666 or a mission with bots across every wave.
EDIT: if Behind dies it will occasionally spawn bots in the tank spawn as well