Unmeltable PSCN or NSCN
-
In 91.0, there is a new way to block ambient heat. You basically just need a lot more INSL / FRME. To see exactly how much more, press 'g' once. Each 4x4 area is one spot in the pressure grid / ambient heat grid. You'll need to put at least 8 insulators in each grid area for it to block ambient heat.
Due to some weirdness / maybe a bug, the ambient heat will actually move into the square that is blocking it, but it can't move past it. So you'll actually need to put insulators in the squares to the left and to the right of it. Really that means a minumum of 8 pixels wide. -
Why not add a way to make them unmeltable by setting their tmp2 to -1, for example? It can't be hard, as its easily done in LUA, so is it related to that rule that elements cant have different functions?
-
@DanielGalrito (View Post)
That isn't possible. There are two kinds of properties. One defines how an element acts, stuff like "pscn melts at this temperature". Then there are the per element properties, stuff like .life and .tmp that individual particles use to store state.
Even if it were possible (which it technically is with some hacks I don't want to do), I wouldn't want some obscure property to change how an element works that much.
This gives me another idea though, maybe you could turn off heat simulation? Only works in specific electronics though. I think we once contemplated a setting to make electronics more indestructible, I would be fine adding a global setting for that at some point.Edited once by jacob2. Last: 17th May 2016 -
I think its possible, instead of having "HighTemperature" and "HighTemperatureTransition", these metals could have something like
if tpt.get_property("tmp2", i) == 0 then
if tpt.get_property("temp", i) >= (melting point) thentpt.set_property("type","lava",i)
But I understand that part of "secret" properties not being that good to change how elements work.
-
@DanielGalrito (View Post)
That is the "hack I don't want to do". That moves state transitions into the update function, right now they are handled in the simulation loop before the update, using the same code for all elements.
Your method would be slightly slower and a lot harder to maintain. -
jacob2:
Thats the last thing we need. IMO, the game needs to be made as fast as it can be, not slower.
