Is "Save"ing still a legitimate tactic to avoid destruction ?

If he couldn't catch you, then he couldn't catch you. I don't know of any in game mechanic that would allow him to catch you if you were in the faster ship actively boosting, unless we're talking running out of fuel here. In this case, it was a stalemate you ended early. That's not the same as logging out to avoid destruction.

Also, all this kill on sight talk is very juvenile, comrades.
 
So you lied.

Can you not use the search function?

FD have stated several times that the 15 second timer is a legitimate way to avoid combat/log out... I do not agree with their decision but at least i do not make stuff up as i go along ;)
 
I learn about a player utilizing safe combating logging that is allowed by FD's standard, but I dislike safe combat loggers, so I'll fire upon said player with a clean status or not because I dislike safe combat loggers.

Safe combat logging is a legitimate avenue of escape allowed within the game.

Can you please just examine your logic before throwing your emotion into the discussion everywhere and cloud your logic?
Safe combat logging is a career choice now issit?

You determined that was his career logically from his post asking if it was an OK tactic did you? Good logical parallel you've drawn there.

This must be some new meaning of the word logic I've not come across before. Sorry, you're not worth my time anymore - at least now the forum doesn't have to believe you're a legal expert anymore.
 
Last edited:
Also, all this kill on sight talk is very juvenile, comrades.

As juvenile as combat logging/safe combat logging.

It's not that the attacker could not catch the OP, it's that the OP's FSD got shot out in a Conda while the pursuer's a FDL, there's no way the Conda can get away.

The FDL most likely was enjoy his time with his prey being disabled so he stopped firing, most likely he typed something in chat, which the OP was too busy safe logging to see.

- - - - - Additional Content Posted / Auto Merge - - - - -

Safe combat logging is a career choice now issit?

Oh, my, god.

I don't want to believe you are making that mistake by accident, so I'll assume you're doing it intentionally.

The concept here is that safe combat logging and piracy are both legitimate action/career by FD's standard.

You determined that was his career logically from his post asking if it was an OK tactic did you?

... Red herring, strawman, you're really hitting everything, aren't you? No where did I write his career is safe combat logging or safe combat logging is a career, reading comprehension is not that hard.

This must be some new meaning of the word logic I've not come across before. Sorry, you're not worth my time anymore - at least now the forum doesn't have to believe you're a legal expert anymore.

I don't think I want to waste much time on you either, considering you made yourself a laughing stock in front of the entire community, which even I feel bad about.
 
As juvenile as combat logging/safe combat logging.

It's not that the attacker could not catch the OP, it's that the OP's FSD got shot out in a Conda while the pursuer's a FDL, there's no way the Conda can get away.

The FDL most likely was enjoy his time with his prey being disabled so he stopped firing, most likely he typed something in chat, which the OP was too busy safe logging to see.


There is a reboot function if you didnt know, so he could have repaired and just flew away....he just chose to log off the way the game allowed him to.
I do not agree with it...but its a valid and legit choice a player can make without breaking any rules.
 
Last edited:
There is a reboot function if you didnt know...he just chose to log off the way the game allowed him to.
I do not agree with it...but its a valid and legit choice a player can make without breaking any rules.

Yea, I used to teach traders that were new how to get their drives back after I pirated them, because I'm nice like that.

The problem in this scenario would be that if he did reboot, the FDL would know that he is attempting to escape and would finish him off even faster. Not to mention the reboot function restores roughly 1-3% of the module health, which can be taken down within a second.

It's valid, yes, safe logging is valid, no doubt, but that doesn't mean I cannot register his name on a KoS list just as anyone can put me on a KoS list for being a pirate.
 
Don't worry OP, you lost the respect of a bunch of whiny videogamers who harass women and post hate speech for giggles. Other than that, eh, life goes on.

Shouldn't players be banned for keeping a "kill on sight" list, though? Sounds a lot like stalking and griefing to me.
 
Don't worry OP, you lost the respect of a bunch of whiny videogamers who harass women and post hate speech for giggles. Other than that, eh, life goes on.

"It's okay, all those that don't have a problem with safe combat logging are a bunch of filthy pacifists that picket war veteran funerals and vandalize public property for chuckles. Other than that, eh, life goes on."

Asinine? Yes.

Funny? No.

