Privateering: repair while sailing - glitch/cheat

[whiskey]

Originally Posted by Edward Edgemenace

The light sloop - which can have a maximum valid crew of three people - has four repair spots. It is ludicrous to suggest that one might be closer than the others at one time, but less convenient at another time. Just a couple steps in any direction, and you are on the other side of the boat. So why does a light sloop have four repair spots? Because glitch-repair is considered essential to Disney. That is, cheating, to them, is much more important than playing the game.

As to this point, if you read the in-game notes, the location of the repair spot directly repairs that portion of the outer hull first. For example, if you have damage to the right side of the boat, the right repair zone will fix sooner/faster. I have tried this, and it works to a point.

[mlratto]

the effects of thunder and fury are simple immobility - 100% inexplicable

why do the people with the highest level weapons even need to cheat like that?

i don't want to pile on but i have not experienced any lag when getting hit by lightning or fury.

do i shoot lightning and fury...heck ya i do. i worked my butt off for those skills so why wouldn't i use them.

I honestly do feel bad for those who get locked up over this but in reality i have no idea which boats out there are ones who will experience it. I'm just trying to play the game by the rules and i use the options that are available to me.

when sailing solo (which i do a lot) sometimes lightning and fury are your best friend.

[Dr. Zeppers]

Originally Posted by Edward Edgemenace

The light sloop - which can have a maximum valid crew of three people - has four repair spots. It is ludicrous to suggest that one might be closer than the others at one time, but less convenient at another time. Just a couple steps in any direction, and you are on the other side of the boat. So why does a light sloop have four repair spots? Because glitch-repair is considered essential to Disney. That is, cheating, to them, is much more important than playing the game.

Actually, the answer to why, is QUITE simple.

Consistency, which is key to any user friendly software applications.

Many have contended that the light sloop has an advantage of size/speed, why should it have an additional advantage of being easier to repair? Because 'realistically' its size is so much smaller? Lets not talk about realistic, because repairing a ship while at sea to 100% its original strength/ability, is in itself not realistic. Lets talk about fair, same for everyone... point blank and period.

As for using Lightning and Fury, sounds like the problem is local (hardware or connectivity, i dont know). Don't see that many other major complaints, and i've never once experienced a problem with it. Like someone said.. we worked hard for those skills, they put them in the game TO BE USED.

[mongo]

I have unlimited access and tried SvS in my War Frigate and I might as well have just painted a big old bull's eye on the sails. I purposely bought a light sloop (and now a regular Frigate) for SvS.

The War ships can take more damage but also attract more fire.

Plus I imagine that there is a certain amount of surprise when the little light sloop parked off your side starts shooting fury and explosive at you. The light sloop was getting pounded a bit too much so I went for the Frigate so I can point the nose at the target and present a smaller profile.

[Sven Niscadae]

Originally Posted by mongo

The light sloop was getting pounded a bit too much so I went for the Frigate so I can point the nose at the target and present a smaller profile.

Not to mention the cannons on the bow, especially if they're giving chase!

[Nautical Nattie]

As far as i know you can still get the repair glitch even after launching at any time, so long as someone takes over the wheel and then the captiain of the ship takes it back again; so it doesn't have to be when you launch. My crew said it happened twice lastnight when this guy kept taking the wheel and i took it back. I haven't yet tested that one out but i think it works that way too. but i'll report both anyway lol

[whiskey]

About Glitch-Cheating:

Originally Posted by Disney Pirates of the Caribbean Website

The Pirates Online Code of Conduct:
Click Here for Website


1. Respect your fellow pirates - Pirates of the Caribbean Online does not tolerate any swearing, cheating, bullying or overt harassment toward other players. Disciplinary action will be taken should any one of these occur while playing.

....

4. No Cheating - Any use of third party programs is not allowed. Players who use any third party programs while playing risk being permanently banned.

