|
|
|
|
#16
|
||||
|
||||
|
Not to mention the cannons on the bow, especially if they're giving chase!
|
|
#17
|
||||
|
||||
|
About Glitch-Cheating:
Quote:
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. |
|
#18
|
||||
|
||||
|
Quote:
Any why does it take hours to repair a light sloop, anyhow? Your skill with the hammer should generate xxxx points of hull repair per second. A War frigate should take approximately FOREVER to fix with only four people working on it. A light sloop should be able to be repaired, in a minute flat with just a couple pieces of string by one person. 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. 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? Since all crew-matching is still broken (90% of matches are with enemy crews - the rest of the time matching just doesn't work at all) and side-switching is violently encouraged, the natural opposition to such tactics is further hampered. Setting crew on the island takes about a half an hour - by which time your crew likely has four or five separate boats launched out of boredom. Why? Disney hates cooperation to take down the bad guys, and wants to only promote cheating? SvS could have been so cool. These things would have been fixed day one, if they were genuine mistakes. Instead, they are profound reflections of Disney's ethos. |
|
#19
|
||||
|
||||
|
Quote:
Quote:
Quote:
|
|
#20
|
||||
|
||||
|
Quote:
It has nothing to do with intentional cheating or glitching. ![]() Quote:
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
Last edited by Maximvs; 08-07-2008 at 01:29 PM.. |
|
#21
|
||||
|
||||
|
Quote:
|
|
#22
|
||||
|
||||
|
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. |
|
#23
|
||||
|
||||
|
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? |
|
#24
|
||||
|
||||
|
Quote:
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. |
|
#25
|
||||
|
||||
|
Lagging for lightening or fury??? Ya know, some days I lag in svs no matter what. I have sailed into scrums with a single ship and locked up on relatively quiet servers - and other days there can be 10 vs. 10 and nothing slips or is delayed one iota.
I've even had days where we would jump from server to server en masse and still have problems. You can spend all your time getting worked up about it - or, realize it's a game that is supposed to be fun! If it gets to be like a bad day on the golf course, then it might be time to read a book. |
|
#26
|
||||
|
||||
|
Quote:
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. Quote:
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. Aye, matey! Now that is some sound advice. Fair winds! Last edited by Maximvs; 08-08-2008 at 02:56 AM.. Reason: Dont Ya Hate Trying To Triple Quote? :) Just Merging The Three Together |
|
#27
|
||||
|
||||
|
I do think thier gaming/graphics engine could use some rewriting, I spent 2 hours on one of those "other" pirate MMORGs last night, graphics were way better, didnt once even consider the word lag. As beautiful and smooth as it was, I still had to quit and play 2 hours of POTCO last night. hehe POTCO would be awesome with those graphics, and being smooth.
Then again the install of the referenced 'other game' was 7gbs+!!! |
|
#28
|
||||
|
||||
|
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.
|
|
#29
|
||||
|
||||
|
Quote:
As for others, it's all in stride - as you say it really is only a message board (which at the end of the day - I turn off and deal with an 11yr old in soccer, building this monster of a deck on my house, and figure out how oil prices got so high - or maybe not hehehe )But as I read a lot of messages every day - I wish I had more time to respond in them all (unlike that Zep guy that seems to have ALL kinds of time on his hands LOL ) The only thing is that in reading so many, some people you get to know more through their posts (such as Jim and The Monk when they were here were always good for a big thread discussion ).You are one of only a few I've actually ever met 'in game', and for the hour or so we played was a good time where I know a 'less stressed' Edward exists I just wanted to make sure you were still here on planet earth and not totally losing it
|
|
#30
|
||||
|
||||
|
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. |
|
|