Friday, 6 March 2015

Of combat logging and combat loggers (list inside)

While Elite Dangerous is no doubt a magnificient game, it suffers from this archaic issue which really shouldn't be present in any 2015's game. As it stands now, any player can avoid a PVP encounter (or any other encounter for that matter) by simply pulling the plug (the quick and dirty way) or by invoking the laughable 15 seconds logout timer.

I won't lie here. The problem is very widespread and serious. I regularly meet 2-5 combat loggers per raid and had to even alter my playstyle a bit because of them. So if you are just starting with the whole piracy business, brace yourselves against the never ending waves of cheaters. Sometimes I feel like putting down the game for good but the memorable events I had with people who want to play the game properly as was intented by the devs simply outweight this issue, however serious.

You can't do much against a hard disconnect really. But soft ones via logout timer are easily punishable by massive burst damage output. The irony here is proportionally I had more bounty hunters pulling the plug on me than traders.

The criticals scenarios for soft logout are:
  • Target flying in one direction, not moving an inch from the course and not boosting.
  • Trader waiting silently with cut engines during the scanning procedure or negotiating.
  • "Wait, need to find out how to drop cargo" bullshit situations.
  • Interdiction ending abruptly. Trader could have just started logging out.
Always and I mean always give your mark a benefit of doubt. For pirates, combat logging is a tabu and should never be mentioned before a mark until proven guilty. Do not send welcome messages including combat logging warnings etc. It ruins the experience, ruins the whole roleplay thing and the immersion.

Each time you encounter a combat logger, file a report against him (personally, I use other/other for sections and "combat logging" for description). Add him to your KoS list, make it public if possible and just burst him down everytime you see him.

I attach my fresh (oldest record is 1 week max) KoS list of combat loggers. Feel free to use it as you please. I don't provide any other evidence than my word. So either take it or leave it :) Some of them were killed multiple times already. Basically once someone appears on my KoS list I will try to do my best to send them to a free sidey or at least to solo for prolonged period of time.

List of combat log exploiters (28.2. 2015 - 6.3. 2015)
GALIA
CYBORG REAPER
APOLLO FET
MILES_963
BASILIS
MILKAK
ZAPPER_DE_LUX
COLA ZERO
NAMASTEH
LASZLO HORVATH
MOPO
BITNUKL
KHAZSTARRUNNER
FLEX 1978
BUMER_UA
GUSTOVSHIKOV
SINIS
DOCKING COMPUTER
MISTERVALIUM
NERDSHOWANDTELL
THUNDER 950
AIRROX

Remember that combat logging is a serious exploit and FD devs will be taking actions against these cheaters anytime soon. Please help make the open environment better for all of us and report each one of them.

2 comments:

  1. This is probably more easily addressed by limiting the penalties suffered from death by player.

    I have personally lost months of game progress in some senseless burst of player violence. You simply cannot expect anyone to sit idle while you shoot up hundreds of millions of credits, which would be the reality if you happened across my PvE geared Python at a moment where I could not cover the rebuy. Since I don't stand much of a chance against any PvP oriented player, particularly not when they arrive in pairs or packs, I much too often find myself flying with the entire ship in the balance.

    I'm sure you realize that there is nothing FD can threaten to do to my account that will inspire any more fear than the permanent loss of a bounty or combat geared Python or Anaconda.

    ReplyDelete