Closed GoogleCodeExporter closed 8 years ago
what happens is any time a siege date falls in the past, the table stops
updating completely. The quick fix is to just set all sieges you want active
to a future date, then after that they will work fine.
The code should probably be smarter about working with dates that fall in the
past though
Original comment by tric...@gmail.com
on 3 Jul 2011 at 7:16
I'm going to close this. I'm not sure if this is entirely by design, but the
"fix" is known, and I also kinda like it as is because it makes it super easy
to disable sieges or activate them one at a time as you're ready.
I think its something most servers want to give a personal touch on anyway (the
schedules)
Original comment by tric...@gmail.com
on 3 Jul 2011 at 8:12
Original issue reported on code.google.com by
Nuijen...@gmail.com
on 2 Jul 2011 at 1:53