RPG Maker Event Touch Trigger 2.2

By request from Kaza, I've updated this Plugin so multiple events with the same name can now be used as touch sources, as opposed to the first event found with the name.

Version is 2.2

What does this mean? You can have multiple events called "FIRE_BALL" and have them all interact with multiple events called "PILE_OF_WOOD" without having to type in hundreds of event ID numbers.

This update adds compatibility with Orange Custom Events; http://forums.rpgmakerweb.com/index.php?/topic/46527-orange-custom-events/

So now you can do things like spawn multiple projectile events that can hit other events and trigger actions such as killing them. Perfect for an event-based ATB.

I said last update that common event support would require a re-write, so I did that.

There's been some fundamental changes to the API, so compatibility with version 1.1 is completely broken.

I've updated the example event screenshots to reflect this - please take a look!!

This update adds a parameter for defining a default turn-toward behaviour for triggering events.

This mimics the way that events turn toward the player by default with player-touch/event-touch.

If you set this value to false (or clear it) then you will have to implement the turn-toward within the event page, which means knowing what event triggered the touch - something that isn't possible at the moment.

My plan for the next version is to write the triggering event's variable into a globally accessible variable in Javascript; this way we can at least use the script call command to do something with the event. I am also considering adding the option to set the event target to the triggering event in the JSON data structure; which means that we can write event page logic for the triggering event, however the "logic" would be the target's event, so this will be confusing to deal with in the editor; something I want to avoid.

I also tried an idea for having common events be called. This would be a good way to get around the confusing "event logic in other event's page" I described above - but getting common events working along side the current system proves more complicated than I first expected. I'll have to write a separate chunk of code just for common events, something I don't have time for today.