Sorry didn't spot this message earlier. You'd have to have a shared character place and pass copies of the circuits across (via workstation copies, vc datasticks, etc.) In multiplayer may be easier to do with a friend with you swapping characters.

Any chance a simple text export/import could be added? Or possibly, instead of the circuit workbench being a shared thing, all circuits are stored locally, and the circuit datasticks are only really necessary for sharing circuits between players.

It seems a far more reasonable way than locking the circuit to a world - it did take me an hour to put together the configurable airlock manager, and having to recreate it, albeit not from scratch, is a pain.

Hm no clue how but an exportsystem with extrafiles which could be send over to other people outside Starbound would actually be necessary for complicated systems "looks towards his insane configurations..." as well as for the alt chars and backup^^

I could potentially let circuits be saved up into the storage/starbound.config and downloaded again from there, but don't really want to clutter that file with the huge tables macrochips can generate. I already use that to store iec and wizard settings though, so maybe.

Will see what I can come up with.

Are the tables really as huge as you say? For any particular component, I can at most see one field for its ID, one for its type, two for positioning coordinates, and some variable number for each individual output connection, given that the outputs can be connected to multiple other objects. As for connections feeding into a component, they can be addressed by (id)-1, (id)-2, etc. The bulk of the storage would, if the circuit gets programmed by someone who doesn't know how to lay stuff out, contain the nodes of the circuit, which would be as simple as their address and however many outputs they target.

Conceivably, it could fit into a CSV format.

The point of the circuit table then simply becomes being able to store and recall them, preferably to separate files for uploading.

I'm working on adding a 'broadcast' functionality to the workstation to pass circuit data thru the player.config.

aaaand that option is being shut down with SB 1.3 removing the necessary bits of Lua API which have been deemed too powerful. Dev's said such things should be done via object/item transfer.

Other option at best now I think would be writing to the starbound.log so a /spawnitem command with relevant could be used outside of that.

Releasing anything short of all the features is kinda pointless, since modding is meant to transform the game, not just augment it. Why is it a bad thing that modders can do powerful things?

There was some discussion on the modding channel about getting a script.config to read/write to instead for storing such data, rather than using the starbound.config which holds a lot of stuff you probably wouldn't want to have modified by someone elses mod.

On the plus side, a few other extra things are coming which will be interesting to play around with.

Just added to the Datastick eject a starbound.log writeup of the necessary /spawnitem command. Hopefully that will suffice for present :)

Tried the Spawnitem command with an alt and had no success, do i need the macrochip workstation before? since the alt just started out.

Did you have admin mode turned on as well? need to do that first. Also note it spawns the item at mouse cursor position, if you haven't used this before.

Tried it again and worked now, was probably and issue to copy the whole line correctly^^

Maybe it's the right place to also suggest another thing^^

Is there a way to copy data from one macrochip to another with already existent data? So that it places the copied data from chip 2 above or underneath the existing circuit in chip 1?

Atm i have to decide which chipdata i take as base and rebuild the second data within the new chip manually, which is often complicated and very time consuming.

Hmm, not an easy way to do such. I'll note it for a later look though.

Well, a decent first step for a feature like SFC-Daniel suggested would be to make chips auto-center themselves on the grid once a setting is toggled or it's saved into the workstation.

Then, being able to arrange other components would be trivial. Alternatively, you can take a page from Atanua's book and make embeddable chips so that a particular circuit can be reused once built.