Установить Steam
войти
|
язык
简体中文 (упрощенный китайский)
繁體中文 (традиционный китайский)
日本語 (японский)
한국어 (корейский)
ไทย (тайский)
Български (болгарский)
Čeština (чешский)
Dansk (датский)
Deutsch (немецкий)
English (английский)
Español - España (испанский)
Español - Latinoamérica (латиноам. испанский)
Ελληνικά (греческий)
Français (французский)
Italiano (итальянский)
Bahasa Indonesia (индонезийский)
Magyar (венгерский)
Nederlands (нидерландский)
Norsk (норвежский)
Polski (польский)
Português (португальский)
Português-Brasil (бразильский португальский)
Română (румынский)
Suomi (финский)
Svenska (шведский)
Türkçe (турецкий)
Tiếng Việt (вьетнамский)
Українська (украинский)
Сообщить о проблеме с переводом
@NИNИNИ
I've tested with the mod enabled and disabled. It worked the same both ways. I tested with an explorer captain after, they discovered far more sectors as expected with and without the mod enabled.
Are you sure you're not just using a non-explorer captain? Not every captain can discover every type of sector so it can appear as if they're not doing anything even though there are visible mass sectors on radar.
My mod doesn't touch the scouting part of the scouting operation, only the function which controls the size of the area. I also tested it again anyway and it worked normally. You likely have a conflict or other issue.
You're correct, that should by a Y. I've fixed it now in the affected files. Thanks for pointing it out.
I didn't notice the issue during testing as it actually works regardless, even though it shouldn't. Basegame scripts likely ensure the values are equal to the highest/X value to keep it square. I don't remember off the top of my head though.
-- Ensures the resulting value is an odd number
X = utilities.makeOdd(X)
X = utilities.makeOdd(Y)
Shouldn't that last line assign to Y instead of X?
The mod is already updated for 2.5.2, it doesn't need an update. Try unsubbing and resubbing as Steam may not have updated your local copy of the mod yet.