Add a message / warning for task-kill combat logging commanders on next start-up

Querty Out

Q
Just dropping a suggestion on prevention / education. Currently there is nothing telling a commander who has combat logged that he/she did a bad deed. Task kills are easily detectable so how about a warning / stern message on next start-up to educate the commander about his/her wrong doing? Something that stops upcoming career combat loggers in their tracks, give them pause for thought and have those juveniles set upon the path of righteousness for becoming upstanding galactic citizens or respected villains.

Edit:

To clarify, I'm talking about task-killing in Player-versus-Player combat situations here, not network disconnects.

Suggested message, displayed in-game, maybe next to the main menu on start-up after the task-kill / unexpected game termination: "It looks like the game did not shutdown cleanly during a recent encounter with other commanders. Please report any problems you may have experienced. Note that game termination through means other than regular logout should be avoided and is against the rules."
 
Last edited:

Riverside

Riverside
As I said in the other thread I like this idea. If nothing else it would give some reassurance that something is done about CLogging.

A similar concept would be a 'looks like you're having trouble, here's some advice on how to improve network stability' for players with genuine problems.
 

Asp Explorer

Asp Explorer
As nice an idea as it would be to inform CMDR's that their connection is perhaps less than perfect, the number of ways this could be completely avoided numbers in the dozens of dozens - and that's all that can really be said about it.
 

Querty Out

Q
Asp Explorer said:
As nice an idea as it would be to inform CMDR's that their connection is perhaps less than perfect, the number of ways this could be completely avoided numbers in the dozens of dozens - and that's all that can really be said about it.
Click to expand...

Im referring to task-kill, a fairly unambiguous affair. Sure, there are other things that can be done but this one should be easy to implement.
 

varonica

varonica
Eodemos said:
Im referring to task-kill, a fairly unambiguous affair. Sure, there are other things that can be done but this one should be easy to implement.
Click to expand...

So how do you determine it is a task kill rather than a number of other things that an appear identical. For instance, a power cut at the players house, Blue Screen of Death on the PC, the game simply locking up, as it has done for me a number of times, or the game simply just shutting down with no warning. You just going to accuse everyone of being a clogger and to hell with the consequences?
 

Querty Out

Q
varonica said:
So how do you determine it is a task kill rather than a number of other things that an appear identical. For instance, a power cut at the players house, Blue Screen of Death on the PC, the game simply locking up, as it has done for me a number of times, or the game simply just shutting down with no warning. You just going to accuse everyone of being a clogger and to hell with the consequences?
Click to expand...

No determination of cause. If you happen to terminate the game during combat then you get the message telling you that a deliberate act is bad behaviour and you may either feel guilty or appalled.
 

Chrystoph

Chrystoph
Eodemos said:
No determination of cause. If you happen to terminate the game during combat then you get the message telling you that a deliberate act is bad behaviour and you may either feel guilty or appalled.
Click to expand...

Ah, so this is the same mentality as those messages at the beginning of a movie that all but turn you in for piracy, even when you are watching the movie in a theater. Got it...
 

Querty Out

Q
Chrystoph said:
Ah, so this is the same mentality as those messages at the beginning of a movie that all but turn you in for piracy, even when you are watching the movie in a theater. Got it...
Click to expand...

No, not quite. You'd only get to see the message after there was an unexpected termination of the game during combat. Or, to run with your analogy, you won't see the message when watching the movie in a theatre but you might when watching it on your PC after downloading it from a dubious site.

As far as the content of the message goes, yes, it could be similar to those movie piracy messages, kept more or less friendly, but explaining that such and such is against the rules and bad for your karma.
 

Querty Out

Q
Shadowdancer said:
So… anyone who does it deliberately won't give a damn, and those who just have an unstable connection or system get an accusatory finger pointed at them.

Great idea, next!
Click to expand...

I'm not saying that this is a solution, just a little thing that contributes to an overall improvement, for example the proposed karma system. It may raise awareness that your karma could be affected, that FDev is taking combat logging seriously and that it is against the rules. An unstable connection does not terminate the game unexpectedly. If you happen to experience a system crash during combat then yes, you get that message and have to suck it up.

Career combat loggers won't give a damn but maybe you can educate some players before they become one.
 

Chrystoph

Chrystoph
Eodemos said:
No, not quite. You'd only get to see the message after there was an unexpected termination of the game during combat. Or, to run with your analogy, you won't see the message when watching the movie in a theatre but you might when watching it on your PC after downloading it from a dubious site..
Click to expand...

No, I meant exactly what I said. The message is there regardless of the circumstances. Guilty, period because you cannot verify the situation.
 

Roybe

Roybe
Eodemos said:
Just dropping a suggestion on prevention / education. Currently there is nothing telling a commander who has combat logged that he/she did a bad deed. Task kills are easily detectable so how about a warning / stern message on next start-up to educate the commander about his/her wrong doing? Something that stops upcoming career combat loggers in their tracks, give them pause for thought and have those juveniles set upon the path of righteousness for becoming upstanding galactic citizens or respected villains.
Click to expand...


Just a note stating that you left the game unelegantly, would at least be some proof that there was someone watching how a person left the game. No threats of banning or whatever....just a 'hey we noticed that you had a problem', similar in how companies use phony cameras to keep security up...even if there are no cameras...makes people think twice.
 

Querty Out

Q
Chrystoph said:
No, I meant exactly what I said. The message is there regardless of the circumstances. Guilty, period because you cannot verify the situation.
Click to expand...

In that case your analogy is a bit off. So, yes, if the game process terminates unexpectedly during PVP combat (you do not seem to count this as 'circumstances') then my suggestion is to show a message.
 

Querty Out

Q
Roybe said:
Just a note stating that you left the game unelegantly, would at least be some proof that there was someone watching how a person left the game. No threats of banning or whatever....just a 'hey we noticed that you had a problem', similar in how companies use phony cameras to keep security up...even if there are no cameras...makes people think twice.
Click to expand...

Exactly. The tone of the message is for FDev to set. I'm sure they can come up with something 'educational'.
 

Chrystoph

Chrystoph
So, a kernel panic gets the player harassed.

The game crashing gets a player harassed.

A griefer with a lag generator gets the player harassed.

Windows deciding that you need to reboot gets a player harassed.

Yeah, I see your point. We need to have an automatic harassment system emplaced because you object to a statistical minority.

This is the equivalent of arming your police exclusively with grenade launchers.

***phoomp, phoomp, phoomp***

"I got the bad guy!"

"Yep, and the 20 innocent people he was running through."
 
Last edited:
You must log in or register to reply here.
Back
Top Bottom