Hmm, thanks. I might give using regions a go then.
Er, I guess I'll stick suggestion on this topic because I think if checking walkable areas isn't currently available it'd be a good idea.
EDIT: Well, I'm using regions now which works fine except for one problem. I'm using the Interaction editor for regions, putting RemoveWalkableArea() etc in the "When player walks onto region" section. Basically, I have them set out like this:
REGION#4
REGION#5
REGION#1
All touching like that, and all corresponding to walkable areas of the same number. When I step onto REGION 4, it restores all the walkable areas. When I step onto REGION 5, it removes walkable area 1. If I walk onto #5 and stop, the whole thing works. If I move without stopping from 4 onto 5 and keep heading down, my character is able to walk onto #1 and then gets stuck because #1 finally disappears.
So, does this mean these commands are being blocked? Is this supposed to happen?
Er, I guess I'll stick suggestion on this topic because I think if checking walkable areas isn't currently available it'd be a good idea.
EDIT: Well, I'm using regions now which works fine except for one problem. I'm using the Interaction editor for regions, putting RemoveWalkableArea() etc in the "When player walks onto region" section. Basically, I have them set out like this:
REGION#4
REGION#5
REGION#1
All touching like that, and all corresponding to walkable areas of the same number. When I step onto REGION 4, it restores all the walkable areas. When I step onto REGION 5, it removes walkable area 1. If I walk onto #5 and stop, the whole thing works. If I move without stopping from 4 onto 5 and keep heading down, my character is able to walk onto #1 and then gets stuck because #1 finally disappears.
So, does this mean these commands are being blocked? Is this supposed to happen?