Point one uses a broad brush to say that Cheating is not allowed, specifically, cheating that is used against other players. Glitches to this point have been utilized, but their results have not directly affected other players, while this glitch directly changes the outcome of gameplay between clients, be they paying or otherwise.

Point four references outside software cheats, and I think is missing the mark on this point. It is illegal to use outside mechanisms to change the outcome of the game, but this particular glitch is inside the game, and therefore does not apply.

[Sven Niscadae]

Why do cannonballs that land in the water three to ten boat-lengths BEHIND my light galleon, count as hits on my boat? Because I have a high bounty? And yet, if I'm going backwards, cannonballs that hit or skim my bow are not counted as hits.

It's called lag. There is something going on between your client and the server causing latency. It's possible that the server hadn't caught up with your actions and hadn't registered you had moved yet.

Also disappointing, is Disney's handling of lightning and fury. The target boat is rendered stationary, once hit. It is a cheat; unlike grape shot which visibly stuns your pirate with the dizzy animation over their head, the effects of thunder and fury are simple immobility - 100% inexplicable, except to promote cheating. The amount of damage from those weapons is already astonishing - why do the people with the highest level weapons even need to cheat like that?

Please stop making this generalization. Just because this weird bug happens to you doesn't mean it happens to everyone. I've been hit by thunderbolts and fury plenty of times in SvS but never been succumbed to immobility. Don't assume everyone that uses thunderbolt and fury is cheating.

Instead, they are profound reflections of Disney's ethos.

Remember, just because you're paranoid doesn't mean they're not out to get you.

[Maximvs]

The light sloop - which can have a maximum valid crew of three people - has four repair spots. It is ludicrous to suggest that one might be closer than the others at one time, but less convenient at another time. Just a couple steps in any direction, and you are on the other side of the boat. So why does a light sloop have four repair spots? Because glitch-repair is considered essential to Disney. That is, cheating, to them, is much more important than playing the game.

*buzz* The reason for the 4 repair spots is to repair the side of the ship with the most damage. Though the Green Circle only shows three sides (annoying) - you can actually repair one of four sides of the ship - so when you are doing it the legit way and the right side has the most damage - repairing that fix spot first actually shows the meter on that side going up first. Once that side is fully repaired then the repair 'spreads' to cover the enrie circle.

It has nothing to do with intentional cheating or glitching.

These things would have been fixed day one, if they were genuine mistakes. Instead, they are profound reflections of Disney's ethos.

Ya know, I can understand ones fustration with having poor connectivity or poor video or game bugs, so much so that I made the offer to sail with you to experience these options myself (though I did not lock up with you at times) - but being this paranoid about the game to this extent really is overboard.

Almost none of us experience these issues to this extreme (glitching aside of course - we all see it and all agree it should be fixed), and some who do have problems even admit to having computer hardward which just isn't up to snuff. Sure we all experience Lag and I know you experience it more than others - but this not make fault the entire system when it is limited to only a small number of players.

Entire computer configurations can cause issues (motherboard a with video card b = diaster). Where you live, the connection you have (is the next door neighbour filesharing the whole world music collection? Killing your connection in the process?), the hardware you use... its computers. All these things can contribute. Have you tried another computer? Another Location? Another connection? These all must be addressed... and many questions which answers are needed for.

I am only concerned because your issues have gone from yourself and SvS to grouping all of us into this potential diaster for all players over the last several threads / posts - when most of us do not experience these issues (or not to the extremes you have) and cannot be called glitches - these are issues which you need to try and eliminate. I don't ACTUALLY believe Big D is trying to place intentional mistakes just to tourture you.

Now as for the REAL glitches of auto-repair and possible sailing forcefield... yes - these should fixed as soon as possible, and maybe even add options to lower graphic settings on ammo.

Your a good man and a great sailor, I'm only worried that your gonna need counciling and meds if you don't ease up a bit

[Edward Edgemenace]

Originally Posted by Maximvs

