安装 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（越南语）
Українська（乌克兰语）
报告翻译问题
(in a way to make it a viable alternative to, say, a green background to take pictures in and so on without the need to use commands such as admin and fullbright, or to edit the background shading in the game files?
Like, this: White neon + Manipulator Module Red Paint = Red neon, but still glowing white
Or this: White neon + Manipulator Module Red Paint = Red neon with red glow
If you don't know, tell me to experiment this.
thanks, i'll do that right now.
That will indeed conflict. - https://starbounder.org/Modding:Materials:Mods
I strongly recommend to relocate the ID range and register the new range on that wiki page. We start with roughly 65k IDs so I can't see a reason to overlap them. It makes mods totally incompatible. Starbound won't even start and most people (who don't look at their logs) won't know why.
Upon moving the ID range, your existing blocks will turn to dirt. Still now is the best time since it will inconvenience very few people. As your subscriber count grows, it will become a bigger issue later on to move it.