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
They already said that the whole procedure is proofing to be mire difficult than they thought it would, so there can be a chance that they cancel it if it consumes to much time and ressources.
If another avenue is more effective, I support that.
The host migration currently in the game is useless. I may as well quit the game and start a new lobby or join another group.
Ideally, host migration/progression should in theory reset the horde timer on short cooldown. Such as if a host dc's during a horde, the client holds the next wave in a buffer for when a new host is picked.
Nothing but a dedicated server machine can.
This is the main issue I have with the whole "dedicated servers" thing honestly. I don't really care how they fix the connection issues whether it's host migration, dedicated servers, or something completely different, I just find it obnoxious that said fix has been "coming soon" since release like 9 months ago.