Jump to content
Naval Games Community

Recommended Posts

Posted
28 minutes ago, Tiedemann said:
9 hours ago, admin said:

Nations who used fake battles to create cooldowns have called this upon themselves. Thank them for this.
RVR will only become better as a result. 

 

I don't think it's fair to point the finger at an entire faction

 

  • Like 1
Posted
14 hours ago, admin said:

next day they can start hostility
in 1 day the can have a port battle
so 2 days minimum anyway. 

 

I think we can say for sure this is NOT working as intended.

2 examples from the map today:

1) La Blanquilla, captured by Prussia: No cooldown. And presumably timer still cannot be set until after first maintenance. Hence, tomorrow it has no timer and can be flipped from 11-08.

2) Road Town defended by Sweden today at ~05:30. New PB set at 06:24 tomorrow - 25 hour later, because there's not even cooldown the day the PB happens.

The fact that these critical flaws were anticipated and described by the community before the hotfix, and yet was not addressed, is kind of concerning.

  • Like 10
Posted (edited)
40 minutes ago, Anolytic said:

I think we can say for sure this is NOT working as intended.

2 examples from the map today:

1) La Blanquilla, captured by Prussia: No cooldown. And presumably timer still cannot be set until after first maintenance. Hence, tomorrow it has no timer and can be flipped from 11-08.

2) Road Town defended by Sweden today at ~05:30. New PB set at 06:24 tomorrow - 25 hour later, because there's not even cooldown the day the PB happens.

The fact that these critical flaws were anticipated and described by the community before the hotfix, and yet was not addressed, is kind of concerning.

This change has made abundantly clear the fact the developers do not play this game.

 

Using a chainsaw to fix a problem which required a chisel....

Edited by Isaac J Smith
  • Like 1
Posted

To overcome the shortages of this hotfix. the community could agree on not flipping a port, which had seen a PB, again until the maintenance. if its clear to the whole community that this is not helpful.

Posted
17 hours ago, admin said:

 

Just agree as a community to focus on the nations that used to create artificial cooldowns. Make them pay. We untied your hands. You are now the tribunal

Once you get it out of your system we will have the new ruleset ready. This change is purely done to help you be the judge yourselves.

You, um, watched to the end of the movie right... and understand that the moral of The Purge is that anarchy and vigilantism DON'T solve our problems, right?

Posted (edited)
2 hours ago, Drugie said:

To overcome the shortages of this hotfix. the community could agree on not flipping a port, which had seen a PB, again until the maintenance. if its clear to the whole community that this is not helpful.

Or we can do the opposite to make it abundantly clear to the devs how broken this is.... (and perhaps just no show?)

 

Seriously... I really don't get why this change happened. all that needed to happen was have either a shorter cooldown or no change until their updated mechanic was ready. This is just complete anarchy now.

Edited by Isaac J Smith
Posted
18 hours ago, admin said:

The goal is to give clans a chance to punish those who were hiding behind fake cooldowns. This is not a permanent change. The change in RVR port battle set up will be in coding next week. 
 

As someone who does not involve himself in RvR, thank you for this gift. I expect that the salt in global will flow like never before. 

  • Like 1
Posted (edited)

GG @admin

 

Just killed the game for any nation that can't field a PB fleet in all timezones. Whilst this change might be fine for some of the larger nations (mainly Sweden, Russia, GB who can have PBs basically 24/7), it basically kills any chance we in DK-NG have of doing anything. If we were to take any port now, the enemy will flip it at 0500 when they know we can't mount a reasonable defence. Not adding a cooldown for successful port captures (disallowing us from setting a timer) has just completely ruined any point in attacking any port. Cooldowns are necessary to prevent burnout, and right now I have 0 motivation to continue RvR in this broken system.

image.png.d79af7d15d0009c168d9a3940f540d6a.pngimage.png.7218bf8afe15b588115b6461a735f2ea.png

Prussia took these 2 frontline ports yesterday, and unless they can mount a defence 24/7 they have no real way to prevent the enemy from taking it back at some obscure time when everyone is sleeping.

PLEASE you MUST revert this cooldown change until you actually have the replacement system ready to go.....

Edited by Isaac J Smith
  • Like 7
Posted (edited)

