Devoting this entire post to collecting evidence of only new 4 star crew being added to the loot table, since it's obvious 5 star crew were added without issues.
So many 10xpremium pulls and no new 4* featured for me.... The reason I did the pulls in the first place. There’s clearly an issue evidenced by the other tread featuring players accumulating 100’s of 10xpremium pulls results and getting none of the newly added 4* other than Augment Riker.
I think that once the realize that they were wrong and there was a problem, the people like silverrose who opened 100+ packs to test it should be able to trade in at least 10% of their Super Rare pulls in exchange for the new super rares of their choice.
Opened at least 40 packs since the update was made and i got zero of the new added 4* crew. Think there already have been enough proof, that they were not added, or at least not live.
yeah, I think that is why they are being so quiet here. The implications of having to do some kind of credit/appeasement to make things right for people who bought packs this week who were expecting a shot at new crew is going to be rather complicated.
The worst thing they can do is say there's no problem when there clearly is, especially when it is going to kill future sales from people who feel like they were misled.
Because the last time it turned out that players were pulling packs with zero chance of the represented crew dropping (ie Musketeer LaForge) & the initial reaction from DB was to cover it up, their innocent till proven guilty posturing is no longer legitimate. The burden is now on DB.
This is a garbage response. Your lying to the player base is unacceptable
You know, as someone that's been accused of being negative on this forum, I find your response just asinine. The response is fine, and there's a big difference between lying and learning that your information was wrong (which is exactly what it says in the response) and correcting it.
This was ultimately a bug, and an annoying bug because it was caused by what, based on their response, is a service mismatch. It's unfortunate, but part there are scenarios where testing won't catch everything, especially when they're dealing with an integration like this. It's unfortunate that it took them as long as it did to find it, but that's also something that a deep bug can cause.
While DB as a company has been less than up front with us before, ripping into Shan and accusing her of lying only diminishes whatever point you have to make.
While DB as a company has been less than up front with us before, ripping into Shan and accusing him of lying only diminishes whatever point you have to make.
I would have given this post an awesome, except that Shan is a her.
Shan stated in another post: "I can confirm that this has been verified when the change was made live, and was verified again today when I brought up these concerns to the team."
I asked over and over: "are you sure there isn't a problem?" and was told over and over there is no problem. Other players did the same.
While DB as a company has been less than up front with us before, ripping into Shan and accusing him of lying only diminishes whatever point you have to make.
I would have given this post an awesome, except that Shan is a her.
Whoops! I knew that and still typed it wrong... luckily the new edit feature is vastly better than the old forums!
This is a garbage response. Your lying to the player base is unacceptable
It's unfortunate, but part there are scenarios where testing won't catch everything, especially when they're dealing with an integration like this.
All they had to do was have a player account with 100,000 dilithium loaded onto it, make 150 pulls, realize no one was dropping, and tell us there is an issue and we are working on it. This response take 15 minutes. Instead we were told we were wrong repeatedly. How can we not be jaded?
Instead we were told we were wrong repeatedly. How can we not be jaded?
Shan can only convey here what she gets told from "above". And as Erin said herself: They tested things (again) and found no issues. Despite our experiences here saying something completely different. At least in the end "justice gets served". And cheers for being so peristent with this Niner...
This is a garbage response. Your lying to the player base is unacceptable
It's unfortunate, but part there are scenarios where testing won't catch everything, especially when they're dealing with an integration like this.
All they had to do was have a player account with 100,000 dilithium loaded onto it, make 150 pulls, realize no one was dropping, and tell us there is an issue and we are working on it. This response take 15 minutes. Instead we were told we were wrong repeatedly. How can we not be jaded?
The problem is this is not the first time where Shan has talk to Devs, been told X, we insisted on Y, and only after forcing them to look further did they admit it was Y. Every time it happens DB loses credibility and Shan loses credibility in insisting on X.
For every issue where DB says something and we notice something different it's hard to trust "sorry it's just RNG" as a response when DB has a history of it not just being RNG. But the problem is, because there is RNG it takes a huge sample like this for DB to even acknowledge the issue enough to investigate it.
![(CSF) Jesus Is Lord [••••]](https://us.v-cdn.net/6030345/uploads/userpics/839/nQHMW3V3VSZSB.jpg)
Comments
The worst thing they can do is say there's no problem when there clearly is, especially when it is going to kill future sales from people who feel like they were misled.
https://forum.disruptorbeam.com/stt/discussion/712/what-we-re-doing-to-fix-broken-time-portal-pulls
This is a garbage response. Your lying to the player base is unacceptable
I had issues earlier as well, I believe the forums might have been impacted by the level3 outage that occurred earlier, and might still be ongoing.
You know, as someone that's been accused of being negative on this forum, I find your response just asinine. The response is fine, and there's a big difference between lying and learning that your information was wrong (which is exactly what it says in the response) and correcting it.
This was ultimately a bug, and an annoying bug because it was caused by what, based on their response, is a service mismatch. It's unfortunate, but part there are scenarios where testing won't catch everything, especially when they're dealing with an integration like this. It's unfortunate that it took them as long as it did to find it, but that's also something that a deep bug can cause.
While DB as a company has been less than up front with us before, ripping into Shan and accusing her of lying only diminishes whatever point you have to make.
Haha -- I read that as "level 3 outrage" and thought that was a fairly accurate description of some of the recent posts.
Could you please continue the petty bickering? I find it most intriguing.
~ Data, ST:TNG "Haven"
I would have given this post an awesome, except that Shan is a her.
I asked over and over: "are you sure there isn't a problem?" and was told over and over there is no problem. Other players did the same.
So yes I personally feel lied to.
Whoops! I knew that and still typed it wrong... luckily the new edit feature is vastly better than the old forums!
Lol. Outrage was how i first read it through, too
All they had to do was have a player account with 100,000 dilithium loaded onto it, make 150 pulls, realize no one was dropping, and tell us there is an issue and we are working on it. This response take 15 minutes. Instead we were told we were wrong repeatedly. How can we not be jaded?
Shan can only convey here what she gets told from "above". And as Erin said herself: They tested things (again) and found no issues. Despite our experiences here saying something completely different. At least in the end "justice gets served". And cheers for being so peristent with this Niner...
The problem is this is not the first time where Shan has talk to Devs, been told X, we insisted on Y, and only after forcing them to look further did they admit it was Y. Every time it happens DB loses credibility and Shan loses credibility in insisting on X.
For every issue where DB says something and we notice something different it's hard to trust "sorry it's just RNG" as a response when DB has a history of it not just being RNG. But the problem is, because there is RNG it takes a huge sample like this for DB to even acknowledge the issue enough to investigate it.