A simple fix [semi fix] to combat logging!

Robert Maynard

Volunteer Moderator
Why must explorers switch modes while they are out exploring?

Why not?

Restricting players from mode switching to suit a PvP play-style does not seem to gel with the freedoms offered to every player by the core game features.
 
Last edited:
They could still log off, just not change modes.
But then you'd be stuck in the mode you set off in. That doesnt sound like a good idea to me. Would put explorers in a bit of a disadvantage through no fault of their own. Whilst the idea in principle isnt bad, its execution needs work. :)
 

Robert Maynard

Volunteer Moderator
I just don't think logging off should be available if you're taking hits from another player, simple as that.
Jump away and then log when in a safe zone, but no logging off option in a scenario where you're being fired upon and registering hits.

That's a different conversation altogether - the 15-second delayed logoff is an act sanctioned by Frontier (if it wasn't then it wouldn't be an option in the menu system).
 
What if firing on a CMDR in a smaller ship would automatically and instantly always spawn a wing of Elite NPC Vultures with large beam lasers from system authority, attacking the assailant?
 
Why must explorers switch modes while they are out exploring?



Guess that would work, too. :)



Depends on the point of view... for non PvP players it is of course no issue. For PvP player it is a major, game breaking issue.

But Robert's suggestion would resolve such concers elegantly enough.


It isn't a matter of 'must', it's a matter of want. The ability for individual players to play as they like shouldn't be restricted because other players are annoyed at loosing a kill. If we are in combat, and I take the 15 second option, I didn;t combat log, but I have be forced to log back in just for you? Craziness. The zeal over CL'ers is way over the top.
 
Restricting mode switching to stations / landed on planets requires there to be suitable stations or planets available - this would prevent mode switching during exploration for players who do not own Horizons as they cannot land on planets and there are no stations out in the black. Given that there are no restrictions on mode switching, imposing a restriction would seem unreasonable at best.

A simpler way would require the player whose connection had been lost (for whatever reason) to rejoin the same mode as they left.

Agreed - same thing but more elegant.
 
But then you'd be stuck in the mode you set off in. That doesnt sound like a good idea to me. Would put explorers in a bit of a disadvantage through no fault of their own. Whilst the idea in principle isnt bad, its execution needs work. :)

You are not stuck. land and switch.
 
'Combat logging' (the truest form of it where ED is closed or the router is turned off without logging out) is a problem that FD can't reliably fix, which is party why doing it, or even suggesting it, is policed so vehemently in this 'ere forum; there's little else that can be done about it.

There are so many real life reasons outside of escaping an in-game no-win situation that could result in sudden disconnection that FD simply can't risk turning ED into a game that punishes players for having a life / network problems.

The OP's suggestion targets the wrong group of players and would make the lives of 'law abiding' players harder, particularly explorers. So, alas, that one's a non-starter.
 
Last edited:
That's a different conversation altogether - the 15-second delayed logoff is an act sanctioned by Frontier (if it wasn't then it wouldn't be an option in the menu system).

Yep, but it's this act that causes problems. Just don't have it in a combat scenario and then you can correlate combat logging with the necessary report submitted by the attacker and take action.
This isn't unreasonable at all in my books.
 
Last edited:
Why must explorers switch modes while they are out exploring?

Ask the ghosts of the explorers who made it all the way to Sgr A*, only to be sent straight to Hades upon their arrival, not even given the time to glance at the spectacle they came so far to gaze upon.......
 
Yep, but it's this act that causes problems. Just don't have it in a combat scenario and then you can correlate combat logging with the necessary report submitted by the attacker and take action.
This isn't unreasonable at all in my books.
How do you define what's a 'combat scenario'?
 
It isn't a matter of 'must', it's a matter of want. The ability for individual players to play as they like shouldn't be restricted because other players are annoyed at loosing a kill. If we are in combat, and I take the 15 second option, I didn;t combat log, but I have be forced to log back in just for you? Craziness. The zeal over CL'ers is way over the top.

A commander cheats his way off a deadly situation - he is put in the same place afterwards. Combat logging/cheating has to end. There are endless numbers of videos that this exploit is used by a huge ammount of commanders. If other exploits are fixed this one should be fixed too.
 

Robert Maynard

Volunteer Moderator
Yep, but it's this act that causes problems. Just don't have it in a combat scenario and then you can correlate combat logging with the necessary report submitted by the attacker and take action.

The introduction of the 15-second delay on exit is because of combat and applies whether the combat is against players or NPCs - otherwise there is no delay on exiting at all.
 
It isn't a matter of 'must', it's a matter of want. The ability for individual players to play as they like shouldn't be restricted because other players are annoyed at loosing a kill. If we are in combat, and I take the 15 second option, I didn;t combat log, but I have be forced to log back in just for you? Craziness. The zeal over CL'ers is way over the top.

If you log in combat - even with the timer you are considered a combat logger and will be listed as one on the kos lists of the in game clans.
 
I can't post videos here [ that's why what I am writing is moderated now] so I will try to set up a scene here.
There are commanders in open who play only to win. They attack other players, get into fights and like to blow up commanders. They prey mostly on non pvp players because against pvp'ers most of the time they LOOSE.
What does a player like that do when he finds an equal or better match? HE LOGS OFF! I win - stay in open. I loose - I log off. Molest people near station - blow up people - GREAT! When a force comes in and almost destroys the culprit... LOG OFF!
Our group has a couple page document of combat loggers and the list is growing every day. There are numerous videos and unfortunately FD's response is below weak. I see known combat loggers every day. The only thing we can do
is to shun them by texting them in game. They laugh at reporting them to FD.

So if FD is unwilling to punish them directly let's have an idea here.

What if mode switching would be possible ONLY when in station/landed ? You want to switch mode - you need to be landed/srv whatever.
If you combat log in space - you have to wait before your enemy get's bored waiting for you or log in and get what you deserve.
Maybe it will not fix cheating entirely but would at least pose a nuisance for those who are willing to put risk on other commanders but never take the risk alone.

I know that people are combat logging on npc's to never die but this is another story which I never expect to be fixed.


Just remember in this conversation that leaving the game by properly logging out at anytime is NOT considered combat logging.

The devs only consider combat logging to be the 'ungraceful exit' of the game by somehow disrupting the internet connections.

Keep chasing the latter...but complaining about the former will be met with silence.
 
How do you define what's a 'combat scenario'?

The introduction of the 15-second delay on exit is because of combat and applies whether the combat is against players or NPCs - otherwise there is no delay on exiting at all.

Precisely. It knows you're being fired upon and hence puts a 15 second timer on before logging off. Just remove it. If you're connection just drops in this scenario, it's logged as such on FDs server end. If a report comes in that correlates with this and the report is that of a combat log, action is taken.
 
Back
Top Bottom