I guess devs forgot to clear already taken hostlity missions :D

[Yehoodi]

2 hours ago, --Privateer-- said:

That is correct, better now than at release, right?

As i mentioned in my prior post, your guys prove the bug exists once you saw the hostility still active after map wipe, which was a partial game wipe.  

Release will be a full wipe so one can not repeat what happened here.  Either way we thank you for identifying this issue.  

So there is no need to run the PB tonight. 🙂

Edited April 25, 2019 by Yehoodi

[Yehoodi]

btw, nice to see the pirates got Baracoa. 

[--Privateer--]

1 hour ago, Yehoodi said:

So there is no need to run the PB tonight. 🙂

We'll have to sail out to the attackers line to join, do what you will with that info.

[William Death]

11 hours ago, Yehoodi said:

Wonderful, you have identified a bug in the system and now we know what is was - setting up hostility missions prior to a wipe that will remain after the wipe.  Thank you for identifying this bug.  

At the same time though  :-). 

1) At this point no one can repeat what you did as no one can take hostility missions in ports away from friendly ports.

Again though, how would you know that nobody can repeat this? Did you speak with developers and ask them if they plan to wipe missions every time they wipe the map? Because from everything I read, all they said they were wiping was XP, map, and player assets like ships and materials at release. Nothing was said about wiping missions. I assumed they will wipe missions upon release. But assuming things isn't part of a tester's duty.

Obviously, now the bug has been reported, corrected by the developers, and will not be an issue going forward.

So, on behalf of VCO, I'd like to thank the developers for their prompt fix of this issue. And also assure everyone that we will continue to look for, test, and report any possible bugs we find, to prevent them from becoming issues after release.

11 hours ago, Yehoodi said:

2) Now that you have identified the bug, there is no reason for you to take St Marys.  The bug was being able to take missions, not the act of taking the port. :-).

And lastly, if St Mary's is taken it will give a false sense that the Pirates (and friends) can move quickly to the US coast after release, which they will not be able to do after a full wipe as there will be no missions to take day one outside St Marys.  

The only way to truly test the system is to see how it works then adjust.   For example, give dedicated attackable ports to Mortimer town 

Nah, we did the grind, we're taking it. Fair compensation for the grind and effort. We'll continue to explore the new RvR mechanics, using St. Marys as our testing grounds. 

I don't really care what impression it gives to the players, having a black dot on the coast. Taking ports from others and raiding their waters is literally the goal of this game. Also, you can, of course, grind it up and try to take it back, we always appreciate the PvP opportunities.

Don't worry, St. Marys will be in good hands.

Agreed on the final point, Mortimer needs more hostility paths that lead north through the Bahamas.

 

11 hours ago, Bull Hull said:

You conveniently ignore the fact that it should have been IMPOSSIBLE to set that PB per the new PB mechanics.  The only bias I see is the bias some players and some clans and some nations have for cheating every chance they get.

Did you read the explanation for how it happened? It was outlined quite clearly in previous posts. 

TL/DR: It indeed would have been impossible to set that port battle, if the missions had been wiped with the reset. They weren't. So we could set the battle. Thats a bug. Bug report was sent.

Welcome to early access games where we are the testers of mechanics. If players want to play a game where all mechanics work perfectly, they should wait till release. Admin himself has said as much. Until then, its our obligation to test, find, and report bugs. I'm happy to be a part of this process.

Also, be careful about cheating accusations. Accusations without proof is punishable. In a small gaming community like Naval Action, a player's reputation is important. False accusations tarnish that reputation. But, if you legitimately believe and have proof that any players cheated/hacked/whatever, you should tribunal it. Finding and reporting broken mechanics is not cheating. 

Edited April 26, 2019 by William Death
Grammatical error: past tense of grind is ground, I'm a noob.

[William Death]

11 hours ago, Msk said:

Hey boss man you gonna open st Mary’s up? I thibk I know a few folks who wouldn’t mind hanging around out of there for the time being.

In exchange for dank memes, we'll consider it.

[Yehoodi]

