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 do not know about a pull-request page however there is a forum that is linked in the top right of the Avorion.net page.
The forums themselves can be found at forum.avorion.net
Hope that helps!
Do you know anyplace I could fill a pullrequest ar a real bug report?
I don't even see any forum link on official website...
This could help them by saving them the work time needed to develop a fix and instead they only need to implement it!
local richAsteroids = sector:getNumEntitiesByComponent(ComponentType.MineableMaterial)
with this:
local richAsteroids = 0
local asteroids = {sector:getEntitiesByComponent(ComponentType.MineableMaterial)}
for i, asteroid in ipairs(asteroids) do
if asteroid.isAsteroid then
richAsteroids = richAsteroids + 1
end
end
Because sector:getNumEntitiesByComponent(ComponentType.MineableMaterial) can (and will) also count wreckages as they have MinableMaterial Component.
My fix just also checks if the thing returned by component search is actually an asteroid.
And yep, it indeed is a stupid kind of bug, probably stemming from the thing that game did not have minable wrecks in very early development and then dev forgot that this script uses this method.