I think this is a good example of the kind of humour that passes you by. What happened to you man? You used to be cool![]()
Now you're getting into the spirit!
I think this is a good example of the kind of humour that passes you by. What happened to you man? You used to be cool![]()
He's still cool
Gentlemen, what I propose is a studied and rigorous discussion of the actual elements of clogging dissuasion that FD have already imposed and how they could be made more robust and selective.
They introduced a big stick with the "IP changed mid-session" disconnector, but the cloggers using that particular workaround were not affected in the slightest, and heaps of peeps on low-lease transients got hit big time and many left the game, not for anything they did, but for what was done to them for reasons completely beyond their control.
Now you're getting into the spirit!
But that's hard![]()
As I stated on the other thread with the video, if you are not completely harmless combat rank and have some spare honour, you do not need to rely on the 15 sec logout. You simply do not log out and face your rebuy. It is called fairness in sports. Otherwise go back to your mama
If Fdev ever does something about the situation, such as dramatically increase the menu timer, or disable the ability to gracefully exit the program when taking damage for instance, is everyone who is currently championing menu logging as being fair going to gracefully abide here on the forum? Sandro has brought it up before, so that's not exactly an impossible scenario someday in the future.
What floors me about all of this is that 2 or so years ago, Rinzler published the git gud guide to trading in open. Title of the video aside, it perfectly demonstrated for players a detailed and near flawless procedure for escaping from combat scenarios without having to log in any way.
The video has been posted and referenced and reposted and rereferenced again and again and again. Beleaguered players ready to quit the game have been directed to the video, taken in the instructions, and with them rose from the ashes like phoenixes, happily proclaiming how much they now enjoyed open play and the prospect of being attacked.
It has worked for me time and again. Badly outgunned and out numbered... I've made clean escapes in everything from vipers to Asps to diamondbacks to pythons and even my big dumb T-9. And when I say clean, I mean maybe a shield ring down, if that.
Despite all of this, there is still a large portion of this community that flat out adheres to the idea that the only way to escape from and annoy their attackers is to combat log.
Frankly, I find the mentality to be pathetic.
Honour will get you killed.
I quite like organised or spontaneous but agreed fights, usually one concedes rather than going all the way to ship destruction ime and it's a good way to make friends & test a build.
But there is no room for complacency or trust that some rule of honour will be upheld. Play to your own rules, don't expect (or demand) others stick to your rules too.
I think you can legitimately blame Microsoft and Sony for that one, they do seem to like to keep their on-line gaming services separated from each other (in addition to the general PC/Mac/Linux gaming platforms).And don't say CQC... xbox average wait time is listed in decades atm.
At least I will die with honour.
Likewise - I would prefer pre-agreed PvP to random no-comms kill encounters. That would be great. I would probably then never have to indulge in something which I have no interest in doing. And exactly why I have never and probably will never open CQC. (Never say Never, of course - it is a possibility that I might Open CQC sometime. But in all probability, probably not.)
I don't expect other players to play by my rules at all.
That would be to expect others who min-max their PvP meta-builds to also possess some honour. Sadly, from experience, those appear to be mutually exclusive concepts. (see above.)
Slainte Mhath
Mark H
I agree that 'most' is hyperbole, however a large number of pvp players are quite knowledgable and will be glad to offer tips on avoiding death. The issue is that most people communicate to said 'murderer' in less than friendly terms.
There are a number of us that are more than happy to help players. There are also some that are more than happy to say they will help and then just kill you again.
Bears do give the best hugs afterall...
There is a vast distinction between "some" and "most" and a very visible disconnect between what some PvP players see as "being friendly and helpful" and the reality, in my own experience, of how many are actually friendly and helpful in the game.
As long as the plug can be pulled, there is nothing that can be done.
They could better enforce the rules against doing so.
The act cannot be made impossible and keeping a ship in an instance after a client disconnects is not practical, but keeping an eye out for such patterns and making examples of people who engage in prohibited behavior would remove some of the most flagrant violators from the game, and deter many more.
They could better enforce the rules against doing so.
The act cannot be made impossible and keeping a ship in an instance after a client disconnects is not practical, but keeping an eye out for such patterns and making examples of people who engage in prohibited behavior would remove some of the most flagrant violators from the game, and deter many more.
I do agree. It is my personal opinion, that if reported with included evidence of 'disappearance' prior to an obvious death, either by log, a series of screenshots, or video, that these should be actioned on a 'strikes' basis over a period of time.
The reason it needs to be strikes is because one incident is not actionable, due to lack of proof of whether a plug was pulled or a genuine unscheduled connection outage occurred. It also needs to happen during a set period as three combat disconnects in a year is not an issue, but in a week or even a month it could be.
If I were in charge of implementing this, my first draft would be something like this.
If you see someone combat log, gather all the evidence you can in the form of log files, screenshots or video where possible. We will also try to determine from instance logs, the likelihood of this being a deliberate disconnection. When a user is reported for this, they get a 'strike'. 3 strikes in a 30 day period results in a ban from Open Play for a duration of 1 week. Repeat incidents increase the duration of the ban.
Having said all that, it depends on Fd's willingness to call people liars and face the potential consequences of doing that.