Its doing it to most of the players characters of my older campaign... I have not brought to the players attention yet but I would like to know what's going on...
Had another one in my group have this happen to yesterday. Has anyone had their character recovered after this occurred? The error does say it is logged and someone will fix it and I am asking:
1. Is D&DBEYOND actually reading the error logs and responding without submitting a ticket?
2. Once someone submits a ticket how quickly is it being fixed?
3. I have heard the issue may be related to equipped home brew items and changes being made to the backend in prep for the changes coming. If this is so can not D&DBEYOND add some command that auto unequips all items that the owner of a character can access and enable?
1: yes that appears to be whats going on, either that or they arent doing anything at all
2: I took 3 months last time for an issue to be fixed when i reported it.
3: Yes that seems the issue: however you cant unequip items if they arent able to open the character sheet to begin with, and i cant view it as a dm either.
the easy thing would be for them to have you opt in to which version of the character sheet you want to be using untill the update is fully released.
Since this is just a database with a rules layer and a presentation layer it would not be difficult for them to put a piece of code on a support page that:
A: Does a look at the signed in account and presents a listing of all their characters sorted by Character name.
B: Lets the owner select the erroring character and executing the command below after verifying ownership.
C: The command executes code that switched the equipped toggle for all equipment on the character to unchecked in the database and saves the record with Recovered appended to the end of the character’s name.
D: Once it verifies the record can be accessed on the presentation layer it sends by email the link to the recovered character.
This will allow users to fix the issue that they otherwise could not because they cannot get back to the character once the beholder shows up. This could be done in 1 hour by a decent coder. Adding the support page is another hour. I used to build N-Tier applications accessed via the web. I know what I am talking about here and it would be secure.
It would eliminate the backlog for any problems resulting from new coding causing character sheets with home brew issues conflicting with what is to come, I suspect on the 23.
I was trying to load on IPad and kept having this issue… long story short my IOS was out of date and updating it fixed this issue completely... worth a try if you’re having issues!
IDK if this will help for anyone here, but there are two things I want to note because I fixed my character that was having this problem
1. the problem that caused this for me was a homebrew item called the "fireball gun" My char sheet said this error whenever it was equipped
2. and this is how I primarily fixed it; you can still access the char on the dnd byond mobile app that has this error
Now, here's the solution to the problem, or at least the one that I think will work if you don't want to delete every home brew item. 1. unequip each home brew item on the mobile app and then test if the same error appears on the website wether it be mobile website or PC website. 2. on the website, equip each item one by one until the error appears again and once the item or multiple items that are causing the issues are found, simply don't equip them
could there be a way the website can fix this... probably, am I gonna wait on that? No, If I need a custom armour that gives certain bonus to ac or immunity or resistances I will just customise that part of the sheet and leave the armour unequip I don't like this glitch but it happened and I am moving past it
I installed the mobile app on my phone and unequipped everything on them and then gained access to all of the characters all of my players had lost access to.
Thank you for your suggestion. It worked.
I am stunned that a developer or support tech has not discovered this as a solution to gain access to characters with this error.
In addition to the solution I made in #12 above it is now apparent DNDBEYOND could make a webpage to emulate the inventory function on the mobile app to a support page on the main website with access controlled by the logged in account.
It is also apparent this is going to be a continuing problem that may well get much worse depending on what they may do tomorrow. It would be nice to know exactly what they are going to do tomorrow.
Last would be a question to DNDBEYOND...What impacts, if any, will be coming to homebrew from the changes coming in the future?
whenever i click on the characters in my campaign it gives me:
The error that summoned it has been logged and the D&D Beyond team will hit the forge to make repairs. Back to Previous Page
Character App (dndbeyond.com) @dndbeyond/character-app@1.59.48
it never gave me this issue before and its only when i try to view characters... on the mobile app my players can view their sheets however i cant
Its doing it to most of the players characters of my older campaign... I have not brought to the players attention yet but I would like to know what's going on...
Verified with the players they also get the following:
The error that summoned it has been logged and the D&D Beyond team will hit the forge to make repairs. Back to Previous Page
Character App (dndbeyond.com) @dndbeyond/character-app@1.59.48
Three of the seven players cannot access their character in that campaign...
What is going on.
Hi all
I have this issue with only one of my characters ( I have 7) it's totally bizarre I'm the only player effected in my campaign
Any news if they are looking in to this?
glad to see im not the only one who is suffering this weird glitch
nothing yet, i filed a formal report and complaint and nothing back yet
also have this problem, how do you make a complaint
you contact customer support
that dude i have and they are working on fingers crossed it gets sorted soon
Had another one in my group have this happen to yesterday. Has anyone had their character recovered after this occurred? The error does say it is logged and someone will fix it and I am asking:
1. Is D&DBEYOND actually reading the error logs and responding without submitting a ticket?
2. Once someone submits a ticket how quickly is it being fixed?
3. I have heard the issue may be related to equipped home brew items and changes being made to the backend in prep for the changes coming. If this is so can not D&DBEYOND add some command that auto unequips all items that the owner of a character can access and enable?
1: yes that appears to be whats going on, either that or they arent doing anything at all
2: I took 3 months last time for an issue to be fixed when i reported it.
3: Yes that seems the issue: however you cant unequip items if they arent able to open the character sheet to begin with, and i cant view it as a dm either.
the easy thing would be for them to have you opt in to which version of the character sheet you want to be using untill the update is fully released.
Since this is just a database with a rules layer and a presentation layer it would not be difficult for them to put a piece of code on a support page that:
A: Does a look at the signed in account and presents a listing of all their characters sorted by Character name.
B: Lets the owner select the erroring character and executing the command below after verifying ownership.
C: The command executes code that switched the equipped toggle for all equipment on the character to unchecked in the database and saves the record with Recovered appended to the end of the character’s name.
D: Once it verifies the record can be accessed on the presentation layer it sends by email the link to the recovered character.
This will allow users to fix the issue that they otherwise could not because they cannot get back to the character once the beholder shows up. This could be done in 1 hour by a decent coder. Adding the support page is another hour. I used to build N-Tier applications accessed via the web. I know what I am talking about here and it would be secure.
It would eliminate the backlog for any problems resulting from new coding causing character sheets with home brew issues conflicting with what is to come, I suspect on the 23.
I was trying to load on IPad and kept having this issue… long story short my IOS was out of date and updating it fixed this issue completely... worth a try if you’re having issues!
IDK if this will help for anyone here, but there are two things I want to note because I fixed my character that was having this problem
1. the problem that caused this for me was a homebrew item called the "fireball gun" My char sheet said this error whenever it was equipped
2. and this is how I primarily fixed it; you can still access the char on the dnd byond mobile app that has this error
Now, here's the solution to the problem, or at least the one that I think will work if you don't want to delete every home brew item.
1. unequip each home brew item on the mobile app and then test if the same error appears on the website wether it be mobile website or PC website.
2. on the website, equip each item one by one until the error appears again and once the item or multiple items that are causing the issues are found, simply don't equip them
could there be a way the website can fix this... probably, am I gonna wait on that? No, If I need a custom armour that gives certain bonus to ac or immunity or resistances I will just customise that part of the sheet and leave the armour unequip I don't like this glitch but it happened and I am moving past it
I installed the mobile app on my phone and unequipped everything on them and then gained access to all of the characters all of my players had lost access to.
Thank you for your suggestion. It worked.
I am stunned that a developer or support tech has not discovered this as a solution to gain access to characters with this error.
In addition to the solution I made in #12 above it is now apparent DNDBEYOND could make a webpage to emulate the inventory function on the mobile app to a support page on the main website with access controlled by the logged in account.
It is also apparent this is going to be a continuing problem that may well get much worse depending on what they may do tomorrow. It would be nice to know exactly what they are going to do tomorrow.
Last would be a question to DNDBEYOND...What impacts, if any, will be coming to homebrew from the changes coming in the future?
this work for me! awesome thank you!
Thank you, the mobile app fix, worked lol