Author Topic: How is copying of events handled?  (Read 690 times)

Title explains it all. How are they saved? How are they loaded? Etc.

What do you mean "copying"? The event system is quite large so you have to give more detail what you want to know.

What do you mean "copying"? The event system is quite large so you have to give more detail what you want to know.
Sorry for the ambiguity, I was referring to the client sided feature in which a user wrenches a brick, hits events, presses the "copy" button, wrenches another brick, and apples copied events to the other brick.

That's just a client sided feature where if you have the box checked it will not request the events from the new brick and keep the old ones in the gui.

That's just a client sided feature where if you have the box checked it will not request the events from the new brick and keep the old ones in the gui.
Ah I see now, a little more complicated than I had wished it to be. Is there a pre-existing add-on that allows injection of events from a file?

You could get events gui plus, it has the ability to save a set of events to a file and load it again. Though it has a little bug with saving checkboxes, which I fixed, here is my version: https://dl.dropboxusercontent.com/u/143512782/bl/Client_EventsGUIPlus.zip


You can then write a set of events, save them to a file and see how it is structured, then edit it with a text editor or something and load it again.

If you mean server sided then I don't know.