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









Any chance of an update for the corner LCDs?
Good luck with the script-renovation, flexibilty and ease of use should be the hallmark of scrips that has such outwards simplicity as this one, keep it up.
I still plan on doing some minor changes to the script, maybe add in a group option for those that like using groups, but I will make it so the tag goes inside the custom data block instead of filling the blocks name.
Have a small planet miner that I need to know when to stop mining with before it crashes and burns, since the thrusters can't hold it up with even the drills loaded. Worked like a charm before, but now it throws an exception as it can't type cast 'Sandbox.Game.Weapons.MyShipDrill" to 'Sandbox.ModAPI.Ingame.IMyCargoContainer', anything I can do? Can't really cram a container in there, it's really compact.
Also, not too keen on the renaming everything to 'cargo ore' and what not, like to have more helpful 'induvidual' names for containers. Block Groups always seemed like a more flexible way to tell scrips what they can fiddle with.