<snip>

I am only concerned because your issues have gone from yourself and SvS to grouping all of us into this potential diaster for all players over the last several threads / posts - when most of us do not experience these issues (or not to the extremes you have) and cannot be called glitches - these are issues which you need to try and eliminate. I don't ACTUALLY believe Big D is trying to place intentional mistakes just to tourture you.

Now as for the REAL glitches of auto-repair and possible sailing forcefield... yes - these should fixed as soon as possible, and maybe even add options to lower graphic settings on ammo.

Your a good man and a great sailor, I'm only worried that your gonna need counciling and meds if you don't ease up a bit

OK, perhaps I did go over the top on those last few. Just because you and I had no lockups that one evening, does not mean they went away. The performance enhancements you pointed out made other parts of the game smoother, but seem to have nothing to do with the lockups I've been affected by, the most. With other players, I still get lockups; some people I sail with experience MUCH greater lockups than I do. For example, my best gunner (the one I'd always invite to boss battles) locks up consistently when thunder or fury is in use nearby. But she doesn't have little 15 second lockups like I sometimes do; she was gone for 30 to 60 seconds at a time; other times just disconnected. A couple other game-friends haven't been able to SvS at all. Just today, two more people got locked up on Andoso.

Now, as the days pass, I'm discovering more about the lockups. It is not everyone's thunder and fury, but every time I get a lockup, it is from thunder or fury. (My observations of lag-from-grenades does not seem to be repeatable.) Approaching the same lag-storm boat a second time consistently locks up again when that boat fires thunder or fury. Well, sometimes a light sloop - other times four war frigates - but in both cases, repeatable. Not "random" or "intermittent."

I'll try to keep your kind words in mind, when I find myself getting frustrated by all this again. I'll try to remember that it is never easy to push software changes out, even if the change (turn off some minor feature that causes major disruption) itself is easy. I'll also try to not let some of the editing of my messages get to me - this is just a minor message board, just for a game, after all. But seeing my messages here be edited was very strange - that action itself was perhaps what goaded me over the top, here.

I would like to see these problems fixed. If they rework it, so that EVERYONE has auto-repair all the time, that would be cool. If they rework it, so that noone has auto-repair ever, that would be OK. If they rework it to hide the glitch and make the glitch require one more action to activate, that is not cool. If they do that (as someone said they did with the skeleton glitch,) I indeed, may need medication to curb my comments.

Originally Posted by whiskey

My favorite method is to use the sloop, back up towards a rock, and throw lightning to draw opponent ships towards me. When they are in better range, I pull out the fury. If they close further, I draw out the explosives!

I have not seen the immobilization problem, either. Have you run a tracert to determine latency on your packets to Disney?

Didn't see anything of concern in my traceroute (nor my tracert) but won't put those results here, as I'm not clear on the privacy rules about IPs and city locations. I WILL post this though:

C:\>ping 204.2.148.53

Pinging 204.2.148.53 with 32 bytes of data:

Reply from 204.2.148.53: bytes=32 time=34ms TTL=122
Reply from 204.2.148.53: bytes=32 time=32ms TTL=122
Reply from 204.2.148.53: bytes=32 time=30ms TTL=122
Reply from 204.2.148.53: bytes=32 time=30ms TTL=122

Ping statistics for 204.2.148.53:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 30ms, Maximum = 34ms, Average = 31ms

C:\>
C:\>ping 198.105.196.91

Pinging 198.105.196.91 with 32 bytes of data:

Reply from 198.105.196.91: bytes=32 time=71ms TTL=239
Reply from 198.105.196.91: bytes=32 time=75ms TTL=239
Reply from 198.105.196.91: bytes=32 time=74ms TTL=239
Reply from 198.105.196.91: bytes=32 time=70ms TTL=239

Ping statistics for 198.105.196.91:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 70ms, Maximum = 75ms, Average = 72ms


