Important information about port battles re-assignments after server crashes

[Ink]

Captains,

The current Port Battle re-assignment system works as follows:

• A Port Battle is re-assigned to the time the server is restored (live)
• Example 1 
  • A Port Battle was planned at 15:00
  • Server crashed at 14:00 and restored at 17:32
  • Players can join the Port Battle right away at 17:32 despite the timer is still shown as 15:00
• Example 2
  • A Port Battle was planned at 15:00
  • Server crashed at 14:58 and restored at 15:20
  • Players can join the Port Battle right away at 15:20 despite the timer is still shown as 15:00
• Example 3
  • A Port Battle was planned at 15:00
  • Server crashed at 15:20 during an ongoing battle. Server is restored at 16:00
  • Players can join the Port Battle again right away at 16:00 despite the timer is still shown as 15:00 (All ships lost in the previous battle are restored).

PS: Please post here in comments if you prefer the rescheduled port battle to happen the next day instead (at the time of original port battle)

[Guest]

We have no idea WHEN the server will be restored. We cant all linger by our computers for a half day waiting for the moment it comes up to jump into a PB that starts immediately. 

Any pb simply needs to get resceduled to the next day at the same time. 

[z4ys]

shouldnt it be delayed to the next day? I mean who wants to sit in front of the pc and check server status every min?

[admin]

10 minutes ago, z4ys said:

shouldnt it be delayed to the next day? I mean who wants to sit in front of the pc and check server status every min?

Usually the crashes are recovered within 15 -20 mins. Long crashes are rare (black swan events). We assumed that if crash is recovered fast players would prefer to have the battle right away. 

[z4ys]

Just now, admin said:

Usually the crashes are recovered within 15 -20 mins. Long crashes are rare (black swan events). We assumed that if crash is recovered fast players would prefer to have the battle right away. 

I agree on that but if the crash is over a certain timeframe lets say 30mins or 1h the battle should be rescheduled for the next day. But thats my opinion.

[Sverne]

You know what they say about assuming.

 

[Guest]

The crash that cancelled salina point lasted 6 hours or more didnt it?

[Corona Lisa]

20 minutes ago, Ink said:

• Example 1 
  • A Port Battle was planned at 15:00
  • Server crashed at 14:00 and restored at 17:32
  • Players can join the Port Battle right away at 17:32 despite the timer is still shown as 15:00

Players have to sail to the PB, deal with screening etc... In this example the attackers basically lose 1 hour which means autolose in 90% of the time (10% only if all attackers instant log in after server is up again, they have a port close and will dominate the battle)

[Gregory Rainsborough]

I don't even think it should be the next day though that is better than what it currently is now. I remember on Gold Ship Day having to do a port battle twice. Yes, it was annoying but the amount of time people take to organise port battles etc I think it's unfair on the defender to have to spend more time out of their day the next day through not fault of their own and the attacker has the advantage of extra time.

A chance should be given for the attacking clan to grind hostility in the same hours as the previous day so they have a chance for a successful flip.

Just automatically giving the attackers another port battle would favour them too much.

[Farrago]

@admin is there a way to have it conditional? For example of the server is down > 15 minutes the PB is rescheduled, < 15 min the PB continues.

[Lord_Drax]

4 hours ago, Flinch said:

We have no idea WHEN the server will be restored. We cant all linger by our computers for a half day waiting for the moment it comes up to jump into a PB that starts immediately. 

Any pb simply needs to get resceduled to the next day at the same time. 

Completely agree with this as far as us player base is concerned. But I would even take it a step further. If hostility raising is interrupted by server instability that window should be extended as well to give both the attackers and defenders a chance. The previous situation with Little River where the French would start hostility, sink a few ships, server crash, players would get kicked out and thus raise hostility on port, rinse and repeat 5 times isnt fair to defenders. Any and all hostility should be paused and window extended as long as server instability is present.

[Archaos]

5 hours ago, Ink said:

Example 3

• A Port Battle was planned at 15:00
• Server crashed at 15:20 during an ongoing battle. Server is restored at 16:00
• Players can join the Port Battle again right away at 16:00 despite the timer is still shown as 15:00 (All ships lost in the previous battle are restored).

 

If the server crashed 15 minutes into a port battle, where would people rejoin? would it be in the battle instance or outside? Would they still be limited to the join delay after log on? Or if they rejoin in the instance then surely the ones that appear first will have an advantage and you will get people joining to find themselves already sunk.

Unless you can guarantee that all players join at the same instant and are all able to operate at the same time then it is not wise to allow a port battle to continue like this as a minute difference could be huge in terms of damage taken.

[cztim]

5 hours ago, Farrago said:

@admin is there a way to have it conditional? For example of the server is down > 15 minutes the PB is rescheduled, < 15 min the PB continues.

This would be the best option.  Expecting people to sit around and hit refresh for more than 15 minutes is not reasonable.  If a conditional system can not be integrated, it would be best just to postpone to the next day.