The Powder Toy

nijalninja98

i have seen many threads about adding a command block to tpt, but what about a sort of CRAY that uses commands and can change the value of certain element attributes. i think it should be 0xFFC4C70F yellow (as seen in deco). to do this you might have to add a new property, one that defines what attribute and how much they are affected by this elements ray. it will use the same principles as CRAY, with tmp being how far it will go, and it will be indestructable. i hope that the only way to see it's ray will be a small streak of positive pressure following where it goes.

uses:

obviously bomb machines

the possibility of qubits

being able to give one element quickly changing properties that could be used in computers

and the list goes on

what say you? (yes i realised i put this in the wrong category)

G-LinuxorU

cray transferring its life to the elements it creates might be a thing someday.

as for your ray particle, here's a mod for it; https://github.com/boxmein/The-Powder-Toy/tree/eray/

boxmein

@nijalninja98 (View Post)
As @G-LinuxOrU pointed out swiftly, I have a similar ray element set up however it's a bit tricky to use (which never stopped portals and PIPE!)

...More about ERAY,
https://github.com/boxmein/The-Powder-Toy/tree/boxmein
also has a few changes to the UI to see which properties the element changes and what their values are.
ERAY is used by first setting its tmp value to a bit string of "which properties it copies", then copying an element by shooting with PSCN at it and then shooting with any other metal to fire off the property.

The bit string can be set by

bit.bor(elem.ERAY_TYPE_BIT, elem.ERAY_LIFE_BIT, ...)

. Alternatively adding the numbers together which were in the linked file works too.
It defaults to copying type, life and ctype.

The element is in fact copied to a separate "known element list", which can be indexed by setting tmp2 between 0 and 100 exclusively. So if ERAY's tmp is first 0, right, and then you copy an element, then everything that element embodies will be copied to the "known element list" to position 0. If you make another ERAY particle with its tmp 0 then the two ERAY particles will share the underlying element.
You can copy properties over by sparking PSCN that touches the ERAY particle.

When in Debug mode (D), one can mouse over the ERAY in boxmein/The-Powder-Toy/boxmein to view the "sub-element's" properties. There's yet no difference between which are shown and which hidden.
In boxmein/The-Powder-Toy/eray, I didn't add it because I wanted the branch to be pull-requestable.

I'll make a build when I fix my environment :(

IRAY?