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
On a horde night the Z's always know where you are, there is no 'aggro' they just try and reach you anyway possible, and begin destroying stuff if they can't, unless you have constructed some kind of hamster wheel for them.
I'm not even sure if the assassin stealth armour will work.
The main change with this expermental build is that the horde is all night now, they'll keep comming until 3/4 in the morning.
I have seen the same behaviour, just didn't think it was a bug
Correct. When you die during a BM night, the horde temporarily suspends, allowing you to get your body and gear back. If you are spotted by -any- zed at this time, the horde resumes. If you manage to your gear and remain unseen until the morning, essentially "waiting it out" then you're safe.
The game code checks when a horde starts, and when it stops. That's it. It'll track your kills for that session so that the horde eventually turns into a trickle until it's over, but the moment you log out and back in, the game checks the time to see if the event is still active. Sees "yes, it is" and restarts. New connection, new session, new horde.
You may see it as a problem, but others see it as exp and loot farming. Both aspects are by design though.