Closed MadManNBlueBox closed 2 years ago
It should work fine with the latest 5E unless something changed since Sunday. I used it then and had no issues.
I am running Foundry on Forge (not sure if that matters), Version 9.269, DnD5e 1.6.3
So just tested something. It appears that when its a character sheet that was brought over using D&D Beyond importer is when it has the issue. Other sheets that were created in Foundry work fine.
Ah that sounds more like a D&D Beyond Importer issue then, I believe.
On Wed, Jun 29, 2022 at 7:35 PM MadManNBlueBox @.***> wrote:
So just tested something. It appears that when its a character sheet that was brought over using D&D Beyond importer is when it has the issue. Other sheets that were created in Foundry work fine.
— Reply to this email directly, view it on GitHub https://github.com/jopeek/fvtt-dndbeyond-character-sheet/issues/28#issuecomment-1170683401, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJBV6XYAKWKMFX5I4GGVATVRUBXJANCNFSM52HFIXLA . You are receiving this because you commented.Message ID: @.***>
-- Jan Ole Peek http://www.janolepeek.com/
I will go drop a note on their repository
You're using DEFAULT_TOKEN
which is no longer valid, you need to use CONST.DEFAULT_TOKEN
Just published 1.8.4 with the fix. Thanks for all the troubleshooting!
It looks like there are some other issues similar to this already open but they are a bit older. Are you guys working on an update to get this working with the current version of the DnD5e system?