{some insight plx} Fort siege date scheduling overkill?

Support for the latest build of L2J Server, get help here with installations, upgrades, problems.
Do not post bugs reports here, use viewforum.php?f=77 instead.
There is no support for other server builds than the official provided by l2jserver.com
Forum rules
READ NOW: L2j Forums Rules of Conduct
Post Reply
blarke
Posts: 77
Joined: Thu Nov 18, 2010 7:48 am

{some insight plx} Fort siege date scheduling overkill?

Post by blarke »

If you want to receive support we need this info to help you properly.
» Find Revision
L2J Revision Number: exported (built on 20110703_1231 from the then-newest core)
L2JDP Revision Number: exported (built on 20110703_1231 from the then-newest core)

Hello everyone,
Just one quick question since I can't seem to find the problem. This was the same with the build on 20101215: when registering to most forts (except for Dragonspine, which seems interesting...), basically nothing happens. Checked the db and it seems that it is way overkilling the timestamp. (1313612807718 and so, so like 41500 years from now)
Tried to update the db since mine is still using decimal(20) for siegeDate, but it is the exact same with bigint(13).
No error message, no log, just this small scent of mistake. Used the same db for the newest beta H5 repo for testing but same result; also had this issue back before on another server so this does not seem mysql/servertime/whatever error. Seems like a format problem - but where or what? :)
As mentioned above, Dragonspine is working fine along with the castle siege schedules. Are the other forts (all of them) disabled, or this is some kind of error? If so, can somebody provide some ideas about what to check? :)

(Note: main problem, as mentioned above, that this is an exported core/dp combo since my eclipse subclipse plugin is missing some dependency and the synched code is not compiling with a subclipse error. Yey, distributed enhancing - I do not have the original code so I did not yet bother to get the source with some working svn solution...)
blarke
Posts: 77
Joined: Thu Nov 18, 2010 7:48 am

Re: {some insight plx} Fort siege date scheduling overkill?

Post by blarke »

now I'm totally confused.
I managed to get afk for like 2 hours and forgot to reg out. fort siege started!
after it was completed, it started to count down from 10mins right in the very same second I conquered the flagpole... and after reaching 0s, nothing happened :o
also side-note: setup for countdown is 10mins.
and the suspicious merchant didnt even respawn but it initiated the countdown.
Post Reply