An evening of combat logging with a surprise ending

Long story short, I recently purchased a clipper because I was tired of CMDRs escaping my python....... And the game changed for me
-
Today I decided to hit hard against the federation capital for Hudson to find some brave CMDRs to fight, I left well alone the babies with thier harmless of mostly harmless and went after some pythons, to my surprise I managed to outmanouvour them so easily and win 4 battles against different CMDRs, but as soon as their shields dropped.......they all all combat logged, frustrated I met another python who told me that one guy had been doing it for days, I caught up with said CMDR who kept combat logging on people and he decided it would be fun to keep interdicting me over and over and logging off a few seconds after we drop out of SC
-
-
Well I reported them all, when I asked the guy why he combat logged, he actually asked me what combat logging was, and then while I explained he said he's always done it and never got banned and that it's a cool way to escape death (by his way of speaking, and total lack of combat skills I believe this was his first few times in open)
-
I managed to follow him into a wake, when I saw him under attack by a vulture from which he lost his shields and combat logged.....against an NPC
-
I was about done for the evening when I got interdicted again, so I submitted and expected the python to be logging off again but it was a fer de lance, which turned out to be one of the best fights I've been In, so it has a happy ending.....ish
-
 
Last edited:
Interesting, so that CMDR was not even aware he was using an exploit that is basically the equivalent of a "cheat".

That's really interesting to note, thanks for sharing.
 
He he he...The Clipper seems to be all the rage at the moment after the change in the rank needed to buy it. I think you need to find better players in Pythons to fight though, as the pythons that I wing with, as well as various enemies with pythons I've faced, send most clippers and FDL's running. But they don't always send vipers running - that's what I love about this game :) Also, you sound like a very skilful commander, so I'm not saying you would not defeat the aforementioned pythons :)
 
ED should really leave your ships in game until it is no longer considered to be "in combat" for at least 10 seconds before removing the ship from the game actual. This is a feature in literally every MMO.
 
He he he...The Clipper seems to be all the rage at the moment after the change in the rank needed to buy it. I think you need to find better players in Pythons to fight though, as the pythons that I wing with, as well as various enemies with pythons I've faced, send most clippers and FDL's running. But they don't always send vipers running - that's what I love about this game :) Also, you sound like a very skilful commander, so I'm not saying you would not defeat the aforementioned pythons :)

Thanks, some of those fights were not easy though, one of them we both lost our shields at the same time and he then just sat there for a few seconds before dissapearing, took a few nasty hits in a few is those fights
-
I usually fly a python and find the same thing, I only ever had trouble with other pythons and anacondas, felt like setting myself a challenge and fly the clipper for a while, it's much more intense when I know I can't take a pounding like my python can
-
I also recorded most of the loggers, but as I can't name and shame here I will upload it for FD to view if it helps
-
And the guy in the fer de lance was very good, it was pretty much a draw as he ran after a good fight but I couldn't hold out much longer anyway , it was really tough against him
 
Last edited:
I wonder if denying knowing about it is an attempt to get away with it. I mean it makes sense if it wasn't so obviously an exploit. I mean who does that without knowing...
Like, honest officer, I didn't know stealing was a crime.

Also a good trick with combat loggers is to stay in the same patch of space for a while aiming at where they left.. More often than not they'll appear again in 2-5 minutes time when they re-enter the game. Since they are still loading or just entering the game if they are not paying attention you can get a good free hits on them as payback while their shields are still down.
That is unless they re-load in solo/group until shields re-charge but you'd be surprised how many go straight back to open just assuming their attacker will have left.

Well done for reporting, I often don't have recording software running but shadowplay always helps :)
 
Last edited:
FD really need to come up with a system that notes and auto bans frequent abusers. Having to report every player that does it is a joke.
 
Last edited:
ED should really leave your ships in game until it is no longer considered to be "in combat" for at least 10 seconds before removing the ship from the game actual. This is a feature in literally every MMO.

Actually the game itself do exactly this. There is 15 seconds timer, if you want normally log out from the game and there is hostile target somewhere around you.

BUT, because the whole game is based on P2P networking model, the whole "fight" is actually running on clients and not on some central server. So, you can "combat logout" simply by killing the running game process via Task Manager. Or by pulling your networking cable from computer. Or, if you are running the game in window, you can simply close the window. In such case, there is no timeout and FD can't do anything against it. It is simply not possible from technical point of view.
 
Actually the game itself do exactly this. There is 15 seconds timer, if you want normally log out from the game and there is hostile target somewhere around you.

BUT, because the whole game is based on P2P networking model, the whole "fight" is actually running on clients and not on some central server. So, you can "combat logout" simply by killing the running game process via Task Manager. Or by pulling your networking cable from computer. Or, if you are running the game in window, you can simply close the window. In such case, there is no timeout and FD can't do anything against it. It is simply not possible from technical point of view.

