[RELEASE] e:getWirelink()

[Grocel]

Maybe because is does not wire anything.

[TomyLobo]

it makes people too lazy to wire things up

[kna]

Oh, great reason to not include in SVN... Is there any difference, wire you things manually or write code that wires them with wirer or with e2?

[TomyLobo]

wired wirer is not wiresvn, for one

and you'd just spawn a bunch of components and a chip and have the chip auto-detect everything.
this has nothing to do with building anymore.

[Rybec]

It would, however, be great for factory construction.
And you still have to place those entities. It would take a lot of the tedium out of wiring up something large, like display screens that all show the same thing scattered throughout a base. You could make a "universal car" chip or something where you build a new car with wire components included, then just slap the chip on and not need to wire.

It adds to creative ability.

[TomyLobo]

for factories you have the wired wirer.

[Syranide]

You could make a "universal car" chip or something where you build a new car with wire components included, then just slap the chip on and not need to wire.

It adds to creative ability.

The only purpose of something like E:wirelink() is to create self-wiring stuff, which basically boils down to creating frameworks or "templates"... which are rarely associated with creative flexibility, rather the opposite. I don't see how creating a "universal car" template gives you more creativity or flexibility.

It would take a lot of the tedium out of wiring up something large, like display screens that all show the same thing scattered throughout a base

Use "wireless" stuff then for instance or create "hubs" that simply connect using a single wirelink, and place prefabricated dupes with everything included. No need to wire the same stuff up, the same way over and over.

[kna]

If you create "universal car e2" you can focus mainly on building car itself, altering design and others things, and then just place thrusters and e2. So you waste less time coding loads of expressions that do same thing or wiring one semi-universal e2 to thrusters that you should attach in special places.

I don't think wireless stuff can act as hi-speed device, so you can't wirelink console screen with hubs.

And if you can wire any entity to e2, then it does not mean that you must create "templates" or anything similar. You can just use it to wire multiple screens at one time, or just shorten time of wiring.

I don't see any difference between wiring stuff yourself of writing code that wires stuff automatically.

[Hardy]

It can be useful for SB, just point at doors, and say something like /adddoor "name", then control them by /open "name" and /close "name", instead wiring each door. This is only one example...

[TomyLobo]

do you mean door controllers on the map?