Element Suggestion : LSCN

  • Philip153
    20th Feb 2015 Member 4 Permalink

    LSCN would be L-type Silicon. It would be a solid melting into lava at 2500.00 K. L-type silicon can power materials like it's cousins PSCN and NSCN. When you spark the LSCN once, the power goes on. If you spark it twice, the power goes off. and so on. (This is not a steal of the QRTZ idea thread)

     

    LSCN would also :

     

    LSCN + ARAY : the BRAY formed does not create points and does not stack up. Also the ARAY only shoots BRAY in only the opposite direction from where it is sparked. 

     

    LSCN + FRAY : FRAY affects only it's ctype. Spark again, then it affects only the things that are NOT it's ctype.

     

    LSCN + CRAY : CRAY, like ARAY, shoots particles in only the opposite direction from which it was sparked. This is NOT how CRAY already works - CRAY just shoots out particles everywhere. The LSCN functionailty on ARAY and CRAY stops the work of putting INSL around them.

     

    LSCN + PSTN : PSTN pushes and PULLS particles in front of it

     

    LSCN + TUNG : TUNG does not heat up while conducting

     

    LSCN + WIFI : WIFI gives, but cannot recieve.

     

    LSCN + BTRY : LSCN acts like INST, instantly conducting.

     

    LSCN + INST : LSCN can recieve/give to INST like it's cousins PSCN and NSCN.

     

    LSCN + PSCN : LSCN does not conduct.

     

    LSCN + LCRY : LCRY's color is changed, then fades away after *LSCN's tmp* frames.

     

    LSCN + HSWC : HSWC can give heat, but it cannot "recieve" heat. This is an alternative for Heater, which is rejected. (This is NOT a heater suggestion thread)

     

    LSCN + WWLD : WWLD gives/recieves from LSCN.

     

    LSCN + C-4/TNT/RBDM : The explosives does not explode

     

    LSCN + Life 0 : LSCN's life is normally 10 and doesn't natually reduce. However, if it becomes 0 (only way to do it is to connecting BHOL to LSCN), the LSCN turns into PSCN.

     

    LSCN + tmp2 : LSCN disappears if it's tmp2 becomes 0. The tmp2 will decrease with each spark. Typing !set tmp2 lscn ? will cause the tmp2 to become infinity. Default is infinity.

     

    Edited once by Philip153. Last: 20th Feb 2015
  • Kikkin
    20th Feb 2015 Banned 3 Permalink
    This post is hidden because the user is banned
  • Protcom
    20th Feb 2015 Member 0 Permalink

    @Philip153 (View Post)

    "LSCN + WIFI : WIFI gives, but cannot recieve."

    Actually, to make a wifi that will give and won't recieve (if O = wifi, D = PSCN and C = any other metal that can be sparked like ttan for example)

    1. OC

    2. OC

    3. ODC

    when you spark 1, it will give a signal to 3  and will not give a signal to 2.

    when you spark 3, nothing will happen.

     

    Also next time, please tell us what are the uses of these suggestions :P

  • CeeJayBee
    20th Feb 2015 Member 0 Permalink
    The thing is, p-type silicon and n-type silicon are actual things. The p/n comes from the charge of the semiconductor (positive or negative). I doubt LSCN would work, as nothing is 'legative' or 'lositive'. Also, this is sorta like SWCH, in a way.
  • the_new_powder99999
    20th Feb 2015 Member 0 Permalink

    It could be ASCN, PSCN is positively charged semiconductor, NSCN is negatively charged semiconductor, ASCN could be alternating charge semiconductor. It seems to change between the properties of both PSCN and NSCN so it makes a bit more sense than LSCN.

     

    LSCN+ARAY doesn't create points or stack up, isn't this the same as PSCN+ARAY? And I don't understand what you mean by "the ARAY only shoots BRAY in only the opposite direction from where it is sparked." Doesn't it already do that? Maybe the BRAY could act like LSCN, Might be useful if you can't put LSCN close to something.

     

    LSCN + CRAY shoots particles in only the opposite direction from which it was sparked. Again, unless you are just putting big blobs down or not using it properly, this shouldn't happen. 

     

    LSCN + TUNG doesn't heat up while conducting. I think the TUNG is in control of whether it heats up or not, this might be hard to code, and anyway, why wouldn't you just use METL?

     

    LSCN + BTRY acts like INST. INST already does this, adding this would remove the use for INST completely.

     

    LSCN + Life, Life is used to conduct electricity already, you can't use it for something else. Why don't you make it turn to PSCN when it touches BHOL without changing it's life value.

     

    LSCN + tmp2 Use: variable use wires, not very obvious, you might want to say that.

  • Philip153
    21st Feb 2015 Member 0 Permalink

    @the_new_powder99999 (View Post)

     

    Philip153

    Nope. You are wrong sir. ARAY and CRAY doesn't only shoot beams in the opposite direction, it shoots then in every possible diagonal/horizontal/vertical way. So that's why they are almost always capped with insl

     

  • the_new_powder99999
    21st Feb 2015 Member 1 Permalink

    I looked at your saves and found the problem, you are doing then like this: (ARAY=A METL=M)

     

    M1 A1

    M2 A2

    M3 A3

     

    The sparks are all coming from the left, but A1 has a spark coming from the bottom left (M1 and M2) as well, so shoots BRAY on that angle. A2 has sparks coming from the top, middle and bottom left (M1, M2 and M3), and A3 has Sparks coming from the top and middle left (M2 and M3). 

     

    If you had 1 METL and 1 ARAY it should only shoot in a straight line, without any insl required.

  • KydonShadow
    21st Feb 2015 Member 0 Permalink

    @Philip153 (View Post)

     Actually, yeah. All the RAY elements shoot in the direction opposite that which they recieve their spark.

  • Antares
    22nd Feb 2015 Member 0 Permalink

    NO THE RAY ELEMENTS DO NOT (I'm gonna save a proof)

  • Protcom
    22nd Feb 2015 Member 0 Permalink

    @Antares (View Post)

    if X="ray element"; O="metal like ttan"; }="beam"; C="Spark";

    Move1: CCCCCX

    Move2: OOOOOX}}}}}}}}}}...

               <-----------X------>(Opposite directions)

    move3: OOOOOX

    Edited once by Protcom. Last: 22nd Feb 2015