I fortunate enough to ping the second one during a 15 second slowdown. The result was this:

C:\>ping 198.105.196.91

Pinging 198.105.196.91 with 32 bytes of data:

Reply from 198.105.196.91: bytes=32 time=70ms TTL=239
Reply from 198.105.196.91: bytes=32 time=70ms TTL=239
Reply from 198.105.196.91: bytes=32 time=77ms TTL=239
Reply from 198.105.196.91: bytes=32 time=72ms TTL=239

Ping statistics for 198.105.196.91:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 70ms, Maximum = 77ms, Average = 72ms

Which is to say, network round-trip time was FASTER during the slowdown. No network disconnection. I wasn't doing any major downloads at the time. Other times, I have done large internet downloads while playing, with no noticeable affect on game performance. When it is just the game, network utilization is 0.5 to 1.5 percent. With a simultaneous download it is 49.5%. Network traffic changes when my crew status changes, but not much for regular game vs. privateering.

Now, even though I'd like my ping times to be closer to 10ms, I really can't complain when they are under 100ms. I don't mean to be complaining about minor lag issues - I am seeing occasional major stops. About the light galleon - I find it hard to believe that shots consistently off my bow miss (if going backward,) while shots consistently three boat lengths behind, hit (if going forward.) I don't see that behavior with my light sloop! But that is a minor annoyance, so please forgive me for having mentioned it. The lockups are the problem that make it truly unpleasant, at times.

Originally Posted by Tuefenhandel

<snip>
If it gets to be like a bad day on the golf course, then it might be time to read a book.

Aye, matey! Now that is some sound advice. Fair winds!

[Nautical Nattie]

It's not thunder or fury i have a problem with, it's firebrand lol. I can't do SvS on my PC because it just lags too much (even on quiet servers), but i try it on my dads brand new PC and it's fine, no lags = basically i need a new PC lol. . As for the glitch/cheating thing for repairing, i crewed up with someone once and when i went on their ship they could sail and repair, i thought it was quite cool at first but then i believed it to be just unfair to other players, i rarely play SvS now because there are so many cheaters out there. I don't see why people can't just play the game for a game and not have to get so competative and cheat all the time.

I thought the repair glitch was just lucky for them though, that i can understand if it's accidental, but deliberate - nah ah! Gain respect by getting a good crew and good ammo and beat them the proper way, then you can say you earned your score and bounty.

[Poison elf]

OK, well here is what I can say about this. Ramming speed causes some problems. This glitch, repair, is also what is causing problems. Today entered a server, the entire time locking 15 seconds or so from canon to wheel. Finally found what was going on, after sinking some ships, I started on what I think the culprit was. Start hitting it, lock up , then back and its at full health and no ships sunk. Hit it some more, more lock-ups and health changing back and forth.

Now some may put blame to peoples computers, but maybe you should of been around enough years to see enough things to get a better opinion. I can talk about my end and what is going on with that. From my end, this was NOT happening until this svs came out. Going out and shooting regular ships was NOT locking up until this came out. So the people all gun-hoe blaming others (others computers) should maybe back off and put the blame where it belongs,,,,,Disney. I don't think the number of people having these problems, all of a sudden cut their computers back from what was working yesterday?

It can be argued back and forth is it fury, is it lightning, fire, ramming, or glitch repairing, or just standing around not trying svs. In any way you look at it, its effecting the entire game play and sailing, and is a PROBLEM.

This problem began when,,,hello? Lost of Internet windows started when? Lock-ups started when? These avoided issues is where the problem is from some people here who aren't having problems. Conveniently some of the same people on the test servers. Not having a good base in the testing system to cover all aspects of game play probably the biggest problem. Maybe try testing stuff with experienced players, different computer set ups, instead of just who found a web-site first? Then something needs to be done with the problems instead of the usual "ignore", can I help you with anything else today "button".


