I combat logged a duck last night.

I'm waiting for someone to get upset over the KoS list and call me a psychopath or something like that.

Then when I ask why isn't people screaming at the people who put me on KoS lists for being a pirate, then they go quiet or say that I deserve it because god forbid I play the game legitimately and reasonably.

*Chuckles in the background*

I thought about making a comment about the KoS, but that would have been boring. But if it entertains you a bit:

Why are you so obsessed with KoS lists?
Why do you think that putting a combat logger on a KoS list would change anything other than motivating that combat logger to combat log even more?

Have fun :)
 
And an actual valid disconnect or machine hang or reboot? Which is probably more common than combat logging?
That would, unfortunately, be par for the course.
I suppose FD could implement a feature to challenge it and their support team could investigate it (though it's not a very feasible solution).
But in WoW for example, if I'm in combat and get DC'd .. I can die .. it happens.

Edit: Perhaps a "reconnect" timer. If you reconnect within a certain amount of time, you are restored to your last known location.
 
Last edited:
I thought about making a comment about the KoS, but that would have been boring. But if it entertains you a bit:

Why are you so obsessed with KoS lists?
Why do you think that putting a combat logger on a KoS list would change anything other than motivating that combat logger to combat log even more?

Have fun :)

The thing is that combat loggers mostly believe what they're doing is legitimate or that they think FD won't do anything about it (probably right at this point, or that we just don't know because they are big on no name and shame). So to prevent them from ruining other players' experience, they need to be removed as soon as possible upon encounter. Not to mention high profile combat loggers (that get reported a lot [not accusing anyone of being a logger]) do seem to receive punishment accordingly, so basically it's win-win.
 
Last edited:
The thing is that combat loggers mostly believe what they're doing is legitimate or that they think FD won't do anything about it (probably right at this point, or that we just don't know because they are big on no name and shame). So to prevent them from ruining other players' experience, they need to be removed as soon as possible upon encounter. Not to mention high profile combat loggers (that get reported a lot) do seem to receive punishment accordingly, so basically it's win-win.

This isn't about abusive menu log uses at all! You promised me! :)
 
Last edited:
*Coughs like a politician*

Why the discussion simply hasn't extended to that part quite yet.
Oh I see, I'm early to the party. Lets see if I can seamlessly introduce the subject in a non-obtrusive manner.

And what about KoSing menu loggers eh? What's that all about?

Nope, I couldn't.

Gluttony and Combat loggers sitting in a tree.
K.o.S.<chuckling>.i.n.g.
 
I am upset about the KOS list. Now you put people who's crappy computer crashes on.

And me? I'm too stubborn to ever quit, I reset my router daily and keep my computador in top shape. How am I supposed to make it to that fabled "KOS List"?

Well, people with crappy computer/crappy internet won't always log when there's combat, if they normally escape/somehow ward me off legitimately, I simply don't go after them anymore and will be a mark next to their name on the KoS list to inform people that it might be a mistaken accusation. If it's confirmed twice that they escape legitimately, the name goes off the list until future offenses. Don't worry, we have a system going.

Well, as for how to make the list. Disappear in the middle of combat/interaction and pray :D

- - - - - Additional Content Posted / Auto Merge - - - - -

Oh I see, I'm early to the party. Lets see if I can seamlessly introduce the subject in a non-obtrusive manner.

And what about KoSing menu loggers eh? What's that all about?

Nope, I couldn't.

Gluttony and Combat loggers sitting in a tree.
K.o.S.<chuckling>.i.n.g.

Menu logger are treated the same as combat loggers if they do it during piracy/bounty hunting (so not all menu loggers), there is video evidence verification so it works.
 
I say they should put combat loggers on a seperate server with these settings

1. No effect on BGS
2. All repairs cost triple
3. All ships & modules cost triple
4. Police and military ships are 10x more likely to interdict and always attack
5. All commodities cost 10 and sell for 11 anywhere.

That way they are still in game and cannot try the complaint that they were banned and FD is not giving them access to what they paid for. make the 1st offense 2 week, 2nd offense a month, 3rd offense perm

They should also put all PK's at one server with these settings:

-no impact on BGS/PP
-no repair possible because of
-permanent docking request denied at all stations
-iron man mode required
-police actively searching and interdicting criminals
-no trade available
-no exploration first gains

This would be also a solution. Let us combine your idea and mine and we will get a perfect open play :D
 
Menu logger are treated the same as combat loggers if they do it during piracy/bounty hunting (so not all menu loggers), there is video evidence verification so it works.
Well good on you! But since they're making use of an intended FD feature, it's not morally the same is it? It's not cheating.

Help me out on the mechanics. High waking out takes about as long as menu logging? If so, not sure, what's the difference for the bottom line for the pirate?
This would be also a solution. Let us combine your idea and mine and we will get a perfect open play
biggrin.png
PKers and CLers and Tigers, oh my!
 
Last edited:
Well good on you! But since they're making use of an intended FD feature, it's not morally the same is it? It's not cheating.

Help me out on the mechanics. High waking out takes about as long as menu logging? If so, not sure, what's the difference for the bottom line for the pirate?

PKers and CLers and Tigers, oh my!

Highwaking out is only possible as long as your thrusters/powerplant/fsd are working.
Menu logging doesn't require anything.

So if you cripple your target to rob it, launched than your hatchbreakers and the target suddenly disappears it can be very awkward and frustrating
 
Last edited:
Well, as for how to make the list. Disappear in the middle of combat/interaction and pray :D

Hmmm.. can I just go silent running and you pretend I logged out?
Or maybe if I just went AFK. Would that work?
In the last 22 years of car driving, I had 3 speeding tickets. None of them even 2 digit. I refuse to change my lawful-chaotic behaviour just for the sake of a computer game.
 
Highwaking out is only possible as long as your thrusters/powerplant/fsd are working.
Menu logging doesn't require anything.

So if you cripple your target to rob it, launched than your hatchbreakers and the target suddenly disappears it can be very awkward and frustrating
Sure, that makes sense. And while not cheating, still a very unsportsmanlike move. You accept the challenge, you deal with the consequences.

So to specify, high waking/menu logging as soon as possible.
 
I didn't read all thread (I'm at work atm) but there are my thoughts about it:

The main problem is tell apart a combat logger and a legit crash (connetion lost for example: at my parent's house they got a very very very bad connection, probably if I play from there I will get random disconnections). And you may ban/punish people who didn't wanted to "log out" and that would be unfair too.

From my point of view the simpliest way to do it is just keep alive the ship in the instance for a while (a minute for example): If it was a logout due internet issues probably nothing will happen to you (as long you will be alone in your own instance at that moment) and, on the other hand, if it was a real attemp of combat log... well you can destroy them (they won't want to fight anyway), and when they reconnect will start with the rebuild screen.

I don't now if I explained myself properly (language issues xD) but I hope will you understand the point :)
 
I have absolutely no clue what combat logging is. So I can tissue you I've never done it. Sucks that there's cheats in this game, same as anywhere else.
 
As a mental exercise, I'll often read just the first post in a thread and then the last, to try and figure out how the original argument often gets so derailed. I can't even touch this.

It's a "combat log".


...



...

[yesnod]
This one, too:
wttsoxr.png


Someone should invent some new name for that stuff....
 
Last edited:
As a mental exercise, I'll often read just the first post in a thread and then the last, to try and figure out how the original argument often gets so derailed. I can't even touch this.

:p

I just voiced my opinion on OP's "adventure"

But you're right. While everybody talks about combat logs, I think Combat Kegs are much more interesting.

JuniorsBeerRun.jpg
 
Well good on you! But since they're making use of an intended FD feature, it's not morally the same is it? It's not cheating.

Help me out on the mechanics. High waking out takes about as long as menu logging? If so, not sure, what's the difference for the bottom line for the pirate?

Menu log is legitimate as long as it's not done to avoid piracy and bounty hunting.

Menu log is different than a high wake for that high wake has counters and is an in-game mechanic where as menu log does not have counters nor is it an in-game mechanic. Not to mention players affected by menu log doesn't get notified that they are being menu logged upon.

Piracy simply cannot be done in 15 seconds, and bounty hunting cannot be done either unless the logger's in a Sidewinder or some vulnerable ship.
 
Back
Top Bottom