Quote:
Originally Posted by PlumbGame
Wouldn't you have to change the zone line coords to actually send you to highpass, and not highpasshold?
|
I'm not sure what you mean by "zone line coords". If you mean the zone record, the old zone record has short_name "highpass" and zoneidnumbner 5, and it has all the zone data i want. But, trying to zone to zone 5 in the underfoot client does nothing, which is the basic problem. So I have to change the short_name to "highpasshold" and the zoneidnumber to 407 to get the client to do anything when I type "#zone highpasshold" or "#zone 407". Looking at the logs, it does seem to try to load zone 407, but, again, I get no landscape.
Here is the log entry for zone out of highkeep to highpasshold:
[07-11-2016 :: 17:04:47] [Status] Zoning 'Wizzie' to: highpasshold (407) - (0) x=-105.000000, y=63.000000, z=4.000000
and here is the entry for zoning back to highkeep using #zone:
[07-11-2016 :: 16:49:39] [Status] Zoning 'Wizzie' to: highkeep (6) - (0) x=88.000000, y=-16.000000, z=4.000000
[07-11-2016 :: 16:49:41] [Zone Server] Dropping client: Process=false, ip=10.0.0.3 port=61622
[07-11-2016 :: 16:49:46] [Status] Zone Shutdown: highpasshold (407)
As you can see, it is zone 407 that is being used, which normally loads the new version of highpass called highpasshold, but which should load the old files that I have renamed to highpasshold.