Zainstaluj Steam
zaloguj się
|
język
简体中文 (chiński uproszczony)
繁體中文 (chiński tradycyjny)
日本語 (japoński)
한국어 (koreański)
ไทย (tajski)
български (bułgarski)
Čeština (czeski)
Dansk (duński)
Deutsch (niemiecki)
English (angielski)
Español – España (hiszpański)
Español – Latinoamérica (hiszpański latynoamerykański)
Ελληνικά (grecki)
Français (francuski)
Italiano (włoski)
Bahasa Indonesia (indonezyjski)
Magyar (węgierski)
Nederlands (niderlandzki)
Norsk (norweski)
Português (portugalski – Portugalia)
Português – Brasil (portugalski brazylijski)
Română (rumuński)
Русский (rosyjski)
Suomi (fiński)
Svenska (szwedzki)
Türkçe (turecki)
Tiếng Việt (wietnamski)
Українська (ukraiński)
Zgłoś problem z tłumaczeniem
I think that @Brett himself will decide who to ignore and who not and he does not need your instructions.
I have passed on my experience to author, not for you.
@Brett Maybe I'm wrong, but as soon as I disabled this mod, the problem I mentioned below disappeared...
You again mickey? Brett, please ignore him.
He shows up in every comment section and always bothering the authors.
I have already blocked him. ;p
Here example: if player you opened a mission in the editor and launched it, then when you exited the mission, you get to an empty map (without your) mission and the editor loads your mission again. Sometimes an additional (double) editor loading occurs if first the player first time tries to load a mission. This is what happens. The player has selected a ready mission, pressed "open" But instead of a mission, an empty editor will open and then the mission will load a second time.
In any case, I did not notice any super fast noticeable loading of attributes. For this reason, the mod creates more problems than solves them.