I have been having the same problem for a while. I was running Rev 535, but Today I just updated everything to 590. (I pulled down the current database/quests as well as the new build) I searched the changelog, and found this SQL Script:
DROP TABLE IF EXISTS `respawn_times`;
CREATE TABLE `respawn_times` (
`id` int(11) NOT NULL default '0',
`start` int(11) NOT NULL default '0',
`duration` int(11) NOT NULL default '0',
PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
ALTER TABLE `spawn2` DROP `timeleft`;
If you run it, (You may need to remove IF EXISTS if you're not using a stored proceedure) it looks like it basically removes the instance_id key of the respawn_times table. Removing that field allows my #repop force to work. However, it breaks #repop, and now #repop works the same as #repop force, which can also be a pain.
For a developer, or someone who has more knowledge than myself, I think the problem may be that my zones aren't establishing an instance_id, and that's why #repop force isn't working for some people, like myself. I hope it's not a wild goose chase, but I'd appreciate it if it could be looked into.
Thanks
|
Threaded Mode
