Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
(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.