When folks first started using json access for various things, the developers here warned that it wasn't supported, and that the structure was subject to change. So I'm not quite sure why so many of you are surprised that this has now happened, or why you invested so much money here solely because of an unsupported work around.
A. They didn't announce it, warn about it, or anything. Just did it and since... radio silence. For a couple of days now. It's not like they were unaware this was being used, whether it's "supported" or not. Nor have they provided any reason why it suddenly is not available, why the structure has changed, any of that.
B. I don't think people invested money because of an unsupported workaround. For me, upon seeing how much better Foundry is for me than this site, the only reason to continue paying them here in the future is if I can import stuff from here into Foundry. If I can't, and have to hand-type it all there anyway, then there is no reason to buy it here, as I won't be using it here. I'll be using things only in Foundry. Not sure that Fandom Games cares about me, but if a lot of people made the same decision, they'd have reason to care.
I agree completely. I have invested my money mostly to support Critical Role. This was a useful way for that investment to payoff in my games. It seems like a wasted opportunity to shut off that compatibility and synergy.
The integration with Foundry VTTis the ;ain reaso why I took a D&D Beyond subscription so I can make plenty of characters to play in Foundry VTT. Fix it!
The main reason i bought all the source books on here was to allow my players to Create characters and manage campaign at eash with the character sheets in DND beyond Im able to import Level changes and new characters into my games with ease for new players and now u have removed the part that makes DND beyond Worth while. Please add this back at least until you release your API Why remove this before. I am able to import i will be requesting a refund on my Dungon Master subscription.
I'll add in my support for keeping a stable way of getting character data. I own every book on dndbeyond, and my intent is to continue to buy every book that comes out because both I and my players really love the character building and managing functionality, and I love running adventures with digital resources. And it's for that reason that having a direct integration between dndbeyond and my VTT is super nice, since it allows me to continue to use and support dndbeyond and my players get the full dndbeyond experience. If that integration does not exist, then I am forced to stop using dndbeyond and just simply use the in-app VTT character sheets and do everything manually there, and everyone loses: my players and I lose functionality and I have no reason to buy and subsequent books from dndbeyond.
I know you are working towards a public API, which is fantastic, and I know will be a huge boon to all these integrations. But I do hope that until then you can continue to offer unofficial, but relatively stable ways for the current integrations to continue working.
If that integration does not exist, then I am forced to stop using dndbeyond and just simply use the in-app VTT character sheets and do everything manually there, and everyone loses
I'm convinced that, a la Microsoft, Fandom believes that if they can force us to choose between this site, and our VTT, we will choose them over our VTT, because DDB "has the official docs" and many VTTs do not (although FG and R20 do, of course). They're counting on the strength of that character sheet maker of theirs. But it's not enough all by itself, and they don't really have anything else but that. Every other feature (encounter builder, combat tracker, dice roller) is already available in multiple other places, and nearly always better-implemented than what they have here.
I just wanted to clear up a few things here, and give some context around the changes and expectations for the future. I think the community being able to come together, and create amazing tools that benefit all types of use cases is amazing, and an important part of what let D&D Beyond become what it is today. I want to thank everyone here for voicing how important an API is to them, as seeing feedback is the most powerful way to see how important a feature is to the masses.
Now for context on the current undocumented API. If you have been watching the developer updates, you know we just finished up a massive rework of the character sheet. Up to this point, all the logic still lived on the same nodes as our website. This caused some serious issues with performance and we needed to get this logic off ASAP. The logic is now in its own service, and also why the URL has changed. However, for all the same reason it was undocumented and "unsupported" as before, is still true today. There is still more work to be done, such as now moving all our data out into its own DB as well for example. We don't want to officially support this, due to the rapid changes that can happen at this stage, and no real way to monitor who is going to be affected. With that said, we have not, and will not be blocking anyone from using it, as long as they are aware of its unsupported state, and that it may change as we continue to refine and develop more features, and that it is ultimately "unsupported"
The main feedback at this stage we are looking for, would be from various app developers, and knowing what they would be looking for in a fully supported API.
Edit Looks like adam also covered this on the dev update!
Great to see, thanks devs. I feel I'm still missing something though cuz it sounds like we can still copy and create an import into roll20. Maybe I'm missing something (or I caught the dumb big time) but I can't seem to get it to work.
I want to thank the Molster and the rest of the D&D Beyond staff to be extremely responsive about the matter and I will look forward to the release of the official API.
In the meantime, we do have a mutual understanding that some changes do need to take place and now having an establish communication channel will make changes in the future way more visible to us, and therefore we will be able to prepare instead of reacting to necessary changes. That is overall a great thing.
Coming from a datacenter background and now having watched the relevant part of today's stream, I can just say that I do understand the need for some of those changes: The main service has priority when it comes to availability, and the will to "get it right" and not half-assed speaks for you. I am looking forward to the official API and will be available for feedback regarding the design (and of course beta-testing) of it.
Thank you again, your response was something I desired, but honestly, did not expect in regards of pleasantness and quickness. Also sorry for my english. I sound ******'y when I try to sound somewhat official.
I just want to add my voice to this for the future. A friend and I recently purchased content (much of which I already owned) on D&D Beyond, soley because of the VTTA module that allows us to make use of that content on the Foundry VTT.
It is only because of this module that I've had plans to start buying more content from D&D Beyond. If I can't feel comfortable moving forward that this will be a reliable integration point between the FVTT and D&D Beyond, I would have zero reason to continue purchasing anything from D&D Beyond.
For now, I just hope my current campaign can be completed in the coming weeks/months without much disruption. I'll be holding off on purchasing more content from here until I can feel more confident that my use for it will remain intact in the long term. If not, I'll be canceling my subscription and looking elsewhere in the future.
Thanks for your consideration.
P.S. I've already had a hero lab subscription with much of the content that I want and need. I *only* purchased here to make use of the excellent work on the VTTA module and extension.
I would like to add my thanks to the DEV team for responding and that from all of us I think its safe to say we would like this to continue and be enhanced as time goes on.
My own opinion on this is I understand the need to keep this as "undocumented" to allow you to make rapid enhancements to the tool and the data it provides, I think this is a good move, we just dont want to see it go away, I think is the concern from everyone.
Thank you Molster! Your comment of: With that said, we have not, and will not be blocking anyone from using it, as long as they are aware of its unsupported state, and that it may change as we continue to refine and develop more features, and that it is ultimately "unsupported"
That sets my mind at ease. It's obvious you're constantly making improvements and enhancements to the site. Everything has been really great so far and I look forward to seeing what else is in store for us. As long as we can continue to utilize our purchased content through VTTAssets into Foundry, that's what matters to me the most right now. We realize it's 'unsupported' and I have the utmost faith that SolFolango will remain on top of things.
Understand all the arguments presented from the Dev side. But I am currently running multiple Campaigns that depends on these endpoints and functionality for usage with VTTs.
They are a major reason I continue to use DNDB as well as purchase new content.
Let's hope we can ll work toghether to make this an even more awesome platform.
Cheers!
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
I agree completely. I have invested my money mostly to support Critical Role. This was a useful way for that investment to payoff in my games. It seems like a wasted opportunity to shut off that compatibility and synergy.
I could have sworn I saw an announcement about the endpoints being shut down, but can't currently find it. That said, here's one of the warning I was talking about: https://www.dndbeyond.com/forums/d-d-beyond-general/general-discussion/49086-d-d-beyond-terms-of-service-api?comment=3
EDIT: Found the announcement I was remembering; it was in the most recent changelog.
Trying to Decide if DDB is for you? A few helpful threads: A Buyer's Guide to DDB; What I/We Bought and Why; How some DMs use DDB; A Newer Thread on Using DDB to Play
Helpful threads on other topics: Homebrew FAQ by IamSposta; Accessing Content by ConalTheGreat;
Check your entitlements here. | Support Ticket LInk
The integration with Foundry VTTis the ;ain reaso why I took a D&D Beyond subscription so I can make plenty of characters to play in Foundry VTT. Fix it!
Just another voice that used the integration with Foundry VTT. Woulde be really sad if this feature no longer worked :P
The main reason i bought all the source books on here was to allow my players to Create characters and manage campaign at eash with the character sheets in DND beyond Im able to import Level changes and new characters into my games with ease for new players and now u have removed the part that makes DND beyond Worth while. Please add this back at least until you release your API Why remove this before. I am able to import i will be requesting a refund on my Dungon Master subscription.
I'll add in my support for keeping a stable way of getting character data. I own every book on dndbeyond, and my intent is to continue to buy every book that comes out because both I and my players really love the character building and managing functionality, and I love running adventures with digital resources. And it's for that reason that having a direct integration between dndbeyond and my VTT is super nice, since it allows me to continue to use and support dndbeyond and my players get the full dndbeyond experience. If that integration does not exist, then I am forced to stop using dndbeyond and just simply use the in-app VTT character sheets and do everything manually there, and everyone loses: my players and I lose functionality and I have no reason to buy and subsequent books from dndbeyond.
I know you are working towards a public API, which is fantastic, and I know will be a huge boon to all these integrations. But I do hope that until then you can continue to offer unofficial, but relatively stable ways for the current integrations to continue working.
I'm convinced that, a la Microsoft, Fandom believes that if they can force us to choose between this site, and our VTT, we will choose them over our VTT, because DDB "has the official docs" and many VTTs do not (although FG and R20 do, of course). They're counting on the strength of that character sheet maker of theirs. But it's not enough all by itself, and they don't really have anything else but that. Every other feature (encounter builder, combat tracker, dice roller) is already available in multiple other places, and nearly always better-implemented than what they have here.
WOTC lies. We know that WOTC lies. WOTC knows that we know that WOTC lies. We know that WOTC knows that we know that WOTC lies. And still they lie.
Because of the above (a paraphrase from Orwell) I no longer post to the forums -- PM me if you need help or anything.
-
View User Profile
-
View Posts
-
Send Message
Grandfathered AccessHey everyone!
I just wanted to clear up a few things here, and give some context around the changes and expectations for the future. I think the community being able to come together, and create amazing tools that benefit all types of use cases is amazing, and an important part of what let D&D Beyond become what it is today. I want to thank everyone here for voicing how important an API is to them, as seeing feedback is the most powerful way to see how important a feature is to the masses.
Now for context on the current undocumented API. If you have been watching the developer updates, you know we just finished up a massive rework of the character sheet. Up to this point, all the logic still lived on the same nodes as our website. This caused some serious issues with performance and we needed to get this logic off ASAP. The logic is now in its own service, and also why the URL has changed. However, for all the same reason it was undocumented and "unsupported" as before, is still true today. There is still more work to be done, such as now moving all our data out into its own DB as well for example. We don't want to officially support this, due to the rapid changes that can happen at this stage, and no real way to monitor who is going to be affected. With that said, we have not, and will not be blocking anyone from using it, as long as they are aware of its unsupported state, and that it may change as we continue to refine and develop more features, and that it is ultimately "unsupported"
The main feedback at this stage we are looking for, would be from various app developers, and knowing what they would be looking for in a fully supported API.
Edit
Looks like adam also covered this on the dev update!
I do stuff, sometimes.
We did get a response on Twitch today. Please feel free to watch it.
https://www.twitch.tv/videos/647817155?t=0h49m16s
UPDATE: I see we got an official response above. So that maybe better than the twitch stream
Great to see, thanks devs. I feel I'm still missing something though cuz it sounds like we can still copy and create an import into roll20. Maybe I'm missing something (or I caught the dumb big time) but I can't seem to get it to work.
Very awesome to get a reply on stream and here.
Getting the Devs of the community in to give feedback what they wish for is a great step towards a great API.
I want to thank the Molster and the rest of the D&D Beyond staff to be extremely responsive about the matter and I will look forward to the release of the official API.
In the meantime, we do have a mutual understanding that some changes do need to take place and now having an establish communication channel will make changes in the future way more visible to us, and therefore we will be able to prepare instead of reacting to necessary changes. That is overall a great thing.
Coming from a datacenter background and now having watched the relevant part of today's stream, I can just say that I do understand the need for some of those changes: The main service has priority when it comes to availability, and the will to "get it right" and not half-assed speaks for you. I am looking forward to the official API and will be available for feedback regarding the design (and of course beta-testing) of it.
Thank you again, your response was something I desired, but honestly, did not expect in regards of pleasantness and quickness. Also sorry for my english. I sound ******'y when I try to sound somewhat official.
Sebastian
This is amazing news! Thank you for taking the time to respond
I just want to add my voice to this for the future. A friend and I recently purchased content (much of which I already owned) on D&D Beyond, soley because of the VTTA module that allows us to make use of that content on the Foundry VTT.
It is only because of this module that I've had plans to start buying more content from D&D Beyond. If I can't feel comfortable moving forward that this will be a reliable integration point between the FVTT and D&D Beyond, I would have zero reason to continue purchasing anything from D&D Beyond.
For now, I just hope my current campaign can be completed in the coming weeks/months without much disruption. I'll be holding off on purchasing more content from here until I can feel more confident that my use for it will remain intact in the long term. If not, I'll be canceling my subscription and looking elsewhere in the future.
Thanks for your consideration.
P.S. I've already had a hero lab subscription with much of the content that I want and need. I *only* purchased here to make use of the excellent work on the VTTA module and extension.
I would like to add my thanks to the DEV team for responding and that from all of us I think its safe to say we would like this to continue and be enhanced as time goes on.
My own opinion on this is I understand the need to keep this as "undocumented" to allow you to make rapid enhancements to the tool and the data it provides, I think this is a good move, we just dont want to see it go away, I think is the concern from everyone.
Enhancements, keep them coming!!
Thank you to the DDB team for responding to our concerns. This was a wonderfully welcome response. As always, love everything you guys do!
Thank you Molster! Your comment of: With that said, we have not, and will not be blocking anyone from using it, as long as they are aware of its unsupported state, and that it may change as we continue to refine and develop more features, and that it is ultimately "unsupported"
That sets my mind at ease. It's obvious you're constantly making improvements and enhancements to the site. Everything has been really great so far and I look forward to seeing what else is in store for us. As long as we can continue to utilize our purchased content through VTTAssets into Foundry, that's what matters to me the most right now. We realize it's 'unsupported' and I have the utmost faith that SolFolango will remain on top of things.
Thank you for the quick and reassuring response!
Thank you for the update!
Thanks for the response guys, this is very reassuring. Quick finance check and Legendary Bundle time, I think....
Thanks for keeping everyone in the loop.
Understand all the arguments presented from the Dev side. But I am currently running multiple Campaigns that depends on these endpoints and functionality for usage with VTTs.
They are a major reason I continue to use DNDB as well as purchase new content.
Let's hope we can ll work toghether to make this an even more awesome platform.
Cheers!