That's like me asking "why use an ABS script when you could just event it?"
I'm sure there are use cases where the event solution is unfeasible.
But I guess in the case where someone did manage to port the default engine to some other platform and custom scripts didn't work...the event solution would be the only way around it.
Nope, it's not at all like that. I would also be interested in hearing the specifics of the cases where the event solution is "unfeasible".
You are asking for a feature which automates nothing.
Feature requester:
"Make the maker intelligent enough to know that, when I start my character on map M, variables X, Y, and Z should be set to N"
E!:
"That is impossible. The maker cannot determine the state that your game should be in when the player first enters map M. Any number of things may or may not happen between the beginning of the game and that point and there is simply no way the editor can predict which will and will not occur."
Feature requester:
But right now I have to manually change each variable and switch to get the game into the state that I want. This stinks when I need to perform the test more than once.
E!:
That's a valid concern. I suggest you create an event on this map to set them for you when the game begins.
Feature requester:
But... but... I want a new dialog window! It will make my life so much easier! And oh yeah, there are times when the event solution won't work, but I'm not going into specifics.
E!:
....yeah ok it's on the list. Have a good day!
----------
It simply makes no sense. *This cannot be automated*. The computer cannot read your mind.
Really, this is what I do for a living. I have developed some amount of skill in weeding out the good feature requests from the bad. Users are terrible at proposing good, workable solutions. The new "feature" wouldn't save you any work, that is why your analogy is erroneous.