I consistently encounter a JavaScript bug when I go to the page that shows me a particular encounter that I've built. After I've clicked on one of the monsters included in the encounter to show their stat block, if I click any other monster in the encounter, the entire "body" of the page (not the HTML BODY element but just the main content aspect of the design) will disappear, leaving only the header, the footer, and a "Report feedback" button.
I've pasted the error itself below (I had a screen capture but couldn't find a way to upload it here since inserting an image required it to be at a URL on the Internet).
I have a few extensions in my browser related to work, but I've been running all of these since well before this error started manifesting. I run a VPN for work, but this error happens regardless of whether I'm connecting to it — and again, I've been using this particular work VPN for a long time, possibly longer than D&D Beyond has been around.
Hmm... looks like Beyond20 is the culprit. Something in a recent update must have screwed things up with the Encounter Builder. I also discovered that the error only seems to occur once you've clicked into a homebrew monster and then try to click to a non-homebrew monster in the same encounter. If I click between official monsters, the error never occurs.
Hmm... looks like Beyond20 is the culprit. Something in a recent update must have screwed things up with the Encounter Builder. I also discovered that the error only seems to occur once you've clicked into a homebrew monster and then try to click to a non-homebrew monster in the same encounter. If I click between official monsters, the error never occurs.
Yeah, this is why disabling extensions are the first port of call. Sometimes DDB pushes out updates that the extensions don't like, sometimes the extensions get updates DDB doesn't like. So it's always wise to disable them first, to rule it out.
Yeah, this is why disabling extensions are the first port of call. Sometimes DDB pushes out updates that the extensions don't like, sometimes the extensions get updates DDB doesn't like. So it's always wise to disable them first, to rule it out.
Makes sense. I filed a bug at the extension GitHub last night. If I have time, maybe I'll just fix it myself. LOL
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
I consistently encounter a JavaScript bug when I go to the page that shows me a particular encounter that I've built. After I've clicked on one of the monsters included in the encounter to show their stat block, if I click any other monster in the encounter, the entire "body" of the page (not the HTML BODY element but just the main content aspect of the design) will disappear, leaving only the header, the footer, and a "Report feedback" button.
I've pasted the error itself below (I had a screen capture but couldn't find a way to upload it here since inserting an image required it to be at a URL on the Internet).
Are you running any extensions? Do you use a VPN?
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
I have a few extensions in my browser related to work, but I've been running all of these since well before this error started manifesting. I run a VPN for work, but this error happens regardless of whether I'm connecting to it — and again, I've been using this particular work VPN for a long time, possibly longer than D&D Beyond has been around.
Hmm... looks like Beyond20 is the culprit. Something in a recent update must have screwed things up with the Encounter Builder. I also discovered that the error only seems to occur once you've clicked into a homebrew monster and then try to click to a non-homebrew monster in the same encounter. If I click between official monsters, the error never occurs.
Yeah, this is why disabling extensions are the first port of call. Sometimes DDB pushes out updates that the extensions don't like, sometimes the extensions get updates DDB doesn't like. So it's always wise to disable them first, to rule it out.
Find my D&D Beyond articles here
Makes sense. I filed a bug at the extension GitHub last night. If I have time, maybe I'll just fix it myself. LOL