2 replies to this topic

[argent77]

I don't know if this is already known, but it looks like MoveGlobal() (action 197) does NOT substitute the current area for the MYAREA text. (Just had a long debugging session to find this out.)

I've tested it with several more actions and MoveBetweenAreas() as well as LeaveAreaLUAEntry() show the same behaviour (although it doesn't make sense to use MYAREA with them anyways). Some of them even crash the game. Following this pattern, I guess MYAREA doesn't work correctly on any global movement actions.

[Avenger]

Yeah, in the original IE this action doesn't execute the movement only when the target area is loaded. Until that, the actor resides in Limbo (in the game file), effectively having an invalid "MYAREA".

[igi]

Updated MYAREA note in the variables appendix, thanks.