Open TeoTwawki opened 3 years ago
Good first issue: look inside battlefield.cpp at entry when we send out the timer packet. We should also be sending that out again on time updates. Notice that we send an empty timer packet to remove the timer (I think)
It also sends the full time value when entering after the battlefield has been initiated. So players who enter after the first one have their timers off by a little bit. If you wanted (or the battlefield was started while someone was afk and they entered 3 minutes late 😔), their timer would be 3 minutes off. It should send the current remaining time to subsequent entrants.
While thinking about this, can anyone confirm that the timer starts while an event is rolling for the first player to enter? I would assume yes
Additional Information (Steps to reproduce/Expected behavior) : Battlefields that show the countdown clock in the top left corner do not get updated if the time is modified (time extensions) in any way. Chat log messages do function correctly with the updated time however, so this is a missing cosmetic feature and not a bugged time remaining. It will reach zero, stop, and then you will still have however many minutes/seconds remain before being kicked out.