Cài đặt Steam
đăng nhập
|
ngôn ngữ
简体中文 (Hán giản thể)
繁體中文 (Hán phồn thể)
日本語 (Nhật)
한국어 (Hàn Quốc)
ไทย (Thái)
Български (Bungari)
Čeština (CH Séc)
Dansk (Đan Mạch)
Deutsch (Đức)
English (Anh)
Español - España (Tây Ban Nha - TBN)
Español - Latinoamérica (Tây Ban Nha cho Mỹ Latin)
Ελληνικά (Hy Lạp)
Français (Pháp)
Italiano (Ý)
Bahasa Indonesia (tiếng Indonesia)
Magyar (Hungary)
Nederlands (Hà Lan)
Norsk (Na Uy)
Polski (Ba Lan)
Português (Tiếng Bồ Đào Nha - BĐN)
Português - Brasil (Bồ Đào Nha - Brazil)
Română (Rumani)
Русский (Nga)
Suomi (Phần Lan)
Svenska (Thụy Điển)
Türkçe (Thổ Nhĩ Kỳ)
Українська (Ukraine)
Báo cáo lỗi dịch thuật
These issues existed for years before EHG decided to move to 1.0 . Its not a launch load issue, its a code issue. The game only performs well with ideal connection scenarios with limited hops and consistently low latency. Consumer internet rarely meets that standard though.
The game seems to lack any code to handle these issues, glaringly evident as they frequently occur when transitioning zones or portaling. The servers should be able to keep track of players and put them where they are supposed to be once any network issue clears, not disconnect or crash the client.
Supporting and shilling for publishers and studios that implement this shameful marketing strategy of launching broken games is what needs to stop