I've seen "combat logger" in any mmo or rpgmmo that I have played so far.
Combat logging ban in solo?
- Thread starter Sandysky
- Start date
The problem with shadowban is that it's not even a disincentive for traders. If a shadowban prevents you from affecting the BGS, this means you're also not going to deplete whatever trade route you're running. Sounds like every space trucker's dream to me.
And commodity prices won't degrade from the trade runs of other players either ?
This whole shadow ban thing becomes more and more appealing to me.
Last edited:
Usually to avoid opening support tickets due to bugs. Normally, players would just reload (like in previous Elite games), or use the console (Bethesda style).
BTW, I don't think there is a "moral" discussion here, as it doesn't affect others (only in PvP mode, where it is deprecated) and it's just there to mitigate missing features and bugs on Frontier's side as well as lessen the workload on the support team (since there is no monthly fee anyway). Besides, the AI cheats anyway (unlimited ammo, not penalized for speeding etc.), so cheating doesn't seem to be an issue for Frontier.
Not gonna lie I combat logged once against an M type star. The game spawned me into it and as I was looking away from the screen at the time, I had no idea was happening. The clues were the fact that solar flairs were all around me and my fuel scoop activated as soon as I zoned in. I figured this wasn't meant to happen and decided to expedite the ship refund process by not dying.
No you cannot be banned for combat logging in solo. Think about this for just a second: Who the hell is going to report the solo player in the first place? Obviously no one, so no ban possible. I would have thought this was patently obvious.
If you did, it would be a shadowban (which is basically another solo mode). Not much difference, really.
Unless Frontier has managed to get the server to send a unique signal when client presses the exit game button and also log disconnects. If the correlate one with the other any combat logs will flag up as there will be a disconnect but not a exit signal. Combine that with the in-combat flag that the game uses for the 15 second timer and voila, if there's an abnormal distribution of those and you'll find the most frequent combat loggers and those with major connection issues. Further monitoring will find if the people disconnect in combat or all the time, if all the time they have internet issues, if only in combat situations then they are logging.
They did mention they were looking at automated data gathering in a post about combat logging a while back.
Last edited:
Unless someone is personally monitoring you, how would they know? The npc isn't going to complain.
The minute they can tell that you killed your process instead of their game crashing, that's when they'll be able to enforce a ban because of "combat logging". Until then, and as unreliable as the game client is, it's crazy to ban someone for "combat logging" since you can't tell why the game client crashed.
Ban for combat loggin is only possible if you got reported numerous times for it.... And to be reported, you need to be in Open. At solo, there is no one who can report you. FD wont even bother to check Cmdr's, unless they are being reported.
You can combat log in Solo to heart content. You wont be affecting anyone beside yourself there by doing that. Lol.
You can combat log in Solo to heart content. You wont be affecting anyone beside yourself there by doing that. Lol.
Last edited:
For now , I do hope FD look into this , because cheating the BGS is cheating everyone
I doubt it happen... They only bother with those, who are affecting others directly again and again. And even worst combat logger, will receive warns before anything, then is shadowban wich last few days only, then is ban wich also is lasting for some time only. I cant image how one has to many times to combat log to get "finnaly" banned for it, period. FD is quite soft for this matter, but is wrong to tell, that they aint doing anything about it.
Last edited:
Oh bullox!
Someone else saving their cargo isn't cheating you of diddly-squat.
Combat logging in open, particularly if there's another commander in-instance... sure. That's an issue. Particularly if PvP is at all involved.
Worrying about whether someone else is "git gud" enough to have "earned" that python is just stupid and childish.
Goose4291
Banned
With their already prescribed method: Shadowbanning, which means you can still play, but your actions don't impact on the 'verse (i.e. no BGS interaction).
And I'm sure they can pretty much ban people from logging in if they really wanted to. Look at Blizzard and it's spate of bannings both in WoW (http://www.cinemablend.com/games/Why-World-Warcraft-Banned-Over-100-000-Players-Week-71941.html) and Overwatch (http://www.dailydot.com/esports/blizzard-bans-overwatch-cheaters/)
They said they were looking at telemetry to do something about combat logging in open, and as many network guys said then, it was a wasted effort. There is really nothing that can be done other than acting on multiple reports in open. And that's open! There is really absolutely nothing FD can do with the current network model. As it stands now, if you're in solo, that instance, the stations, the NPC's etc are running entirely on your computer. Traffic with the frontier server is minimal and only occurs when you buy/sell, or resolve combat and/or bounties. Everything else is running on your PC.
