Property Converter
-
Resurecting an old idea with a better suggestion. Basically a type of non-powered convert that changes only the properties of touching elements.
Stats:
Name: PRPC
Color: FF6600
Code:
Rules of function:
-spawns with all variables at 0 and no ctype
-will change any or all properties of any element that is directly adjacent
-cannot recieve any interaction or properties from other elements (indestructable)
-cannot be cloned or used by CRAY (unless you set it's ctype to itself)
-each pixal functions independantly
-can be moved by piston
EDIT: Can be changed with console or property edit tool.
Rules in application:
-adjacent pixals will not affect each other
-if it touchs an element when it has no ctype then that element will be unaffected (erasing and replacing ctypes instantly could crash the game, so no erasing)
-if it's life is set to 0 it will ignite flammable elements and detonate explosives
-passes heat or cold instantly (1 frame heat transfer, will continuously transfer heat)
-if it is cloned by setting it's ctype to itself the new pixals will stay blank until manually set
-
how about some type of Property ray (PRAY? ... or something better like ERAY (in boxmein's mod)). Instead of changing nearby particles it would shoot out a ray of property edits. I'm just trying to figure out what's more useful here. Something like this would be nice, although I think it was rejected for some reason ... (like properties don't have to stay consistent between versions)
-
Maybe, but I also want a non-powered element too.
-
I wrote a preliminary version of ERAY which could only shoot one property at a time (which I found reasonable enough), but controlling it was a thing of memory. (Selecting which property to edit was via ctype which I arbitrarily selected)
Then I went on to try and make ERAY which could set multiple properties at once. I succeeded thus far, (First particle to be touched is completely copied to an internal Element object, then the ray shot will set ALL properties of that element to the receiving end). It had three fundamental flaws:
1. Still can't pick which properties to copy
2. Is super annoying to control. (First particle must be copied, careful unpausing, ...)
3. Can't change properties after it has initialized
I set off trying to make an user interface for it......
and that's where I straddled off. I felt uneasy by the complexity.
Someone make me an user interface and I'll slap on his name to everywhere around it.
http://github.com/boxmein/The-Powder-Toy/tree/new-eray/ -
No, I absolutly utterly reject. NEIN!! NEIN!! NEIN!! NEIN!! Your ERAY is crap. NO!
No Boxmein...I don't like that at all. -
O.K. Thread CPR. I still really want this, but you guys butchered my suggestion. This is an element suggestion for the official version. No mod elements please unless they follow my suggestion. And no, no "User Interfaces" @_@. It's called the console. -_-
-
@cyberdragon (View Post)
@cyberdragon (View Post)
Stop being a twat. Someone actually wrote something you needed and then you just barf in his face.
The user interface was for making a single pixel of that element set more than one property at once.
And it's not your element, it's mine. You have no say in what goes and what doesn't.
As for `it's called the console` - one can obviously do that in the console but not in a single line. -
@boxmein (View Post)
although he didn't have to say it like that (that's just what cyberdragon does ...), I think neither of these ideas will work. We don't need to go through the trouble of making a user interface, when we can just use PROP's. Something that can only set one property at a time would be much easier for everyone then remembering how to set it with the console, or some weird pausing / creating an element in exactly the right spot thing. You would just click on the element with PROP, it brings up the normal menu, and that decides which properties it now sets. If it was a ray you could just put multiple of the element behind each other, if it was something like this where just nearby particles get the property, then you could just put multiple ones near each other ... (also the only way to set properties of this element would be completely manually, with the console. Other property converters or PROP would not change things like type/life directly)
I think a ray might be better since people are very good with that kind of stuff, but just a property converter would also work well ... (maybe both? I'm not sure)
But then, i'm not sure what the other devs think of this / if they even want it. This opens up a lot of possibilities, good and bad (glitches)
