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

[znôrt]

I just don't see why people can't be happy when something good happens to someone else?
One of the more irritating facets of human nature I suppose.

that's not the point (for me at last). i do laud their endeavor. but you can't have a tag on a place you couldn't have returned from. it's just silly, and makes the whole tag and discovery system a joke, and it's embarrassing for frontier, unless they rectify or can make up some lore that explains it, that is. this has nothing to do with recognizing or not others' merits.

edit: to be clear, it is about frontier mitigating poor or immature game mechanics with external intervention and micromanagement, and getting even that wrong.

 

[Jack Schitt]

Its true.

Thanks. I admit I couldn't find the FAQ that used to specifically say that they couldn't, but interpretation of FD's words or lack thereof can be something of a dark art. This will make me a lot more comfortable doing distant exploration in bug-infested areas (and I don't mean Thargoids). If I lose another ship, and there's even a chance there's a glitch or bug involved, I'll ticket it.

 

[Dbrn47]

that's not the point (for me at last). i do laud their endeavor. but you can't have a tag on a place you couldn't have returned from. it's just silly, and makes the whole tag and discovery system a joke, and it's embarrassing for frontier, unless they rectify or can make up some lore that explains it, that is. this has nothing to do with recognizing or not others' merits.

edit: to be clear, it is about frontier mitigating poor or immature game mechanics with external intervention and micromanagement, and getting even that wrong.

Can nothing just be an accident or a mistake anymore? It has to be dubious and embarrassing? Did you even read the thread, where what actually happened was clarified by Dr. Kaii and excerpts from the player?

 

[o2thaZ]

Lame indeed.
.
.

 

[znôrt]

Can nothing just be an accident or a mistake anymore? It has to be dubious and embarrassing? Did you even read the thread, where what actually happened was clarified by Dr. Kaii and excerpts from the player?

chill, i did not imply it was intentional, but even without intention it's still embarrassing until addressed.

 

[Dbrn47]

chill

I'm so chill that-

[video=youtube;a1sUy1IvDw4]https://www.youtube.com/watch?v=a1sUy1IvDw4[/video]

 

[Esso]

Wait, hold up! The dev teleported them back and let them cash in the exploration data?! What the actual ! Why? On what grounds! So now ANYONE can just write to Frontier support and ask to be teleported back to the bubble? What is this favoritism bull. The guys did a monumental achievment when they reached their destination, but they went in knowing there is no way back. Not only does this negate their sacrifice, it makes the game mechanics cheap! Every single stranded commander out there died for nothing now, because FDev did not deem them worthy of teleport. Way to play favorites... This game is slipping.

Has there been official statement as to WHY devs decided on this? They better revoke that otherwise whats the bloody point!

 

[Dbrn47]

Wait, hold up! The dev teleported them back and let them cash in the exploration data?! What the actual ! Why? On what grounds! So now ANYONE can just write to Frontier support and ask to be teleported back to the bubble? What is this favoritism bull. The guys did a monumental achievment when they reached their destination, but they went in knowing there is no way back. Not only does this negate their sacrifice, it makes the game mechanics cheap! Every single stranded commander out there died for nothing now, because FDev did not deem them worthy of teleport. Way to play favorites... This game is slipping.

Has there been official statement as to WHY devs decided on this? They better revoke that otherwise whats the bloody point!

Read this:

