Privateering: repair while sailing - glitch/cheat

[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