I tried this d&d beyond, posted some of buggy things and read something about issues found by other "players".
About 80% of the issues got the same response "during the beta you can use only the free content like SRD, elemental evil, blablalba"
People can't read properly, it seems, so they will continue to post things like "i have only two feats to select" or "there is only a paladin oath o a priest domain".
So the admin/leaders just responds with a merely copy-paste. But the problem is what the usual response contains: "during this beta".
So, what's the point of all of this? You need to test things, and you choose open beta. Which is good. You choose to limit the content, which is good compared of what you need to do with d&d beyond.
The stupid thing is: do you really think this will be enough to test even the other components you will add to the retail content? I work as a software developer and i must follow the steps alpha (is the project is big enough) -> test -> QA -> test as beta (closed) -> release candidate (if big enough) -> other useless stuff for this topic. After every step must there must be a TEST phase.
You are planning to do test, and then realease without test. Very useless project this beta phase. Everything in IT can be destroyd for just a little feature add without the proper considerations or testing (or Quality assurance, for very big project like this should be).
D&D Beyond can be a good project, and this beta is just a big gigantic advertising system. I don't understand what takes you from give the beta testers the full tools/contents to test. Do you fear the leak of free content? After the release date you can disable the accounts until they buy the product or for what you will plan to market d&d beyond. You still need to advertise d&d Beyond more? just make a demo version: free accounts can do only free content (which is mostly useless) but gives a lot of visibility and shares over social.
To what is now: this beta phase will be useless for you except for marketing. After the very first iissues (like some javascript-related that i posted days ago) and first suggestions this won't be useful anymore. And leaves us a felling of being used...
To me, i'll just wait the retail product. Wake me up when this is going to be, and I will still be pleased to help with bugs and things... But this is going to be just a loose of time.
Simple answer? We aren't allowed to "give away" paid content. That's why we are only allowed to test free content. This isn't a choice from Curse. This is a guideline from Wizards of the Coast, and we have to adhere to it. There are plenty of actual bugs out there to squash. We find them on a daily basis. There will continue to be bugs, well after release. That's how things go. Like we've said multiple times, this isn't a video game, and you aren't testing a finished product. We, the community, are helping build D&D Beyond from the ground up, and I, for one, think that's pretty great. I also realize this isn't what everyone is looking for, for many reasons. I'm also not going to try to convince you that this is a good thing, really. The only thing I can do is tell you to check it out once D&D Beyond has gone live, and see what you think then.
I really want to emphasise part of what Firehawk said there - this isn't about the content/data. Making a hundred additional spells available isn't likely to change anything.
We've already seen that feedback from the community has shaped the functionality of this site. There are major changes to the equipment manager incoming due to this.
THIS is what the testing is about and why your feedback is important - it's helping to make sure that the way the site works is the best way possible. :)
I tried this d&d beyond, posted some of buggy things and read something about issues found by other "players".
About 80% of the issues got the same response "during the beta you can use only the free content like SRD, elemental evil, blablalba"
People can't read properly, it seems, so they will continue to post things like "i have only two feats to select" or "there is only a paladin oath o a priest domain".
So the admin/leaders just responds with a merely copy-paste.
But the problem is what the usual response contains: "during this beta".
So, what's the point of all of this? You need to test things, and you choose open beta. Which is good. You choose to limit the content, which is good compared of what you need to do with d&d beyond.
The stupid thing is: do you really think this will be enough to test even the other components you will add to the retail content?
I work as a software developer and i must follow the steps alpha (is the project is big enough) -> test -> QA -> test as beta (closed) -> release candidate (if big enough) -> other useless stuff for this topic.
After every step must there must be a TEST phase.
You are planning to do test, and then realease without test. Very useless project this beta phase. Everything in IT can be destroyd for just a little feature add without the proper considerations or testing (or Quality assurance, for very big project like this should be).
D&D Beyond can be a good project, and this beta is just a big gigantic advertising system.
I don't understand what takes you from give the beta testers the full tools/contents to test. Do you fear the leak of free content? After the release date you can disable the accounts until they buy the product or for what you will plan to market d&d beyond.
You still need to advertise d&d Beyond more? just make a demo version: free accounts can do only free content (which is mostly useless) but gives a lot of visibility and shares over social.
To what is now: this beta phase will be useless for you except for marketing. After the very first iissues (like some javascript-related that i posted days ago) and first suggestions this won't be useful anymore. And leaves us a felling of being used...
To me, i'll just wait the retail product.
Wake me up when this is going to be, and I will still be pleased to help with bugs and things... But this is going to be just a loose of time.
Bye
Simple answer? We aren't allowed to "give away" paid content. That's why we are only allowed to test free content. This isn't a choice from Curse. This is a guideline from Wizards of the Coast, and we have to adhere to it. There are plenty of actual bugs out there to squash. We find them on a daily basis. There will continue to be bugs, well after release. That's how things go. Like we've said multiple times, this isn't a video game, and you aren't testing a finished product. We, the community, are helping build D&D Beyond from the ground up, and I, for one, think that's pretty great. I also realize this isn't what everyone is looking for, for many reasons. I'm also not going to try to convince you that this is a good thing, really. The only thing I can do is tell you to check it out once D&D Beyond has gone live, and see what you think then.
A dwarf with a canoe on his back? What could go wrong?
I really want to emphasise part of what Firehawk said there - this isn't about the content/data. Making a hundred additional spells available isn't likely to change anything.
We've already seen that feedback from the community has shaped the functionality of this site. There are major changes to the equipment manager incoming due to this.
THIS is what the testing is about and why your feedback is important - it's helping to make sure that the way the site works is the best way possible. :)
Pun-loving nerd | She/Her/Hers | Profile art by Becca Golins
If you need help with homebrew, please post on the homebrew forums, where multiple staff and moderators can read your post and help you!
"We got this, no problem! I'll take the twenty on the left - you guys handle the one on the right!"🔊