Pages are unaware of updated information.
Whenever I (as the DM) or one of my players update information on their characters, everyone else looking at the information has to update the whole page manually to actually have the new information displayed.
This is true for the Character Builder, Character Sheet, Combat Tracker, Encounter Builder, and Campaign Manager. Non-character-information is also affected by this, e.g. the Homebrew Collection and Homebrew Details Pages.
It is one of the most upsetting problems on D&D Beyond in my opinion.
Using WebSockets, it is both easy and efficient traffic-wise to update data in realtime. Connecting to different API-endpoints using WebSockets can even enable live updating specific information instead of transmitting all the info on a page.
I found Socket.IO to be very easy and comfortable to work with, especially easy to integrate into existing RESTful APIs.
The most obvious use case is described in the problem section. As a DM, I want to be able to see the current information of a player on their Character Sheet. Updating it with WebSockets would allow the DM and the player to instantly see any changes made to the character or their inventory as they are made.
The DM Screen page is set to "planned" and making a modular approach to it would work great with WebSockets to show specific information updated whenever something happens.
The Player App is currently in Alpha and I am not a tester so I can not tell whether it already uses something like this but automatically reconnecting using WebSockets enables the app to easily switch between online and offline mode automatically.
The Encounter Builder and Combat Tracker are currently unable to make use of character information like HP but using WebSockets for live updates on that would enable the DM to manage HP in the Combat Tracker which would be visible to the player on their character sheet.
As the planned Development API has been mentioned on this site and on the Trello board, I am also including that use case. Being able to connect to an API using WebSockets would enable a more solid communication method for API endpoint connections.
I have found this topic being discussed in different places on the forums and in feature requests here on ZenDesk, but there are a lot of problems associating these things with each other. Some get no reaction, there is double-posting due to different terms used, etc. which is why I decided to create a new post and include the related posts I could find below to make it easier for the team to work with.
I created this because I desperately want to be able to use D&D Beyond in my next campaign instead of using it to create a character and switching to paper as updating the whole page takes some time which accumulates quickly.
Related Community Posts (ZenDesk)
Travis Huhn requested this and was seemingly ignored: https://dndbeyond.zendesk.com/hc/en-us/community/posts/360026614473-Real-time-updates-for-character-sheets
Tom M requested this feature with another proposition that is a pull method for updates (better than nothing but more expensive on data traffic calculation): https://dndbeyond.zendesk.com/hc/en-us/community/posts/360031902074-Load-Data-Asynchronously-On-Character-Sheet
Charles Toller requested this feature as a "sync" feature: https://dndbeyond.zendesk.com/hc/en-us/community/posts/360029478313-Sync-character-sheets-between-DM-and-Players
These are all the similar posts I could find within a reasonable time. If there are more posts like this, please leave a comment containing the link below so the devs/product owners/community managers can find it).
Please sign in to leave a comment.