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.