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
Add a new test origin - Nebula Guardian [not finished]
You mean, it is too big?
AAR_ap_TITAN_supremancy
I get your point, but terraforming doesn't work that way. So blacklisting is not possible.
A black list when you want all but the listed.
Usually there won't be overwritten in these area. However, many similar functions overlap and coexist, but that is beyond my control.
As for blacklisting... terraforming is peer-to-peer function, so there shouldn't be any possibility of blacklisting.
I may not understand what you mean. In your opinion, how do you implement blacklist and whitelist?