Quote Originally Posted by Futan View Post
Kind of curious where you got the source code to know that the supposed area limit is hard coded? Hard coded, of course, meaning it's in the source code opposed to an external .DAT. And that's something that would only need to be loaded into memory upon changing zones, while a bunch of other much more memory intensive things are being unloaded from memory, so there should be no issue with memory that causes an area limit.
Check the memory? Your current area was stored in a 1 byte variable, which limits it to 255 possible values. According to someone in another thread this was changed recently, so the new the cap would be 65535, which obviously will never be reaches.

And no, it can't just be checked when zoning. It needs to constantly be in memory, just like your x,y,z position.