1 hour ago, --Privateer-- said:

We'll have to sail out to the attackers line to join, do what you will with that info.

What ships are you bringing?  Just between me you and the lamp post :-). 

 

[--Privateer--]

11 minutes ago, Yehoodi said:

What ships are you bringing?

You thinking we plan that in advance amuses me.

[Yehoodi]

46 minutes ago, William Death said:

Again though, how would you know that nobody can repeat this? Did you speak with developers and ask them if they plan to wipe missions every time they wipe the map? Because from everything I read, all they said they were wiping was XP, map, and player assets like ships and materials at release. Nothing was said about wiping missions. I assumed they will wipe missions upon release. But assuming things isn't part of a tester's duty.

Obviously, now the bug has been reported, corrected by the developers, and will not be an issue going forward.

So, on behalf of VCO, I'd like to thank the developers for their prompt fix of this issue. And also assure everyone that we will continue to look for, test, and report any possible bugs we find, to prevent them from becoming issues after release.

Nah, we grinded it, we're taking it. Fair compensation for the grind and effort. We'll continue to explore the new RvR mechanics, using St. Marys as our testing grounds. 

I don't really care what impression it gives to the players, having a black dot on the coast. Taking ports from others and raiding their waters is literally the goal of this game. Also, you can, of course, grind it up and try to take it back, we always appreciate the PvP opportunities.

Don't worry, St. Marys will be in good hands.

Agreed on the final point, Mortimer needs more hostility paths that lead north through the Bahamas.

 

Did you read the explanation for how it happened? It was outlined quite clearly in previous posts. 

TL/DR: It indeed would have been impossible to set that port battle, if the missions had been wiped with the reset. They weren't. So we could set the battle. Thats a bug. Bug report was sent.

Welcome to early access games where we are the testers of mechanics. If players want to play a game where all mechanics work perfectly, they should wait till release. Admin himself has said as much. Until then, its our obligation to test, find, and report bugs. I'm happy to be a part of this process.

Also, be careful about cheating accusations. Accusations without proof is punishable. In a small gaming community like Naval Action, a player's reputation is important. False accusations tarnish that reputation. But, if you legitimately believe and have proof that any players cheated/hacked/whatever, you should tribunal it. Finding and reporting broken mechanics is not cheating. 

First, no I have not talked with the devs on this matter and it was my assumption that everything will be wiped except for a few things at release.  As with the present issues regarding missions, missions have never been wiped since i came back about 3-4 months ago.  Indeed, I still have my first search and destroy mission along with a handful of the old 3000 dubs group kill missions.  So missions survive wipes.  

To the extent moving forward, the devs will certainly have to wipe all missions at release.

Second, the bug was reported, thank you, but it was not corrected by the devs, as we have a port battle tonight.  A correction would be to bring the game to post wipe circumstances which would be to wipe the port battle (no ports may be attacked till the head county port is taken which you have not done), then the "bug" would be corrected, but only then.  Down the road you guys would of had a port near the US somewhere where you could PvP US players. 

Third, I want to thank VCO and its members for trying this out and doing this for us so that we do not have to worry about it at release, thank you again.  At the same time though you did not have to grind the missions but merely present the still existing mission to the devs and let them know this is not going to work post release. 

Fourth, it is fun to have enemy in and around the coast, so thank you guys again for providing that content.  As the same time though it can get a tad much.  :-).

Fifth, i am not totally disappointed as one might argue that there should be a free port near the US capital.,  If you guys are successful tonight and can keep it , it will provide such a port.  Although It would be nice to have a east coast free of the enemy and have plenty of fighting down around the Cabo/Ays region where US and other could fight. 

Sixth, it is not cheating, but we have a situation where we have a port that is not supposed to be there (if you guys get it) this early in the testing of the new port systems. 

Seven, thank you William for responding to my points. 

 

 

 

Edited April 26, 2019 by Yehoodi

[Yehoodi]

11 minutes ago, --Privateer-- said:

You thinking we plan that in advance amuses me.

 :-), can you send me a PM when you get it :-).