Threads like this not only reminds us that there may still exist a bug that we need to account for while competing in events but also that communication between DB and their customers is extremely lacking. It is very evident in the fact that we have many post edits which lets us know that this thread is being read and yet zero response. Our last communication was that a bug report was submitted. What happened with that report? What is the current status of that bug report?? That is pretty much all we are asking for.
So I don't think that this is beating a dead horse.
Threads like this not only reminds us that there may still exist a bug that we need to account for while competing in events but also that communication between DB and their customers is extremely lacking. It is very evident in the fact that we have many post edits which lets us know that this thread is being read and yet zero response. Our last communication was that a bug report was submitted. What happened with that report? What is the current status of that bug report?? That is pretty much all we are asking for.
So I don't think that this is beating a dead horse.
While I agree with your sentiment and goals, this is precisely the definition of beating a dead horse.
If players hadn’t kept beating a dead horse about the polywater yar debacle for 6 weeks we wouldn’t have gotten a reasonable solution to that issue either. I don’t see this being any different.
Guys, I agree with you and I want you to keep at it on the off chance that DB actually deigns to recognize the issue.
My point was that this is beating a dead horse which the other poster didn’t think so. You guys all agree that it is so we’re all good. So let’s resume beating DB’s expired equine shall we.
Threads like this not only reminds us that there may still exist a bug that we need to account for while competing in events but also that communication between DB and their customers is extremely lacking. It is very evident in the fact that we have many post edits which lets us know that this thread is being read and yet zero response. Our last communication was that a bug report was submitted. What happened with that report? What is the current status of that bug report?? That is pretty much all we are asking for.
So I don't think that this is beating a dead horse.
While I agree with your sentiment and goals, this is precisely the definition of beating a dead horse.
I did get a definitive response from customer support but my tests left me with doubts.
I noticed a similar issue with the shuttle missions failing a lot on high success displayed percentages. I read some previous post about the previous AND issue. I have a good feel for statistics (PhD in Physics) but did not have the resources to do the proper population sample hypothesis tests to extreme confidence, also I needed to assume a normal distribution which is likely not correct.
Anyhow I wrote to support and got a load of stupid replies for about 3 weeks. Maybe it was just a lie to shut me up but I finally I got the following definitive response (specific to the AND skill tests)
As per our Community Guidelines, please do not post private exchanges between you and our company, this includes support. ˜Shan
@Shan as per our community expectations, now that you've proven that you've read this thread, can you respond? Or is DB content to continue to lie to its paying customers?
As I said in similar threads, if I had something to communicate I would.
Please let Jon Radoff know that continuing to deny this issue and expecting his customers to forget about it is unacceptable and damages any trust that his customers have in DB being truthful about anything.
Sorry, the horse isn't dead. At best it's a portable hologram with a physically tangible matrix. Or a cat in an unopened box who's state of being we're not sure about until we check.
Management has given development directives not to report to customer relations on the state of the problem that may or not still be a problem. So until we can even identify that there is a horse, it can't be beaten upon after its death.
As I said in similar threads, if I had something to communicate I would.
Please let Jon Radoff know that continuing to deny this issue and expecting his customers to forget about it is unacceptable and damages any trust that his customers have in DB being truthful about anything.
Radoff doesn't care. He sold his control to Tilting Point, and keeps only the name and a fraction of revenues.
How about we try it this way... He's passed on! This parrot is no more! He has ceased to be! He's expired and gone to meet his maker! He's a stiff! Bereft of life, he rests in peace!
As I said in similar threads, if I had something to communicate I would.
Honestly, that answer is worse than silence. It just proves DB's incompetence when you either are unable to look up a bug report we know exists, or are forbidden from discussing it.
As I said in similar threads, if I had something to communicate I would.
Honestly, that answer is worse than silence. It just proves DB's incompetence when you either are unable to look up a bug report we know exists, or are forbidden from discussing it.
Y’all kept asking her to say something. Anything. She said something. Request granted.
As I said in similar threads, if I had something to communicate I would.
Honestly, that answer is worse than silence. It just proves DB's incompetence when you either are unable to look up a bug report we know exists, or are forbidden from discussing it.
Y’all kept asking her to say something. Anything. She said something. Request granted.
Responding "no comment" does not count as a response. If these threads really bother you that much, please ignore them.
As I said in similar threads, if I had something to communicate I would.
Honestly, that answer is worse than silence. It just proves DB's incompetence when you either are unable to look up a bug report we know exists, or are forbidden from discussing it.
Y’all kept asking her to say something. Anything. She said something. Request granted.
Responding "no comment" does not count as a response. If these threads really bother you that much, please ignore them.
As I said in similar threads, if I had something to communicate I would.
Honestly, that answer is worse than silence. It just proves DB's incompetence when you either are unable to look up a bug report we know exists, or are forbidden from discussing it.
Y’all kept asking her to say something. Anything. She said something. Request granted.
Responding "no comment" does not count as a response. If these threads really bother you that much, please ignore them.
Where in my response did I say the thread bothered me?
As I said in similar threads, if I had something to communicate I would.
Honestly, that answer is worse than silence. It just proves DB's incompetence when you either are unable to look up a bug report we know exists, or are forbidden from discussing it.
Y’all kept asking her to say something. Anything. She said something. Request granted.
Responding "no comment" does not count as a response. If these threads really bother you that much, please ignore them.
Comments
So I don't think that this is beating a dead horse.
While I agree with your sentiment and goals, this is precisely the definition of beating a dead horse.
My point was that this is beating a dead horse which the other poster didn’t think so. You guys all agree that it is so we’re all good. So let’s resume beating DB’s expired equine shall we.
-- Til'c (spelling?) From SG1
Teal'c
One of my favorite quotes.
PM for details.
So long and thanks for all the fish.
It’s already been moderated by Shan on the first page, so there is proof that the thread has been read.
That David guy is a big meany-pants.
There. That self-effaciure should do the trick. 😁
I didn't even see that. Man, that's just cold. They can respond to moderate a comment, but deliberately ignore all the people asking questions?
She may have been told specifically not to post anything on this particular topic.
Has been that way since ..hmmm.. maybe thread number 2 or 3?
Since nobody has posted it yet...
Edit: credit to @[10F] Newt (In the last iteration)
The horse is only dead if we let it die.
Clear!
[Zzaapp!!]
@Shan as per our community expectations, now that you've proven that you've read this thread, can you respond? Or is DB content to continue to lie to its paying customers?
Thanks for the update Shan
Please let Jon Radoff know that continuing to deny this issue and expecting his customers to forget about it is unacceptable and damages any trust that his customers have in DB being truthful about anything.
It's been what, 6 months since you opened your bug report? Is it still open? A developer assigned? Still in the queue? Never going to be worked on?
How exactly is an AND slot supposed to be loaded or calculated? 75% first skill and 25% second? 100% high skill 25% low? Order doesn't matter?
You have NOTHING you can communicate on any of that?
Management has given development directives not to report to customer relations on the state of the problem that may or not still be a problem. So until we can even identify that there is a horse, it can't be beaten upon after its death.
Radoff doesn't care. He sold his control to Tilting Point, and keeps only the name and a fraction of revenues.
Yeah, you were witness when the deal was signed and/or are a reporter of Forbes. You know all finer details hence
I think the results from the original investigation prove (beyond reasonable doubt) that there is a horse.
How about we try it this way... He's passed on! This parrot is no more! He has ceased to be! He's expired and gone to meet his maker! He's a stiff! Bereft of life, he rests in peace!
Honestly, that answer is worse than silence. It just proves DB's incompetence when you either are unable to look up a bug report we know exists, or are forbidden from discussing it.
Y’all kept asking her to say something. Anything. She said something. Request granted.
Responding "no comment" does not count as a response. If these threads really bother you that much, please ignore them.
What was that word again? Oh, yeah... “BAYAM!”
Where in my response did I say the thread bothered me?
It’s BAYUM!