I'm amazed how this can't be reason enough to revert the changes.

be6f6c6540939f8dc0cb76f9a4e37b2a.png

Edited by Liq
  • Like 15
Posted
23 hours ago, admin said:

The goal is to give clans a chance to punish those who were hiding behind fake cooldowns. This is not a permanent change. The change in RVR port battle set up will be in coding next week. 
 

Sorry, is a very bad idea....

Posted
On 3/20/2020 at 4:12 PM, admin said:

Once you get it out of your system we will have the new ruleset ready. This change is purely done to help you be the judge yourselves.

so what about outlaw then? long lost mechanic perfect use to police ourselves, long lost mechanic and logical to have it in the pirate nation, it will never be proper pirates where the lawless are when you cant steal from whoever you want.

  • Like 2
Posted

Still wondering when the group join issue on the PVE server will be fixed. I have made 2 reports regarding this issue and not once has an admin replied to it. Multiple players on the PVE server have mentioned this issue but will not bother coming to the forum to report it. Is this actually a bug or is this working as intended? If it is working as intended then I would suggest lowering the fleet sizes on the PVE server as going after anything over +6 would be suicide for the person tagging the target.

  • Like 1
Posted

@admin I think as the game currently works, we need 48 hours/2 days of cooldown as before. Now with 1 day of cooldown, clans cannot set timers on captured ports. That means they will be flipped out of our planned timezone of attack, and we will lose the ports. Even tho you have commented, that frontlines should be under constant attack. It should not be a game feature, that we have to get up outside of our timezone to play a pb. Just because we could not set a timer.

  • Like 2
Posted

It would be nicen if u just have a cooldown for 1 maintenance means cap a port 1 maintenance and then just a cooldown to the next one so u have 1 day time to set a timer

Posted
3 minutes ago, Nixolai said:

@admin I think as the game currently works, we need 48 hours/2 days of cooldown as before. Now with 1 day of cooldown, clans cannot set timers on captured ports. That means they will be flipped out of our planned timezone of attack, and we will lose the ports. Even tho you have commented, that frontlines should be under constant attack. It should not be a game feature, that we have to get up outside of our timezone to play a pb. Just because we could not set a timer.

That will effectively make it a 3 days cooldown though

Eg.

Pb timer 17-20

Day 1: pb gets set 19.00, pb fails

Day 2: cooldown

Day 3: cooldown

Day 4: Port can be Attacked at 19.00; adjudting timers though at prior maitenance to e.g. 14 - 17 puts it on another day of cooldown til maintenance

Posted
13 minutes ago, Nixolai said:

@admin I think as the game currently works, we need 48 hours/2 days of cooldown as before. Now with 1 day of cooldown, clans cannot set timers on captured ports. That means they will be flipped out of our planned timezone of attack, and we will lose the ports. Even tho you have commented, that frontlines should be under constant attack. It should not be a game feature, that we have to get up outside of our timezone to play a pb. Just because we could not set a timer.

1. Hostility
2. Port battle - Contested state
3. Day after - to set the timer (still invulnerable)

You have to set the timer next day after port battle.

Posted
19 hours ago, Spikes said:

Uhh...seems like you're wrong. Can't set a timer when the port is contested. Are ya'll hiring?

Any time after of course. Are you trolling? Let me help you avoid doing it from now on.. 

Posted
On 3/21/2020 at 1:36 PM, Liq said:

I'm amazed how this can't be reason enough to revert the changes.

be6f6c6540939f8dc0cb76f9a4e37b2a.png

Lesson is simple

  • PvP communities try but cannot self regulate because if you could - we would see no port battles as the votes show. Someone breaks down all break down.
    • If this is true how can we cannot really rely on votes - if the action show that you want to ruse, flank, create distractions (fake port battles), exhaust the enemy? 
  • PVP communities should embrace the developer as a partner and should stop distancing to another side of the battlefield.
    • You cannot have a pleasant combat experience without us.
    • And you should start asking instead of voting.
      • Ask what you want - instead of telling us what to do. We wont do what you tell us to do. but might give you what you want instead by other means.

 

On the port battles the fix is in the works. But everyone must prepare for the forthcoming storm. There will be more PVP and more RVR. 




 

×
×
  • Create New...