2 réponses à ce sujet

[Proleric]

On every area transition, I find that the order of events is

EVENT_TYPE_AREALOAD_SPECIAL
EVENT_TYPE_EXIT on the old area
EVENT_TYPE_ENTER
EVENT_TYPE_AREALOAD_PRELOADEXIT
EVENT_TYPE_AREALOAD_POSTLOADEXIT

This was by no means easy to establish, because the Display family of functions appears to be bugged when used in an area event script.

DisplayStatusMessage doesn't seem to work at all.

DisplayFloatyMessage seems to work on initial entry to an area. It doesn't work on subsequent visits, unless there is a transition to a different area list en route. It doesn't work at module start, either.

Does anyone know of a display function that works here?

Life's too short for logging

[Craig Graff]

You don't like PrintToLog?

[Proleric]

Thanks for taking an interest, Craig!

Yes, PrintToLog will do it, in the last resort, but it's a bit clunky for monitoring events in real time IMO.

I have to Alt-Tab from the game to the log, wade through other biz to find the message, only to find that it probably isn't there yet (presumably because log output is buffered).

When testing, I have a debug item in quickslot #1 with a Unique Power script. In the end, I accumulated the event info in a string for display by that widget.

Modifié par Proleric1, 30 mai 2011 - 07:44 .