I just move on, losing a kill equals no loss. Just another person playing their game.
I just wonder about that, as there has been logged problems with the games networking, if it went legal and proof needed to be supplied. Actual proof. Is it there? Is it stronger than the history of network problems in game? If it IS there, why do FD even need you to report it?
If it went legal the EULA states that Frontier can do as they choose and reserve the right to restrict your access to the game. Not even read the EULA properly but almost all digital distribution works that way these days including steam. Not saying it's right but proof wouldn't be needed by FD, it'd highly likely be a case closed move along, you pressed agree and can technically still play just without other players.
As for the data capture it's probably a case of needing to know which of the 2 million units sold they need to look at and it's probably not a big red flag that says "combat logged". It's probably a bit of code that says "connection lost from server to client". It's when that bit of data is combined with the 30 other times it happened and when investigated that the client (player) got below X% hull strength or started loosing before "connection lost" then it turns from data into proof.
In the end a single event, or even multiple events as you say could be just random data. If they put a "if connection lost = 40+ then ban" code in they'd catch a lot of innocent players in there. Some players leave via Alt+F4 or task-kill or whatever due to bugs, some do it because it's a faster way to get to desktop especially on older machines if they need to exit in a hurry.
Similarly if they had "if connection lost = 40+ then flag for investigation" then FD would probably have a few thousand reports a month to look at.
Better PR to use player made reports with cmdr names to narrow down the worst perpetrators vs other players and deal with them on a case by case basis rather than going Blizzard on it and banning a whole bunch of people in one big sweep. Means when they take the time to investigate each instance of "connection lost" it's much more likely it'll be a result rather than spending man-hours investigating for a "ah it was just an accident".
HAHA Hilarious. As long as that works both ways. You kill x number unarmed ships. You are banned. EH Not so hot an idea old son.
Report them every single time they do it. FD won't likely react to a single report. There is always a chance that their connection failed randomly. But if a history is built up, eventually a case is made.
If it went legal the EULA states that Frontier can do as they choose and reserve the right to restrict your access to the game. Not even read the EULA properly but almost all digital distribution works that way these days including steam. Not saying it's right but proof wouldn't be needed by FD, it'd highly likely be a case closed move along, you pressed agree and can technically still play just without other players.
As for the data capture it's probably a case of needing to know which of the 2 million units sold they need to look at and it's probably not a big red flag that says "combat logged". It's probably a bit of code that says "connection lost from server to client". It's when that bit of data is combined with the 30 other times it happened and when investigated that the client (player) got below X% hull strength or started loosing before "connection lost" then it turns from data into proof.
In the end a single event, or even multiple events as you say could be just random data. If they put a "if connection lost = 40+ then ban" code in they'd catch a lot of innocent players in there. Some players leave via Alt+F4 or task-kill or whatever due to bugs, some do it because it's a faster way to get to desktop especially on older machines if they need to exit in a hurry.
Similarly if they had "if connection lost = 40+ then flag for investigation" then FD would probably have a few thousand reports a month to look at.
Better PR to use player made reports with cmdr names to narrow down the worst perpetrators vs other players and deal with them on a case by case basis rather than going Blizzard on it and banning a whole bunch of people in one big sweep. Means when they take the time to investigate each instance of "connection lost" it's much more likely it'll be a result rather than spending man-hours investigating for a "ah it was just an accident".
LOL There is no cheat when they log, you lost nothing cept the thrill of the kill.
Given the history of the network stability, how do you suppose FD could counter this claim?
So you are coming across the same commander time and time again........how?
I don't combat log, but I don't see it as a big issue. Just ignore/block him. Or do like I do: Play in solo. I never see any combat loggers (or griefers for that matter).
LOL There is no cheat when they log, you lost nothing cept the thrill of the kill.
And I refer to it as cheating, simply because if you try and do what the game requires - it doesn't let you log out in combat - so you are cheating the system we're playing in.
The game does let the player log out in combat - using the delayed exit menu.
Sandro mentioned combat logging as one behaviour that might be taken into consideration if the potential karma system is implemented.
Right, splitting hairs there, Im confident you knew exactly what I meant... THAT, vs killing a process from your task manager, in case you're still unsure what i mean![]()
How do you, as a player, tell the difference?
How many 'Report Player' buttons have been hit consequent to this very act of logging off via the 15-sec timer?
How do you, as a player, tell the difference?
How many 'Report Player' buttons have been hit consequent to this very act of logging off via the 15-sec timer?
Right, splitting hairs there, Im confident you knew exactly what I meant... THAT, vs killing a process from your task manager, in case you're still unsure what i mean![]()
No splitting hairs at all - you stated "it doesn't let you log out in combat" when it, i.e. the game, does indeed let any player who so chooses log out at any time (subject to a delay when "in danger").
So you are coming across the same commander time and time again........how?