Installer Steam
log på
|
sprog
简体中文 (forenklet kinesisk)
繁體中文 (traditionelt kinesisk)
日本語 (japansk)
한국어 (koreansk)
ไทย (thai)
Български (bulgarsk)
Čeština (tjekkisk)
Deutsch (tysk)
English (engelsk)
Español – España (spansk – Spanien)
Español – Latinoamérica (spansk – Latinamerika)
Ελληνικά (græsk)
Français (fransk)
Italiano (italiensk)
Bahasa indonesia (indonesisk)
Magyar (ungarsk)
Nederlands (hollandsk)
Norsk
Polski (polsk)
Português (portugisisk – Portugal)
Português – Brasil (portugisisk – Brasilien)
Română (rumænsk)
Русский (russisk)
Suomi (finsk)
Svenska (svensk)
Türkçe (tyrkisk)
Tiếng Việt (Vietnamesisk)
Українська (ukrainsk)
Rapporter et oversættelsesproblem
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 ...