Frankly, from posts I have seen here, I really have to wonder how many people knew after weeks testing, these bugs we all have and reported them. Its been live half the time tested or so, and basically unplayable now. As I stated all during testing, maybe something could be brought out instead of protected secrets, so its not mess live pvp in no time. Also said in days Most of us would find this stuff out. Obviously it was more important to have a mess come out instead of something functional.

[Maximvs]

Maybe I haven't had enough coffee yet this morning, so I'm gonna try to give it a shot but might just get tired and get breakfast instead

Originally Posted by Poison elf

OK, well here is what I can say about this. Ramming speed causes some problems <snip>

So your hitting Ramming Speed just off the wheel? (The "then back and its full health has me a bit confused"). I want to test your finding, but its not described enough.

<snip>maybe you should of been around enough years to see enough things to get a better opinion

<snip> Going out and shooting regular ships was NOT locking up until this came out.

<snip>So the people all gun-hoe blaming others (others computers) should maybe back off and put the blame where it belongs... Disney. I don't think the number of people having these problems, all of a sudden cut their computers back from what was working yesterday?

1) Yea, I've been aound enough years. In fact, I wish I could pull a Tina Turner and 'Turn Back Time'...

2) Don't confuse SvS with everyday sailing - there has been no mention of anyone having everyday sailing issues besides the sails on all the ship being up. I've been regular sailing for a few days now and ships sink today just like they did last week. Since SvS is a totally difference experience, how can you know for sure if you would actually have the problem or not BEFORE SvS came out? From some Phantom shooting a few lighting rounds at you? Not likely.

3) No I will not put ALL the blame on Disney.

Yes, I fully agree the discovered bugs of auto-repair need fixing. If Ramming Speed is a bug then it needs to be fixed (though until tested I'm reserved on this one - since no one as actually been rammed on purpose by another ship until SvS appeared, how can one say that 'locking up' is not a part of it? Maybe all the times you rammed NPC ships the code 'freezes' the NPC ship allowing for the hit to take place, and this code is now being applied to the player ship?) Yes, I knew once SvS was open there would be Lag Issues (sent in serveral of my test reports). Yes, their Tech Support bombs...

But no - until you can tell me you have gone to another computer with another configuration at another connection and possibly another location and tried it - I will not put the blame all on them. And the reason being is that I use several different comps to play and test from several locations (as far as 60 miles), and I get different results from all of them.

It can be argued back and forth is it fury, is it lightning, fire, ramming, or glitch repairing, or just standing around not trying svs. In any way you look at it, its effecting the entire game play and sailing, and is a PROBLEM.

Once again, another person overshooting the bounds. It is NOT affecting ENTIRE gameplay! I am still able to do the 'scary mary' quest without an issue. I still helped guilders last night sink ships for what-ever quest on driftwood... stop stretching everything into the whole game falling apart!

The problems you are having are in SvS, and yes there are some problems. And lets stick with that. If you want to talk about the 'flying sargent at padres' or the 'wall glitch at kingshead', or even the 'flying off the ship glitch' - fine - but please stop comparing it all to SvS...

Just because you are upset does not mean everything and everyone in the whole world is now broken.

This problem began when,,,hello? Lost of Internet windows started when? Lock-ups started when?

Search the forums - after almost every update there arre those incliding posts of myself) who have problems. Once again, don't use common issues to make a case against SvS. If there is any hope to actually find the issues and fix them - set you emotions outside and post your issues and your findings (or even better yet - use the ? mark in POTCO and send them directly to Disney - thats what its there for).

These avoided issues is where the problem is from some people here who aren't having problems. Conveniently some of the same people on the test servers. Not having a good base in the testing system to cover all aspects of game play probably the biggest problem. Maybe try testing stuff with experienced players, different computer set ups, instead of just who found a web-site first? Then something needs to be done with the problems instead of the usual "ignore", can I help you with anything else today "button".

