Elite dangerous and bug/ch abusing has gone to next level.

Should discovered byu tags be removed from m67 star cluster

  • Yes, becasue there is no way with in game mechanics to achieve this

    Votes: 371 52.9%
  • No, let them keep them.

    Votes: 74 10.6%
  • I don't care

    Votes: 163 23.3%
  • replace the tags with "discovered by distant star expedition" tag.

    Votes: 93 13.3%

  • Total voters
    701
  • Poll closed .
Some clarification:

The commander in question died en route to the M67 cluster. He then submitted a ticket alleging a bugged death( I don't know about that if it really happened or not)

While he was waiting for support, he respawned and came all the way back to Cancri climb, then resumed trek to M67 cluster, made it in cluster and scanned his systems. Then Fdev respawned him where he died just outside of cluster with his data intact from inside the cluster. He then made the choice to head back to bubble to turn it in.

That is what I understand how the events unfolded. Feel free for someone to correct me if I am wrong.
 
Some clarification:

The commander in question died en route to the M67 cluster. He then submitted a ticket alleging a bugged death( I don't know about that if it really happened or not)

While he was waiting for support, he respawned and came all the way back to Cancri climb, then resumed trek to M67 cluster, made it in cluster and scanned his systems. Then Fdev respawned him where he died just outside of cluster with his data intact from inside the cluster. He then made the choice to head back to bubble to turn it in.

That is what I understand how the events unfolded. Feel free for someone to correct me if I am wrong.

The plot thickens. So it's a player morality issue and not a support issue?
 
Some clarification:

The commander in question died en route to the M67 cluster. He then submitted a ticket alleging a bugged death( I don't know about that if it really happened or not)

While he was waiting for support, he respawned and came all the way back to Cancri climb, then resumed trek to M67 cluster, made it in cluster and scanned his systems. Then Fdev respawned him where he died just outside of cluster with his data intact from inside the cluster. He then made the choice to head back to bubble to turn it in.

That is what I understand how the events unfolded. Feel free for someone to correct me if I am wrong.

Hum... This looks like foul play.... if he was allegation of bug and intended to go back it self he wouldnt be asking for "teleport" but the "money" ... this is foul play 100% dirty guy.... FD should remove this tags and give him some other punishment... they should not accept FOUL PLAY like this EVER.

But yet , no prof of this also have emerged from your statement (sorry) so i will discard it for now (since this could have been planted by the guy itself or some friends or even the Expedition trying to clear his dirtyness)
 
Last edited:
Is there any evidence the cmdr knew he had the data when he respawned? If the above info is correct, this is likely just an accident.

He knew he had the data when he decided to go back to the bubble. He was trying to decide in Discord general chat if he would just finish going in to the cluster again with us and keep the cluster pristine and tag free or if he would go back to the bubble and be the only one with tags up there. I have no idea if his respawn outside the cluster was a malicious thing or not. He seemed genuinely surprised to have his exploration data intact which I am guessing he found out from whichever FDev employee did the respawning.

All of the information I know about came from that conversation he had. I did not keep proof of everything because that is not the kind of world I live in and I did not think much of it at the time.

I added the disclaimer because memory is a fickle thing, and I have no idea to the players actual motivations in regards to the ticket. I do know that day we were all in a hurry to get in to M67 and those of us that died en route all hurried back as quick as we could. (I failed to land on a 2 G world for a meetup in the most catastrophic way)
 
He knew he had the data when he decided to go back to the bubble. He was trying to decide in Discord general chat if he would just finish going in to the cluster again with us and keep the cluster pristine and tag free or if he would go back to the bubble and be the only one with tags up there. I have no idea if his respawn outside the cluster was a malicious thing or not. He seemed genuinely surprised to have his exploration data intact which I am guessing he found out from whichever FDev employee did the respawning.

All of the information I know about came from that conversation he had. I did not keep proof of everything because that is not the kind of world I live in and I did not think much of it at the time.

I added the disclaimer because memory is a fickle thing, and I have no idea to the players actual motivations in regards to the ticket. I do know that day we were all in a hurry to get in to M67 and those of us that died en route all hurried back as quick as we could. (I failed to land on a 2 G world for a meetup in the most catastrophic way)

I appreciate your candour, but considering that this was known to be a one way trip, why would an expedition member consider selling any data at all? Surely all the systems scanned while travelling there would be expected to be lost too?
 
Some clarification:

The commander in question died en route to the M67 cluster. He then submitted a ticket alleging a bugged death( I don't know about that if it really happened or not)

While he was waiting for support, he respawned and came all the way back to Cancri climb, then resumed trek to M67 cluster, made it in cluster and scanned his systems. Then Fdev respawned him where he died just outside of cluster with his data intact from inside the cluster. He then made the choice to head back to bubble to turn it in.

That is what I understand how the events unfolded. Feel free for someone to correct me if I am wrong.

As I recall it from the comms at the time, what happened is that he got disconnected while supercharging (most of us experienced disconnects at some point during the climb) and lost his canopy upon reconnecting in normal space inside the stream. Filed a ticket since it only happened because of the disconnect, then realised that it would be 12+ hours until Monday morning in the UK and decided to take the death in order to be able to rejoin the expedition for the rest of the day one event.
 
As I recall it from the comms at the time, what happened is that he got disconnected while supercharging (most of us experienced disconnects at some point during the climb) and lost his canopy upon reconnecting in normal space inside the stream. Filed a ticket since it only happened because of the disconnect, then realised that it would be 12+ hours until Monday morning in the UK and decided to take the death in order to be able to rejoin the expedition for the rest of the day one event.

So then why did Support do what it did?
 
As I recall it from the comms at the time, what happened is that he got disconnected while supercharging (most of us experienced disconnects at some point during the climb) and lost his canopy upon reconnecting in normal space inside the stream. Filed a ticket since it only happened because of the disconnect, then realised that it would be 12+ hours until Monday morning in the UK and decided to take the death in order to be able to rejoin the expedition for the rest of the day one event.

I was wondering about how he died. I would not have waited until Monday morning either.

- - - Updated - - -

I appreciate your candour, but considering that this was known to be a one way trip, why would an expedition member consider selling any data at all? Surely all the systems scanned while travelling there would be expected to be lost too?


Yeah I would not have done it. But everyone is different. I don't know why he did it. I only know it was done.
 
So then why did Support do what it did?

Your guess is as good as mine. But I would assume that they got the ticket and moved him to a safe position in that system without first checking that he was actually still there.
 
Last edited:
Yeah I would not have done it. But everyone is different. I don't know why he did it. I only know it was done.

I think I get to use the recently implemented 'unvote' option for the first time! I had voted option 4 on the basis that FD may have wanted to avoid an issue with the server (as has happened before).

Clearly the entire dataset sold after the start of this one way trip from this Cmdr should be removed from the game. Whether deliberately or through negligence this cmdr's behaviour is cheating & (s)he should not benefit financially or with tags. The ship rebuy cost I can understand of course.
 
Yeah I would not have done it. But everyone is different. I don't know why he did it. I only know it was done.

I think I would have done it, mostly out of curiosity to see if it really would work. Then when it worked and I couldn't undo it and people were upset, I would have felt guilty :D

I don't think the helpdesk could have foreseen this outcome, and I don't begrudge a player for wanting to try something that hadn't been done, but I think the result is an unfortunate (and interesting!) outcome that FDev should tweak. (As mentioned, I like the ideas of rewriting the tags with the expedition name, plus of course anything extra like adding a POI ship graveyard would be fantastic too!)
 
Last edited:
Hope this might clear some things up.
(Cropped out his username to avoid name & shame)
2v15agz.jpg
 
Last edited:
All tags on systems that should have been a one way trip should be removed. Double boosting the FSD is an exploit.
 
Back
Top Bottom