The Powder Toy

Element:ARCP

  • DCBloodHound     2nd Feb 2012 Member 0 Permalink
    First time suggesting an element (i think)

    Name:ArayCopier
    Short:ARCP
    Uses:acts like aray but with the same properties as void and clone.

    If it's powered with PSCN and overlaps another ARCP with the same ctype then it creates an element (if both have the ctype of metl then one pixel of metl will be created where they overlapped,if they don't have the same ctype then they simply ignore each other) (like 2x aray overlapping creates solid BRAY)

    When Powered with NSCN it deleted any element with the same ctype(like when aray is powered with PSCN and it deletes all Bray)

    This idea has been lingering around in my head for a while so i wasn't sure if i should post it or not.
  • dnerd     2nd Feb 2012 Member 0 Permalink
    Very nice idea, here's a suggestion; how about the bray-like strands having the property of passing through anything that is not of their ctype. so if it came from a METL-ctype ARCP, then it would pass through all but metl. And if two brays intersect in a particle of another type, then it will replace the pixel of intersection with its ctype.
  • DCBloodHound     2nd Feb 2012 Member 0 Permalink
    Sounds good.

    dnerd:

     And if two brays intersect in a particle of another type, then it will replace the pixel of intersection with its ctype.


    How about it only does that when it's powered with INST?
  • massey101     2nd Feb 2012 Member 0 Permalink
    Wow this idea is great! @dnerd Maybe not everything. Like it shouldn't be able to pass through INSL. It would be nice if you could somehow make it be able to do lots of elements without having to change it each time. But how...
  • dnerd     2nd Feb 2012 Member 0 Permalink
    @massey101 (View Post)
    true, it should be stopped by something. probably insl. and the second thing would require like multiple ctypes or something. EDIT: or maybe tmp could be used.

    @DCBloodHound (View Post)
    how about INWR-inst can't really power things...
  • DCBloodHound     2nd Feb 2012 Member 0 Permalink
    692731View Save 692731


    See the difference between INST powered aray and normal aray?
  • DCBloodHound     2nd Feb 2012 Member 0 Permalink
    bumping this.

    Would this actually be possible to code?

    I can always go an download all the mod/coding tools and code it myself but i haven't really made a mod yet so i have no idea how the code is laid out.
  • cip     2nd Feb 2012 Member 0 Permalink
    Do you think "create" or "destroy" will be used more? I'd use NSCN for the one that is likely to be more common, to reduce the amount of NSCN->METL->PSCN sequences you end up using (because NSCN receives from special conductors like DLAY, INST, etc.). 

    -C
  • DCBloodHound     2nd Feb 2012 Member 0 Permalink
    Create will probably be used more.

    When i first thought of this the main use i thought of was for it to destroy and create (replace) essential electronic components so to expand the possibilities.
  • cip     2nd Feb 2012 Member 0 Permalink
    Interesting. I thought I could do something like that with PCLN + PVOD once but, of course, I failed, because elements have to flow on top of PVOD to be voided (duh).

    ARCP would have to pass through other conductors unaffected in order to be used to its full potential, otherwise you are limited to 3 element types per target location, or 4 if you never want to destroy+rewrite a location:


    Additionally, I think it makes more sense to say that if an ARCP with ctype none intersects an ARCP with a ctype X, then the element X is created (that is, to create an element it must intersect with ctype none, rather than another ARCP with the same ctype). That would provide some additional flexibility and convenience I think.

    C
You need to login before you can post replies