Hi im using beasty files on a ubuntu pc, all is working fina but i have problems with Snake Island Race. All time based quest are working fine but this not. When i try to enter into the race i see a message saying that time mision is expired any ideas?.
Im using beasties files also. Check your servers date/time and see if its on the same time like the quest when you try it. For me its working after i set the servertime to utc -1
I have trouble with this also actually.
The quest doesnt give any error it simply doesnt ever show up.
I got monthly horse race to work once, then it never worked again.
I can only presume the quest time system in our server files is kinda messed up for those quests.
All my other time based quests work, forest ruins, dragon palace, netherbeast...
Snake island race is very difficult to get running. You need BOTH (yes there are 2) clocks which are used by perfect world in perfect sync.
There are some steps to check that:
1. check "hwclock" what time it displays
2. check "date" what time it displays
3. ingame open console and check what "d_getservertime" says
if your hwclock is not set in UTC, you need to set some special file in debian that tells informs some systems (including pw server) about that fact, otherwise you will always have a minimum of 1h offset between 2 of the 3 outputs, which result in horse racing not working.
i can help you but you need to tell in which timezone(s) your server currently is
I set them both and it simply wont activate.
I think it takes into account the client users timezone also to display the quest.
My actual working config for that:
hwclock = utc
date set to local utc -1
working fine with that. Just needed several restarts till the server knew that it has to use that settings.
use repairdb script to apply that settings ;)
additionally in debian are not just the 2 times and their setting, there is also a config file that is threated seperatly from all date/hwclock changings which tell the system (AND pw server) if the hwclock is in utc
edit: i found it again:
its /etc/default/rcS
its the setting "UTC=yes" which tells the low level stuff if the hwclock is utc. this has to be set seperately.
It can be quite confusing, for us the server was always 1h ahead of our time until i found that setting (we are in germany, gmt+1). Since i set it correctly i can even use ntpdate to set the clock automatically and the server accepts it without problems.
Last edited by tbnanubis; 11-03-11 at 12:02 AM.
That is the only thing I don't like about Linux at times... so many ways to do the same damn thing...Originally Posted by tbnanubis
i laughed loud as "ms" had that problem, they took the server offline for 23 hours to fix a clock, instead of letting the repairdb script update all changed times.
Ok thanks i try it.
Any idea how to use that repairdb tool ? cause i cant see any. Our servertime changed again and it killed most of the eventquests.
Actual setting is:
hardware clock: UTC
local clock ( date ): CEST
d_getservertime: UTC+1
Dunno where it gets this time from because its exact between that 2 clocks.
Last time i simply changed the timezone and rebooted the whole Server but this time it doesnt change anything.
one more thigns.
remove unknow date from tasks.data
set the npc in world ncpgen data with trigger where u set the time when its showing up and dissapear
Reply With Quote
