I allowed people to do that sometime this year. For years before that, it would check every save for mod elements, even inside every kind of element like CLNE, STKM, PIPE. If it found one, it would give you some warnings and prevent you from hitting "publish". It was pretty cool, but in the end, annoying. With the OPS format, it doesn't matter if a save has an invalid element, so I decided to just allow people to publish the saves. The elements won't show up in tpt++ clients.
I wonder, what happens if you upload a save with Jacob1's mod that happens to have an element stock TPT doesn't have?
Press Ctrl+F. It is a very useful feature and idk how people get stuck in that mode.
Jacob1 halp I got your mod, pressed a few random buttons, and now all the elements are either gray or red.
Atomic10: CO2 is a string, so do tpt.element("co2"). Your version runs the command with the variable 'co2', which is nil, which should create this error: console:1: bad argument #1 to 'element' (string expected, got nil)
Well that works now apperently. But try to type in tpt.element(co2). Also, I forgot that you can do math in the Lua Console. It's pretty neat if I do say so myself... And I do.
@Atomic10 !set type co2 none works for me.
Hey dpes anyone know what CO2 is? I ean, more specifically, it's real name. Because I need to do !set type co2 none, but it won't work. What's its real value?
Atomic10: well, at the moment it is a beta so you can't upload saves, but once 91.0 comes out i'll definitely push my snapshots more :P. It is nice being able to control updates. Also, i'll make my mod use the starcatcher update server too probably.