Shouldn't players be banned for keeping a "kill on sight" list, though? Sounds a lot like stalking and griefing to me.

Another one not familiar with legality and happily spilling extremely subjective morality all over the place, great.
 
Yes I have, he is not very good at escaping when the tables are turned, maybe if he spent some time practising his escape techniques instead of randomly attacking other commanders, he would not have to combat log.

OK - I believe you did read my original post - but your interpretation is wildly wrong. For the record I do not, have not and never will take part in "randomly attacking other commanders". That is your incorrect embellishment of my posting. I genuinely did not realise I was attacking a CMDR. I'd already lost 2x Condas that day to Pve wings in the haz res and I was not looking to lose a third. I saw the red WANTED, saw the ship in range and opened up....and a few moments later noticed the name....I will look MUCH more carefully next time. I didn't fire a single shot after that - just ran - panicked - kept running....and running.....and running.....low waked.......ran......ran......ran.......ran......and when I thought I was safe I Saved. That is what is annoying people off. I'll not make that mistake again.

Also for the record I did not, do not and will not "combat log". That it why I asked for opinions. I don't want to "combat log" - and I was accused of doing it. Again this is your embellishment of my post.

I've been interdicted many times by CMDRs - mainly when I've been doing deliveries in CGs. I've tried fighting. I don't do fighting - I do trading, smuggling, exploring, tried mining, barnacle hunting, the occasional Pve in res. sites and generally enjoying the game - and fighting CMDRs is not part of that enjoyment. I lose. So for the past 12 months I've been running - "practising his escape techniques" - and generally very successfully. I low-waked out with shields weak but intact. I didn't think he would follow so I took my time in the galaxy map to select the high-wake route and got interdicted during the countdown. My mistake again.

I made 5 mistakes:

1. Unknowingly attacking a CMDR
2. Low-waking out instead of high-waking
3. Not then high-waking immediately
4. Save-ing too soon - opinion is divided but the men with the guns sway the vote
5. Posting about it on here

I will attempt not to make any of them again - you can be sure of that.

Oops - I already have. Add:

6. Posting AGAIN on here
 
Last edited by a moderator:
To be fair FD can ban whoever they feel has broken the EULA or TOS, legality has nothing to do with it :)

What I mean is the legality in discussion here is FD's stipulation, then people can go a step further and discuss general legality in terms of the society they reside in if they wish.
 
You combat log, simple as that. An hopefully he reported you for doing that. Just because you found a loophole make no difference, you combat log and deny a player a legal kill.

An Frontier can and should punish you for it.
 
Last edited:
You combat log, simple as that. An hopefully he reported you for doing that. Just because you found a loophole make no difference, you combat log and deny a player a legal kill.

An Frontier can and should punish you for it.


ROFLMAO!
Dont forget the 6k bounty he missed out on too....bad, bad, bad, lol
 
...The FDL most likely was enjoy his time with his prey being disabled so he stopped firing, most likely he typed something in chat, which the OP was too busy safe logging to see...
This is pure speculation with zero evidence.
Anyone posting this while undergoing legal education really needs to pay more attention to their studies or failure is a real danger.

The arguments in this thread seem very polarised. Trouble is, neither side is definitively wrong. People are just narrow minded.

My view, for what it is worth - logging when your ship is in danger is wrong, but if you can survive the FDev stipulated time interval to enable exiting the game via the provided method, then the ship is clearly not in danger.
 
You combat log, simple as that. An hopefully he reported you for doing that. Just because you found a loophole make no difference, you combat log and deny a player a legal kill.

An Frontier can and should punish you for it.

What kill? The FDL had already failed to kill him and was out of weapons range, the only reason he got any closer to score further hits was directly because the OP was in the process of logging out and no longer boosting.
 
Everyone is missing the point entirely - you should all be asking how the smeg could a conda outrun a FDL?!? Was the FDL pilot flying in reverse? Or only using lateral thrusters? Now I'm off to put myself on my own KOS list (that I don't have) before someone else does it ;)
 
You combat log, simple as that. An hopefully he reported you for doing that. Just because you found a loophole make no difference, you combat log and deny a player a legal kill.

An Frontier can and should punish you for it.

Providing he logged out using the FD-approved method - there is nothing to be punished for. You have no say in his playtime - just as he has no say in yours.
 
Back
Top Bottom