Frankly, from posts I have seen here, I really have to wonder how many people knew after weeks testing, these bugs we all have and reported them. Its been live half the time tested or so, and basically unplayable now. As I stated all during testing, maybe something could be brought out instead of protected secrets, so its not mess live pvp in no time. Also said in days Most of us would find this stuff out. Obviously it was more important to have a mess come out instead of something functional.

Now this is a direct quote at me - and I will respond to it.

Since becoming a tester 7 weeks ago - I've sent in 27 bug e-mails, each containing several issues each (so much so that Disney e-mailed me back saying they may not respond to all my messages, but would continue to read them). I used the ? Mark Sign to immediately report findings as I came across them (such as the Rock Island Glitch). If no one uses it - nothing gets fixed. Everyone reading this message should use the ? mark once a day for any glitch they see (even if its only that flying sargent every day at padres... he will stop flying if enough reports come in).

The discovery of auto-repair (the use of F1 to unlock yourself from the repair and keep sailing) would not matter if there were there a 100 or a 1000 testers. We discoverd many other nifty glitches before it come out to live - but theres always going to me one or two more - someone got lucky oneday and hit F1 and they discovered that they could sail afterwards. They told two friends and so-on-and-so-on-and-so-on... This discovery has NOTHING to do with any 'lack of experience' you think I or other testers may have.

As mentioned I used multiple computers / laptops with different configurations in different locals - but unless you own your own lab good luck with that and whatever that web site first comment was about. We are given no timeline as to when things will be released to open, and very little direction as to what to test - its all discovery. I have posted more than once that Disney should wait to release updates - but they set the timelines, not us (in fact the release of SvS surprised me as I had just sent in a bug report only hours earlier...) and we are not even told when its going to be released.

You would have not done any better than we have - and would only be able to do the same thing we do, which is read issues that people post here - test them - then report them.

=============

Now I'll give you the same advice - then take it myself. Once again I can understand some players are fustrated that they are issues when they play SvS and have problems.

Once again, 15 people posing problems here is not the 11,000+ members registered here or however many in the game. Once again I am concerned because your posts as well have gone from yourself and SvS to grouping all of us together - when once again most of us do not experience these issues (leaving out the direct cheats such as auto-repair - I TOTALLY AGREE these need fixing - use the ? Mark in the game! Send it 10 times each time you play! They will respond...).

The model that Disney uses to implement, deploy and test has not changed for years (in ToonTown or other games) and will not change in time to come unfortunately. So when things are not going right - report your findings to them, keep doing it, because their business model really is 'the squeaky wheel gets the most grease' and if they get enough reports then they will make changes - not overnight - but they do make them.

I myself will take my own advice, and go keep building my deck - I'm about a week from finishing and wait to try out my new pool - so no matter what happens in the game - I'm outside

[Edward Edgemenace]

Originally Posted by Nautical Nattie

I thought the repair glitch was just lucky for them though, that i can understand if it's accidental, but deliberate - nah ah! Gain respect by getting a good crew and good ammo and beat them the proper way, then you can say you earned your score and bounty.

I've seen it happen accidentally here and there, but the broad majority of the time, it is intentional - assassinating the captain resets the repair glitch, but they are in the glitch again in a matter of seconds.

How then, do you do your SvS, when there are five zero-point non-cheaters and three high-bounty cheaters on the opposition? You build up your crew, set sail on your war sloop with the repair glitch, or without? Without it, is certain death (if not from the first cheater ship, from the second.) With it, then you can be accused of cheating (by those five zero-pointer ships) even if you try to avoid them.

Just ignoring that SvS exists is silly - it should be (by far) the best part of the whole game.

[whiskey]

My favorite method is to use the sloop, back up towards a rock, and throw lightning to draw opponent ships towards me. When they are in better range, I pull out the fury. If they close further, I draw out the explosives!

I have not seen the immobilization problem, either. Have you run a tracert to determine latency on your packets to Disney?