Admiraal Mitholyn Posted May 1, 2016 Share Posted May 1, 2016 Dear Devs, We as the United provinces have a major bug to report. We have a lot of ports which had timers set been reset to anytime. We know for certain that we had decent timers put on them mostly 18.00 - 20.00 server time. How come all of the sudden the ports are set to anytime without the lord protectors resetting them? Link to comment Share on other sites More sharing options...
Ink Posted May 1, 2016 Share Posted May 1, 2016 Captain, could you name a few to investigate? Link to comment Share on other sites More sharing options...
Admiraal Mitholyn Posted May 1, 2016 Author Share Posted May 1, 2016 List of Ports that are on the anytime capture window: Willemstad: Capital (logical) Mitara: Transferred from pvp 1 Sinamaica: Transferred from pvp 1 Captured ports and lord protectors: Scarborough: Tweakymercury7 La Blanquilla: Dynagrum Fort Zoutman: Smellybeard Yaguaraparo: NLguinnessNL Cabo de la Vela: Skinner Santa Marta: NLguinnessNL Barranquilla: NLguinnessNL Cartagena de Indias: De gouden Leeuw The ports we captured all had a timer set from 16.00 to 18.00 server time or 18.00 to 20.00 server time. This because it's the prime time of the dutch nation so we are able to defend and people can actually attack the ports on these times. All of the above players are recentley active with the exception of Skinner and De Gouden Leeuw, but these 2 captains still have their accounts on the server so it's not the removal bug. (if a player removes his account the port goes to anytime). Hope u have all the info u need, if u need more then ill be happy to provide it. ps. Some of these ports are given new timers when we found out today, so tommorow 2-5-2016 the timers will be present after maintance. Link to comment Share on other sites More sharing options...
Admiraal Mitholyn Posted May 10, 2016 Author Share Posted May 10, 2016 and is there any update about this problem? Link to comment Share on other sites More sharing options...
Ink Posted May 10, 2016 Share Posted May 10, 2016 We are investigating the issue. The current workaround is to set desired time from "anytime" again Link to comment Share on other sites More sharing options...
Recommended Posts