I have run into this several times now -- When I want to put several SWCH pixels not touching to enable / disable a group of wires with just one PSCN or NSCN.
Main idea:
Say you have a bunch of wires that need to be toggled by a switch. You put a bunch of (... > METL > [none] > SWITCH > [none] > METL > ...)'s up next to eachother. If you don't put INSL between the switches, all of the output wires (and possibly all the other unsparked input wires) receive a spark even if you just sent a spark in one input wire while the switches were on; if you do put INSL, you have to enable or disable every single switch separately at once to get the right effect, which can increase space usage by a lot. HINS will fix this by blocking sparks between switches, yet allowing all the switches to be turned on and off together if they are just seperated by one pixel of HINS.
Element properties:
Name: HINS
Description: Half insulator. Insulator, but less insulating, thus allowing for things like SWCH pieces being able to turn on and off from just one piece while the pieces are seperated by this.
Color: #7f81950 (I blended together the colors of INSL and METL)
Type: Solid
Behaviors:
Behavior uses / functionalities / descriptions:
If any scripter (someone who makes stuff that shows up in Jacob1's scripts manager) decides to add this to their script, let me know the name of the script. (assuming it doesn't change existing electronics' functionality or something crazy, lol)
FIFTH EDIT: I am so bad at leaving tiny errors when I type a lot. (and then notice them after I already posted)
SEVENTH EDIT: An idea occured to me minutes after posting to try SWCH + ARAY. Behavior #1 is unnecessary.
I'm not a fan of this;
CRAY treats FILT in a special way, and I personally like that. There's usually an elegant workaround for any problem arising from that.
Jeez I hate this editor. Don't sweat edits btw :P
I don't quite get what you mean on 5. (SPRK > METL > HINS > CRAY) means you put a wire which contacts the HINS and then the CRAY contacting the HINS on the opposite side will treat FILT like common materials. If no HINS is between the wire and CRAY though, CRAY will do fancy stuff with FILT.
(I'm making a new texter that has 8 reels, normal, shift, control, alt, shift+control, control+alt, shift+alt, shift+control+alt; Each reel extender had a different WIFI set so I needed to pick which WIFI set got the inputs from an equal input WIFI set, if that makes sense)
(Also, the input WIFI set is directly controlled from the keyboard)
By its being complicated compared to its benefits I mean you technically introduce a new conductor just to iron out a quirk of CRAY that is usually easy to work around. That's... not something that tends to make it into the game.
To be quite honest, no, your second paragraph doesn't make sense, but that's likely a problem on my end. In any case, I'd be happy to help working around any issue that comes from CRAY treating FILT differently.
Also, LBP* :P
Okay, thanks in advance if I do need help.
Actually, the CRAY and FILT thing was an issue I ran into a while back in the days of me making DRAY texters;
it most likely won't come up much anymore, since FILT is my absolute favorite for texter systems. DRAY systems are clunky and glitchy compared to the FILT systems. (assuming there isin't a highly glitchable backspace system like in the ZNG Nexgen-R1)
Nothing's glitchy with that DRAY system, it's just that you need to figure out how to use that correctly.
Also you don't need a separate elemenet for just powering on switch.
Btw i created something a long time ago which you can use instead of that switch array thing.
Just ask me in PM if you want, i can provide you the save.
@Cracker1000 "glitchy" as in it goes wild if you spam the keyboard.
The glitchiest the FILT system gets when spammed is odd cursor movement and mabye unprogrammed characters being printed.
(characters might get messed up too)