What about how I described it earlier though? I also don´t like the idea of adjusting events on a per-instance basis. I pretty much want it to be exactly like a behavior, except via events.
Also I just noticed my earlier post ceased to exist :V luckily chunchun quoted it so here it is again:
Like behaviors I see it as a mostly self-contained thing that could be used (and especially reused) in a generalized way.
Lets just say you need an object to move in a specific way, for example have it constantly circle around the viewport edges. The eventsheet would allow you to add properties (e.g. speed) that then are exposed in the object properties. "Global variables" could be exposed in the form of expressions so you can read e.g. how many times the object circled around the viewport.
Further the idea would be that you can´t specify an object inside the event sheet, and the events always automatically reference the instance. This means you can plop it on any object without having to change anything in the code and have it work (including across projects), assuming you don´t access conditions/actions that aren´t available. You can´t "set text to" on a Sprite afterall.
This would also make it easily shareable. Kinda like the plugin database, there could/should be a place to share that kind of eventsheets. Maybe, don´t call it eventsheets just to avoid confusion.
That´s roughly the idea I had in mind, I hope it makes sense.