READ THIS BEFORE YOU MAKE A SUGGESTION

[Colonel Thirty Two]

Lol, I guess noone reads the stickies? Even people that have actually been to wiremod >10 times and have the post in bold print?

Here's a list:

• "canBeDuped(0)"
• Functions
• Virtualization
• wait()

Also, we now have an out of game e2 editor =)

[ktccd]

Just wanted to point out a possible edit in this:
Things not to suggest "out of game E2 editor" is made and works awesomely in the E2 section...

[Colonel Thirty Two]

Also, we now have an out of game e2 editor =)

*Cough*

[Martijn]

This thread suggests not to make suggestion about E:wirelink() or similar functions, I'd like to know why that is. I've used to search function (yes, some noobs (forum-wise) actually DO use it XD) and found several threads about it, in some there was referred to a thread where, supposedly, TomyLobo suggested E:wirelink() but where it was refused by Syranide. I have not been able to find that thread, but if it does still exist somewhere, could someone point it out to me? If I cannot find that thread, I feel tempted to create a new thread on this. Especially because from what I've read so far, it has been suggested multiple times, yet always denied, while neither side had a good reason (that I know of so far) as to why or why it should not be added.

[Bull]

Don't.

It doesn't add any functionality. You still need to spawn the entity where the wirelink is supposed to be added.
And adv wire, gives you an option to create the wirelink too.

It's the same with createWire(), it doesn't do anything else than removing the need to pull out your wire tool.

[turck3]

Since you're not being clear.... I'll assume that you want a function that lets you wire items together via an expression gate 2......

The biggest problems I see with that are:
1) Why? You might as well wire it up and have more than one variable. Also, identifying which items to connect would be equally space-consuming to having multiple variables.
2) It would probably belong as a part of propcore or something like it because of security risks

PS: If you really wanted something like this... there are a billion ways to do it, including with intermediary E2s with if statements and/or using global variables. Might take an extra chip or two, but it'd work and wouldn't require a physical wire to come into play (if you did globals).

[Drunkie]

Added a new rule against the seemingly never-ending E2 code / dupe protection idea.