I think this is the most important. Although I can't really add to the technical difficulties on how easily scripts conflict or break.

This is a trip down memory lane and I do remember chatting about this, mostly just spitballing ideas. Initially I saw things like the events in CloneV, recoloured springs in a bunch of levels and the difficulty events like Seren said in Transarctic Mountains and this got me thinking: From a JCSer perspective it would be nicer to focus on the creative vision rather than spending time importing events that could be useful in any kind of level. Like a parameter to colour your springs and set the strength of a spring is something I'd want available in my event list any time I start levelmaking. I think the most important question is: Could this be used in any level? Then it's probably within the scope.

Back to the scope, I think global settings are the JJ2+ Level Properties, and should probably remain an extension of that. If I want my level to 'infinitely loop' like Hyperspace, that sounds like a checkbox that should be there. The ability to not include events in the Easy difficulty sounds better as a standard MLLE feature.

From what I remember from the conversation, it wasn't necessarily object related, but custom event related. Events are placed somewhere in the space of the level, and does something in those locations to interact with. I know that adding pits to a level is an outlier but overall it still holds true. I can't think of other examples where an event does something somewhere completely else. Adding infinite loop like Hyperspace, or palette cycling, or basically any layerdraw functions do not feel event related. Sure, you can enable/disable layers or palette cycling with tile triggers, but that is not the scope of this at all imo. It's just not feasible that triggering background layers in a specific way from an event can be an automated process. For example the use case in Ezindigo where the background switches at a specific height is not something that can be automated. That sounds like something not useful for any level. Same goes for triggering certain weather conditions that are not global on levelload.

Custom events have to work fully in isolation, while above enables/disables other scripts that are not related to that x-y-tile. I suppose the scope I envisioned is Area + Object events. Having similar events that are already stuck to tiles, but MLLE having a browser of having a list of other useful events that can be added to the event properties.

I think ideally if there if there was a custom event/ snippet browser in MLLE, the scope is to seperate JJ2+ level properties + custom 'Global' tag and Event editor + custom 'Event' tag.