True, the only solution I can think of is an automated script that logs how many times and how frequently you disconnect while enaged in combat with another CMDR, the game already detects combat (log out timer) and knows when you disconnect from the game, so it's entirely possible to track their activities and should they disconnect more than is acceptable (like everytime their shields drop) then FD could investigate and punish them accordingly
-
Pretty sure that could be done as FD have game logs and the game even says when someone on your friend list disconnects, so if they are doing it 10 times a day and there is a patten (like they were in combat every time they logged off then this would raise red flags)
 
Last edited:
FD really need to come up with a system that notes and auto bans frequent abusers. Having to report every player that does it is a joke.
I am affraid that this is not possible. Although I am a Solo player, I understand that combat logout is a pain in the bottom for multiplayer.
Problem is, that FD can try to monitor, but because the same situation (combat logout) can have a lot of "normal and legitimate" reasons (like Internet connection loss, connection overload, game crash etc.) it is almost impossible to prove bad intention.
 
Last edited by a moderator:
ED should really leave your ships in game until it is no longer considered to be "in combat" for at least 10 seconds before removing the ship from the game actual. This is a feature in literally every MMO.

They can't, not with the current P2P system which they have no plans of really changing. Also, FDEV keeps avoiding the question about whether CQC is going to use this current system also. I'd give it 98% that it will.
 
Actually the game itself do exactly this. There is 15 seconds timer, if you want normally log out from the game and there is hostile target somewhere around you.

BUT, because the whole game is based on P2P networking model, the whole "fight" is actually running on clients and not on some central server. So, you can "combat logout" simply by killing the running game process via Task Manager. Or by pulling your networking cable from computer. Or, if you are running the game in window, you can simply close the window. In such case, there is no timeout and FD can't do anything against it. It is simply not possible from technical point of view.

hm, if the game is run on a P2P networking model then im afraid we're stuck with this. Unless one day FD kicks up enough of a playerbase to allow for centralized servers. Come to think about it, aren't P2P networked games especially susceptible to hacks?
 
[...]
I was about done for the evening when I got interdicted again, so I submitted and expected the python to be logging off again but it was a fer de lance, which turned out to be one of the best fights I've been In, so it has a happy ending.....ish
-
Appreciate, very good fight indeed :) I'll always try to run if I can't hold out any longer, but I'll never log. Thats just stupid and silly.
 
True, the only solution I can think of is an automated script that logs how many times and how frequently you disconnect while enaged in combat with another CMDR, the game already detects combat (log out timer) and knows when you disconnect from the game, so it's entirely possible to track their activities and should they disconnect more than is acceptable (like everytime their shields drop) then FD could investigate and punish them accordingly
-
Pretty sure that could be done as FD have game logs and the game even says when someone on your friend list disconnects, so if they are doing it 10 times a day and there is a patten (like they were in combat every time they logged off then this would raise red flags)
If it is so simple, FD is already banning. But it is not so simple. Just try to imagine:

FD will ban a user which combat logout frequently.
User wants his money back, because he was banned and claim that this is not his fault, because his Internet connection is crap, game is buggy and always, when his shields drop, he lost the Internet connection.

Try to prove that he is lying and he can't have his money back. With only an average lawyer, user will win his case.
 
I am affraid that this is not possible. Although I am a Solo player, I understand that combat logout is a pain in the ass for multiplayer.
Problem is, that FD can try to monitor, but because the same situation (combat logout) can have a lot of "normal and legitimate" reasons (like Internet connection loss, connection overload, game crash etc.) it is almost impossible to prove bad intention.
If your connection is always failing during combat with players, I don't see the problem in giving them a temp ban from open. Whether it's legit or not, it's a still a problem for others around you.
 
Last edited:
The whole situation is kinda dumb tbh. The 15 second timer is so short that most people accused of combat logging probably aren't, they're quitting legitimately. It should be extended to either one minute, or only when safe. What's so hard about quitting when no hostiles are around? All it would take is a high wake to another system and then dropping into normal space. But at the end of the day, this is a pve game with pvp hammered onto it. Which is why it won't get fixed.
 
hm, if the game is run on a P2P networking model then im afraid we're stuck with this. Unless one day FD kicks up enough of a playerbase to allow for centralized servers. Come to think about it, aren't P2P networked games especially susceptible to hacks?
Of course it is. AFAIK, there already are hacks like inpenetrable shields, unlimited ammo etc.

Main problem is, that ED should never be a multiuser game which allows PvP. The whole design is basically single user game with networking subsystem more or less OK for cooperative PvE gaming for a group of let's say 2-8 friends.
 
Anyway, even most skillful commanders, not combat logging, would simply high-wake high or twice.
While combat logging is an instant exploit, "legally" high-waking is a matter of 15 seconds.
Death is a choice in this game (when you know what you are doing and did not make stupid choices), which makes some activities such as bounty hunting, simply not viable.

If you think I am wrong, please let me know your thoughts since it is the very reason i have not tried PvP bounty hunting so far.
 
Last edited:
Back
Top Bottom