安裝 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(越南文)
Українська(烏克蘭文)
回報翻譯問題






local entities = {Sector():getEntitiesByType(EntityType.Wreckage)}
for _, entity in pairs(entities) do
local sphere = entity:getBoundingSphere()
local size = sphere and sphere.radius * 2 or 0
local material = entity:getLowestMineableMaterial()
local resources = 0
for a, value in pairs({entity:getMineableResources()}) do
resources = resources + value
end
if size >= 20 or resources > 10 then
table.insert(interestingEntities, entity)
end
end
end
i got rid of the if then for size and resources and its super laggy any way to not have the constraint while preserving performance?
If anyone's desperate for a legacy version until 2.0 officially releases just let me know.
I've altered the values in this line, but I don't see a change, even if I bump the numbers up to 1,000,000.
if size >= 1000000 or resources > 1000000 then
Thanks!
If you mean range, the lower rarity modules have smaller range.
Personally, I've never had trouble locating large wreckages in my strategic map. I made this mod to find the little ones!
No effect after update
什麼都看不到..
Can't see anything ...