Combat Loggers... how many are there!!!! What kind of punishment do they receive and when?
- Thread starter TheoZ
- Start date
- Status
Oh, I see. How many times should I let them kill me before I am allowed to quit? Am I allowed to quit if I see they're waiting for me to respawn at the station? Or do I have to launch, wait for them to kill me, respawn, and repeat until they leave? Because that's usually how it goes.
Last edited:
How can it be cheating if the game was made to allow this?
- - - - - Additional Content Posted / Auto Merge - - - - -
They would've added a thirty second log-out, with exclusion should you be in a safe spot/station if not intended.
Last edited:
Don't play open or get better at running? You have options to avoid these people that don't involve cheating.
- - - - - Additional Content Posted / Auto Merge - - - - -
Because the developers themselves have labeled it as cheating. It doesn't really matter what you think, it is cheating.
Am I allowed to quit if I see they're waiting for me to respawn at the station? Or do I have to launch, wait for them to kill me, respawn, and repeat until they leave? Because that's usually how it goes, and I'm not that excited about being blown back to a Sidewinder because I'm not allowed to quit for fear of being banned.
Last edited:
Switch to Solo while in station. Or use the 15 second log out timer. The only thing deemed as cheating is force ending the application while in combat in order to circumvent the 15 second logout timer.
Last edited:
I'm sure there is a lot of combat logging, but there is some server dropping too. I was just flying w/another commander low over Merope the other day, and then a 3rd player showed up and wham... screen lock, drop to menu. Once I was in a furball CZ with a wing, all fine then massive stammering and back to menu. I've tried a new router, but "Open" still drops me now and then. Solo is solid, and I heard (and have seen with a network tool) that open needs 10x the bandwidth of solo.
And for another problem, I'm in an area where Comcast is now enforcing max data per month rules at 300GB. I didn't think that was a problem until I got my bill... Elite being a major player in data... it's like being a $10/month game in "Open". Thanks Comcast.
And for another problem, I'm in an area where Comcast is now enforcing max data per month rules at 300GB. I didn't think that was a problem until I got my bill... Elite being a major player in data... it's like being a $10/month game in "Open". Thanks Comcast.
In that case, I've never combat logged. Quitting via Alt-Tab and closing takes just as long, it just reverses the wait.
Last edited:
So, if the idea is that Combat Logging is griefing the griefers, I get it. Look at the threads. It's totally working. The single argument I agree with from the CL'ing Inquisition is; not playing in open if you want to avoid the mess. I urge everyone to find the environment they enjoy playing in. Open isn't the end of the rainbow, it's just another bunch of players you can exclude from your galaxy.
Not exactly. If you alt tab and right click window then close in order to circumvent the in game 15 second logout timer then that IS combat logging.
But, no Commander can tell if there was a CL, or a 15 sec withdrawal. It's just like Griefing. Everyone sees it around every star.
You are seriously mistaken on your assumption. (Clearly with bias).
This very thread is about combat logging, which is more often than not a refusal to bend to the wishes of the "Loud" PvP minority group.
You just posted in the wrong thread if you want your assertion to be taken seriously...
Cheerz
Mark H
- - - - - Additional Content Posted / Auto Merge - - - - -
You know exactly what Eddy meant. Even though he did not write PvP-combat-centric, you still know what he meant. So please refrain from twisting the intended meaning.
Cheerz
Then that's just the spirit vs the letter of the law, isn't it? Anyway, I upgraded t'other day, so the menus are not a problem any more and I use the timer.
But the point remains that I got reported for combat logging, supposedly, when I quit in supercruise, got interdicted, failed and dropped into a new instance before the program closed. And I've upgraded my graphics card, so it's not just isolated to the low end folk, or to the poorly connected. People will be punished for the game's own code. Incentives are usually a more effective method of changing behaviour than punishment, yeah?
We can't tell exactly what happened - but you can get a idea from the logs.
{00:21:55} Trying 11 machines to find a relay to x880xx25x9x7xx x 5 [1/2]((Relay))Name Unknown
{00:22:17} Trying 10 machines to find a relay to x8xx53x2x1x9xx x 3 [1/2]((xx.xx.xxx.124:59xxx))Name Unknown
{00:22:17} AttemptReconnectViaRelay - timeout - from Connected
{00:22:21} Machine x8xx53x2x1x9xx x 2 [1/2]((Relay))Name Unknown disconnected: timeout
{00:22:21} allow machine to time out immediately after forced disconnect (ed-31797)
That doesn't mean anyone combat logged - all it means is that something forced that connection to be terminated.
Last edited:
InMemoriamSirocco
Banned
You are wrong there is noticeable differences between the two and you can easily tell.
A menu log the ship will remain in the instance taking damage until the 15 seconds expires then it will vanish.
A Process close will leave the ship in the instance for as long as it takes to time out (20 - 40 seconds) and will take zero damage to shield or hull during this time.
Distinguishing between the two is simple.
Can you accept that because of FDevs definition of combat logging that logging out via the in game menu should not be considered combat logging and therefore not punishable?
Can you accept that this is their games design and it's implementation is working exactly as frontier intend it to (in so far as the logging out menu).
I can accept why you feel it is combat logging and can understand why PvP centric people feel frustrated when commanders use the in game menu to log out. Reality is they are not breaking any rules doing so...
Using exploits such as alt F4 or dropping your cable out of your modem / router etc is defined as combat logging by FD and should be both reported and punished IMHO.
How would this disincentivise logging out during unwanted combat? You take the view it is an offence to log out via the in game option while under combat when logging out that way is not punishable and is indeed frontiers intention to allow players to log out of the game that way (at any time). Still I fail to see how it would reduce people from choosing to log out when unwanted combat starts. Perhaps if they were PvP Centric players themselves and logged out to avoid 'losing' an engagement, it would act as a punsihment but for non PvP players it would make little difference I feel.
Good suggestion, that would go some way towards kurbing random newbie killings for sure.
Yes I can understand why you would dislike those 'earning' their cash in solo then coming to open for PvP, so instead of having some risk of player piracy while trading they only have to deal with NPC's...
I do not see a solution to that particular issue because I agree with the current design of being able to mode switch at the players discretion. I do not agree with locking play modes.
CG's should be for everyone but that is my opinion on that... Indeed CG PvP is a good thing and adds a definite richness to the game IMHO, I have done a few CG's and seen some familiar PvPers in my instances from time to time, a lot of fun either avoiding them, bribing them to get through or outrunning themIt definitely adds a lot of fun and adrenaline to the game in those events.
I think a 15 second timer isnt long enough to punish someone trying to com at log "the legal way" particularly with bigger ships. If someone logs out to avoid destruction they are trying to cheat the system and i think that is fundamentally wrong.
As for the bans on open play... how else are you going to ban someone? Frontier wont ban someone totally from the game..they can shadowban to solo however.
42 pages.
42 pages spent arguing about whether combat-logging is an exploit, when FD were clear that it is.
42 pages on whether they'll do anything about it when they'd already said they would when they could.
42 pages to figure out it's a complex issue given the networking model, and that it'll likely keep on happening for now.
And of course, the obligatory strutting of PVP prowess as well as a heap of childish personal attacks and snark.
I'll say one thing for this thread: it's been another really great advert for any future Offline version FD might release.
42 pages spent arguing about whether combat-logging is an exploit, when FD were clear that it is.
42 pages on whether they'll do anything about it when they'd already said they would when they could.
42 pages to figure out it's a complex issue given the networking model, and that it'll likely keep on happening for now.
And of course, the obligatory strutting of PVP prowess as well as a heap of childish personal attacks and snark.
I'll say one thing for this thread: it's been another really great advert for any future Offline version FD might release.
Last edited:
Well if they increased the timer to 30 seconds, then that would give an extra 15 seconds of damage dealing and potential for them to be killed yes? Then it would be more likely that players would try to highwake out to escape instead of just logging out...
My point about your bans suggestion was with regards to how it would remove the incentive to combat log for the non PvP player... I don't think it would affect them that much being shadow banned for an hour or whatever timeframe, unless they were specifically playing to affect the BGS... Now if when players are shadowbanned, they also were to 'suffer' an 80% reduction in mission rewards and the costs of buying and selling goods meant they made very little to no profit and the other playable options in the game (mining, bounty hunting, exploring) all returned only 20% of non shadowbanned profit maybe then it would be a real punitive step for those exploiting / cheating etc, otherwise the only player type affected by the shadowban would be PvP players who get shadowbanned.
- Status