DeletedUser
Guest
I received an attack during the attack break, and am not happy.
http://us2.tribalwars.us/public_report/0f8b7f73cf8c58198ef52ab85c37f14a
http://us2.tribalwars.us/public_report/0f8b7f73cf8c58198ef52ab85c37f14a
I received an attack during the attack break, and am not happy.
http://us2.tribalwars.us/public_report/0f8b7f73cf8c58198ef52ab85c37f14a
I had something similar, seems attacks that were sent before the break still land those sent after don't.
I had something similar, seems attacks that were sent before the break still land those sent after don't.
That's definitely not the case, and I know because I had around 60 incomings before the break, and those that landed before 5:00 server time hit, and none afterwards did.
isnt US 5 hours off from .NET??? that may be why- just used the same times as NET but forgot to change times???
Those types of mistakes are understandable at first, but after (1) German writing on version 7.0 (2) .net server time on US2 and (3) idiots on the US servers being rewarded for not paying attention to the times of the attack breaks, it can get a little old.isnt US 5 hours off from .NET??? that may be why- just used the same times as NET but forgot to change times???
That might explain it... except it's a 6 hour difference, not 5.
Things happen, it was set up properly there was just something in the.. mechanics that either did not work properly or was not taken into account. Hopefully there is a way to backlog both worlds to the exact time of when the break should have started.
Not possible.
start These settings define a period during which peace is kept. Attacks arriving during this period are turned into visits. After the end of this period an increased server load occurs du to many attacks arriving. This setting determins the starting time (as UNIX-timestamp).
end End of peace period (UNIX-timestamp)
Those are the settings that determine when the attack break is active. There is nothing wrong with the "mechanics". It was either never edited and contained default values, or was edited by someone who didn't understand how UNIX timestamps work. UNIX timestamps are a measurement of time in which a number is the number of seconds that have passed since midnight on January 1st, 1970.
Specifically: There have been 40 complete years since then, ten of which were leap years, specifically the following: 1972, 1976, 1980, 1984, 1988, 1992, 1996, 2000, 2004, 2008
40*365+10=14,610
The break starts eight days before the end of the year, so that's another (365-8) 357 days. 14,610 + 357 = 14,967
14,967 * 24 * 60 * 60 = 1293148800
1293148800 is the time that the start variable should have been set to, which it obviously wasn't.