Changes to STOR and Sensor Elements

  • The-Fall
    13th Aug 2013 Member 0 Permalink

    STOR Changes:

    A feature I believe ought to be added to STOR would be to exclude all other elements that do not match STOR's ctype.

    This would work much like VOID's property; where if the tmp is changed to 1 or 2 (I forget which), The particle of VOID will erase only the particles that match its ctype.

     

    If STOR's tmp or tmp2 are set to something other than the default (0) then STOR will store any particle that is not its ctype.

     

    Changes to Sensor Elements:

    If the Sensor particle's tmp2 property is set to something other than its default, the sensor will emit a spark when the pressure / temperature of a particle fall below the temperture of the sensor.

     

    So, for example, if you have a particle of TSNS and a particle near it has a temperature less than the particle's set threshold, then it will emit a spark.

     

    In short, this is simply the reverse of what TSNS and PSNS already do. Instead of detecting pressure or temperatures higher than the particle temperature, it detects when lower than the particle temperature.

     

    Your feedback on this suggested change is appreciated, as long as it is positive.

    Edited once by The-Fall. Last: 13th Aug 2013
  • BigPig
    13th Aug 2013 Member 0 Permalink

    @The-Fall (View Post)

    STOR's ctype did it but its tmp/tmp2 is used to store the element it stored.Changes to Sensor Elements is nice.

  • Oats
    13th Aug 2013 Member 0 Permalink

     

    "Your feedback on this suggested change is appreciated, as long as it is positive."

     

    Your not going to appreciate this, but here I go:

    -------------------------------------------------------

    Although most people will spawn STOR with the default tmp and ctype, when a player uses the command !set type all STOR, the particles on the screen will retain their previous tmp and ctype.

     

    This suggestion would break existing saves with those properties as STOR particles placed into the simulation that way would now delete most elements.

  • The-Fall
    13th Aug 2013 Member 0 Permalink

    Well, If the STOR Suggestion does not work, then that is fine. The Sensor Suggestion is a bit more critical.

  • Oats
    13th Aug 2013 Member 0 Permalink

    The same problem will occur with all sensors too, as tmp isn't reset when an elements type is changed.

     

    The suggestion can also already be achieved with a simple "NOT" gate.

    Edited once by Oats. Last: 13th Aug 2013
  • Catelite
    13th Aug 2013 Former Staff 0 Permalink

    Not that adding more elusive tmp modes to elements has so far ever been a bad idea, but the reference pile of console/PROP-requiring element modes is starting to pile up, and most newbie users are going to get absolutely nothing from it.

     

    If at all possible, invent ways of routing around the problems this might fix. Sometimes, it makes more amusing machines. :P

  • boxmein
    13th Aug 2013 Former Staff 0 Permalink
    @The-Fall (View Post)
    >So, for example, if you have a particle of TSNS and a particle near it has a temperature less than the particle's set threshold, then it will emit a spark.
    I made this save ages ago, but it applies here:
  • The-Fall
    13th Aug 2013 Member 0 Permalink

    @boxmein (View Post)

     Thank you.

  • greymatter
    14th Aug 2013 Member 0 Permalink
    @Oats (View Post)
    But a possibility of a user going for !set type x stor is very obscure...
    @The-Fall (View Post)
    Gates are awsome. Although the change you suggested is helpful for newbies who don't know logic gates.