KAZESUI'S PROFILE

post=109014

post=108945
you do realize that you need to constantly update the screen related coordinates of the torch event, no?

wrong

yup, realized it after having done some new tests with it. Kind of funny how I never got it to work when I tested it long ago, and ended up assuming it didn't work that way as a result of it

- drops a giant steamroller with an angry vampire on top of the enemies
- uses a random high tier spell/skill
- temporary elemental resistance increase
- changes a monster into a bigger monster
- causes a big explosion damaging both enemies and allies
- changes a monster into a hero and a hero into a monster
- deals damage to the "unit on the battlefield" with the highest level
- reverse hp of party members (ex. 80/100 -> 20/100)
- turns the gambler into a poor peasant

Experienced something similar when I was working with giant events myself. I had an event that big it would take about 5 minutes to load the event window whenever I wanted to edit the event.

You should probably avoid making that big events in the first place though. You'd probably be better of dividing the event into several events while using the "call event" command in the main event. looks better and makes it easier to go over certain parts of the code, rather than having to scroll around to find a little piece in a giant event

Since everybody seems to like those arrow puzzles I figured I'd make a little map with some of those as well. Hope you'll all enjoy it, mwahaha

or if the script really works as it should so far, you could simply put an "end event processing" under the cancel menu branch.