Backup your Zone_Points table then try to run this as a query and see if it fixes things. If it doesn't just restore your backed up Zone_Points table. I believe the old lavastorm had some kind of clip plane issue with PEQdb or in old versions of it. I remember having some kind of Lavastorm issue when doing stuff with my zone_points or when I was changing over the newer zones back into the older classic original file versions around that same time. I ended up saving a SQL file for it in case I ever needed it again. Let me know if it does the trick or not.
Quote:
|
INSERT INTO `zone` (`short_name`, `id`, `file_name`, `long_name`, `map_file_name`, `safe_x`, `safe_y`, `safe_z`, `graveyard_id`, `min_level`, `min_status`, `zoneidnumber`, `version`, `timezone`, `maxclients`, `weather`, `ruleset`, `note`, `underworld`, `minclip`, `maxclip`, `fog_minclip`, `fog_maxclip`, `fog_blue`, `fog_red`, `fog_green`, `sky`, `ztype`, `zone_exp_multiplier`, `walkspeed`, `time_type`, `fog_red1`, `fog_green1`, `fog_blue1`, `fog_minclip1`, `fog_maxclip1`, `fog_red2`, `fog_green2`, `fog_blue2`, `fog_minclip2`, `fog_maxclip2`, `fog_red3`, `fog_green3`, `fog_blue3`, `fog_minclip3`, `fog_maxclip3`, `fog_red4`, `fog_green4`, `fog_blue4`, `fog_minclip4`, `fog_maxclip4`, `fog_density`, `flag_needed`, `canbind`, `cancombat`, `canlevitate`, `castoutdoor`, `hotzone`, `insttype`, `shutdowndelay`, `peqzone`, `expansion`, `suspendbuffs`, `type`) VALUES ('lavastorm', 202, '', 'The Lavastorm Mountains', NULL, -25, 182, -74, 0, 0, 0, 27, 0, 0, 0, 0, 1, '', -230, 50, 1850, 10, 2000, 10, 255, 10, 1, 255, 1.00, 0.4, 1, 255, 50, 10, 10, 800, 255, 10, 10, 10, 1800, 255, 10, 10, 10, 1800, 255, 10, 10, 10, 1800, 0.33, '', 1, 1, 1, 1, 0, 0, 5000, 1, 1, 0, 0);
|
__________________
"We are all on the same team, and I think not enough people realize this."
- Leetsauce
|
Hybrid Mode
