安装 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(越南语)
Українська(乌克兰语)
报告翻译问题









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.