element idea: command ray
-
this has probably been requested before but I will explain some possible properties in detail.
name CMDR
this will work like aray but will change properties of elements that it hits
Properties:
when sparked it produces a ray (haven't thought of a name yet)
sparked with INST it can go through any element and change its property
sparked with METL it will stop at the element it hits acn only change the property of one pixle
It can set TEMP,CTYPE,X,Y,TMP,TMP2 and any other property
setting TMP of CMDR sets what property will be changed
1=temp
2=ctype
3=tmp
4=tmp2
5=x
6=y
7= changes CDMR to flood mode- it will change all conected elements which are the same.
-------------------------------------------------------
changing the CTYPE of cmdr means that any elements that pass through it will have their properties changed.
EG: photons can have their life changed so they can fly further.
pistons can push other elements through CMDR to have their properties changed
Because one CMDR can change another CMDR's properties, many advanced things will now be able to be made.
If you can think of other things that I didn't mention please feel free to post.
Edited once by POWDER_AU_. Last: 19th May 2014 -
this can be exploited. really.
jacksonmj:
I don't think that property setting elements, or elements that run console commands, are a good idea.
1. It means that saves rely on the exact details of how elements are implemented, which makes it a lot harder to change things or tidy up the code without breaking saves.
For example: merging all life elements into one and reusing the element IDs. If an element that could set ctype had existed, any saves that used it to set clone to produce a particular life element would have been broken.
2. If you change any particle properties except through normal element interactions (e.g. by using the console or a property setting element), you do so at your own risk. The game may crash, or elements may not work as they are intended to. I try to make elements do sensible things when people clobber them with the console, but loads of them still don't behave well when fiddled with. Mostly, I haven't bothered fixing any strange effects that don't survive being saved. Console commands in saves would be opening a whole new can of worms.
If you can only make it using the console (molten stkm, frozen sing, bomb powder etc), don't be surprised if it stops working at some point in the future, and don't rely on it doing anything predictable. The only things you can expect to work in the future are things achievable through normal element interactions (and even then, changes are sometimes made if there is a good enough reason to do so).
I would prefer not to see saves relying on things that might not work in the future. People complain when things break. -
I tried to get around this problem with DRAY:
https://powdertoy.co.uk/Discussions/Thread/View.html?Thread=18688&PageNum=0#Message=267612
Since it just makes a copy of particles that have already been loaded into the simulation, the implementation doesn't make any difference to how it functions.