Just as the official DSE rep, I'd just like to say that a) AH Cancri was tagged using the neutron double jump thing, seems legit but ultimately that's FD's decision which I believe they are reviewing now. b) The other two or three people who have tags got it because they blew up and support couldn't move them back, so just moved them back outside the cluster, and gave them their data without being asked (as is routine for them - they didn't know about the full details of the no-return element of the expedition - they deal with hundreds of tickets a day). AFAIK these guys emailed back and mentioned it but nothing was done so they handed in. But again, FD are reviewing it.

Anyone who says anything that contradicts the above is either speculating (and is wrong) or is flat out lying. There is no collusion with FD in this, it is all the result of the above. I strongly suggest the speculation and misinformation stops now, otherwise I think we should lock the thread until FD get back with their decisions.

And this:

http://i64.tinypic.com/2v15agz.jpg

Also this:

Hi everyone, I'm the alleged cheater that this post is about. Here's my post on reddit elaborating on the whole thing, I have no clue how the story got this blown out of proportion. https://www.reddit.com/r/EliteDanger...litch/dd0yp0f/

Copy paste for ease of access.

This is mostly true, but I'll elaborate on why I was moved back. At the time I was sure it was a bug, but it might not have been. I was attempting to scoop the white dwarf, thought it would be no biggie, but the orbit lines never showed up with the "no-fly" zone. Next, as I was going in to scoop, apparently I got caught in the beam despite the actual visible beam being quite far away and very slowly rotating, so I got thrashed around without actually being where the beam should have been. Again, may have just been my inexperience in scooping them and not knowing the scooping beam is a persistent cone regardless of the visual indicator of what should be scoopable.

I got instantly thrown out of supercruise from being thrown backwards into the star's exclusion zone somehow, logged out after taking a bit of damage and submitted a support ticket asking about it and if they could possibly move me away from it, in hopes I'd get one of the super speedy replies people have previously, so I could join the mass jump into the cluster. I waited for ~30 minutes, then decided to just suicide, miss the jump and base camp meeting, and just go up again.
I forgot about the support ticket for awhile, after I had gone up, did the preliminary "honk n go" of my 3 systems assigned as cartographer, scanned the 3 stars in my empty first system, and scanned my third system of all but two that I missed as they weren't landables and landables were my priority. Climbed a massive mountain range one of my (new) friends found in a pretty cool binary system for about 7 hours straight, then got off and wasn't able to play for a week because of school.

Frontier responded to my ticket during the week, I believe it was thursday, and they told me they had moved me back to the white dwarf and restored my rebuy cost. Obviously, I didn't need to be teleported back at this point, and was about to request for them to teleport me back as they mentioned they could in the support ticket. I paused though, and asked the DSE discord what I should do now that I was given this crazy opportunity to tag my systems in the cluster.

The rest is part of another comment I already posted yesterday. I had no clue this would be such a big deal, and I apologize to the people that are upset.

I believe you're talking about me, and I didn't receive any outright negative feedback when I asked several people/the rest of the expedition in discord. I was willing to ask them to send me back up, but as it was I had to go back anyways and restart the climb because they set me at the white dwarf with the full tank of fuel I had on me.

Everyone that replied when I asked (unless I missed someone) was fine with or jealous of the opportunity I had, in a friendly way though. I only tagged two systems, both of which were assigned to me as a cartographer, one which was empty, and the other which I had gone through and scanned all 40 or so bodies (save two, which I'm pretty I missed).
I don't consider this screwing up the mission, as people had already tagged some of the beginning stars in the climb thanks to double dipping the neutron, and the whole point was to chart, catalog, and discover as much as we could for the sake of exploration, but if you're upset I apologize.

Plenty of people in the chat on the initial climb can vouch for the WD story, and hopefully the ones that replied when I asked for advice on what to do upon being moved back will vouch for me too.

All in this thread a few pages back if you just took a minute to two to look. The breadcrumbs are there and the real story unfolded.

 

[Esso]

All in this thread a few pages back if you just took a minute to two to look. The breadcrumbs are there and the real story unfolded.

Thanks for pointing the facts out to me, i appreaciate that. I was not about to read through 25 pages of comments, so TL;DR version is greatly appreciated. Even informed with the facts, the deed has been done. Something that could not happen due to constraints of the game mechanics, did happen despite them, due to direct intervention from the dev. Conscious or not, doesnt matter - it should be reverted post haste. Perhaps someone should send what you sent me to the support rep that carried that ticket out. I dont blame the player for cashing in the exploration data, i blame careless support rep. That said everyone is human and makes mistakes, so as long as it gets reverted its a case of no harm no foul.

 

[Ziggy Stardust]

I was not about to read through 25 pages of comments, so TL;DR version is greatly appreciated.

Don't have the TL;DR, but it should have been 36 pages.

These guys are all talk.

 

[Zulu Romeo]

I asked a few times on the 2.3 announcement page if multicrew would have an effect on exploration data. if so, I wonder if that would impact on this sort of issue with systems from which there is no escape apart from suiciding (while your crewmates can simply nip out and back at will perhaps taking exploration data with them).

 

[ph1Lt0r]

...so, a chattering teeth bobble head? [big grin]

Brett, please make this a reality (with sound) so I can buy one for my wife and sneak it on her dashboard and annoy the out of her.

 

[Riverside]

I asked a few times on the 2.3 announcement page if multicrew would have an effect on exploration data. if so, I wonder if that would impact on this sort of issue with systems from which there is no escape apart from suiciding (while your crewmates can simply nip out and back at will perhaps taking exploration data with them).

It should at least be easy to confirm the behaviour in beta if nothing else. I'd hope you don't get any data unless you actually flew your own ship there & back. How does the current wing exploration tagging work? I've never don't it myself.

 

[Zulu Romeo]

It should at least be easy to confirm the behaviour in beta if nothing else. I'd hope you don't get any data unless you actually flew your own ship there & back. How does the current wing exploration tagging work? I've never don't it myself.

From my recent experience, wimg exploration is really bugged. Trying it in Distant Worlds, if a wing member scans an object while you're in hyperspace, that object does not appear on your system map and while you can see it and fly to it in real space, it cannot be targeted or scanned. I have several "missing" planets as a result of this, appearing as black circles on the system map (and when in close-up on planetary maps, as nothing at all). A longstanding ticket is still open for me.

 

[Riverside]

From my recent experience, wimg exploration is really bugged. Trying it in Distant Worlds, if a wing member scans an object while you're in hyperspace, that object does not appear on your system map and while you can see it and fly to it in real space, it cannot be targeted or scanned. I have several "missing" planets as a result of this, appearing as black circles on the system map (and when in close-up on planetary maps, as nothing at all). A longstanding ticket is still open for me.

So bugged instancing & wing issues pervade, but how are the mechanics of winged exploration intended to work? I'm just thinking a similar process may be applied. I know how winged bounty collection works, and of course we've been told how multi-pew bounty collection will work (ie differently despite less personal risk).

This kind of issue is really the only one I have with multi-crew so far, I'd be interested to know how you think it will/should be applied.