Cài đặt Steam
Đăng nhập
|
Ngôn ngữ
简体中文 (Trung giản thể)
繁體中文 (Trung 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 (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
And then again trying to figure out how to rewrite the code to stay under 100 lines.
And after all that torture I finaly did it
my approach on this one:
one master stays home, spawns scouts and remote-controls them to their fate - and keeps track of the good path in a file. As a refinement I also added the host-names to the file to delete loops, if the scout has been there already.
The way to do that by design would be 2x1-sized hosts with a register in there you can read for linkage data. In the meantime, many EXAs die to bring you this information!