Choosing the "mobile" feat in the character creator will cause the website to move to a page that states:
Whoops! We rolled a 1 on our API check. We're heading into town to visit the blacksmith for repairs.
Try again after a Short Rest.
Error Code
b8d9f65cb40d4e8da0a23b112de36a9f
Version
6.1.2
The character sheet will not save mobility as the feat. It resets to none selected. It also appears to be permanently attached to my character sheet and cannot be removed, though it doesn't appear to be granting the bonuses correctly.
I suspect this is an issue caused by the homebrew variant race. The variant tortle you’ve created uses the modifier Set > Speed (Walking) > 20:
I suspect you used that modifier after realizing that setting the innate walking speed did not work? This is because in the main tortle race, innate walking speed is 30, and so the character sheet will intelligently use the higher of the two. The reason this isn’t affected by the variant race’s Speed trait replacing the base race Speed trait, is that base racial speed is not a modifier in the Speed trait, but rather is defined in the race’s Basic Information section:
My suspicion in this case is that the Mobile feat is attempting to modify your character’s walking speed, but it having been “fixed” at 20 ft., the feat is unable to do so and encounters an unexpected error.
I’d recommend recreating the Garados Tortle as its own independent race, and grouping it under the Tortle race. This way you will be able to set your own innate walking speed, which should avoid this issue!
I created a new race and it now "applies" the movement bonus. However my character sheet now has the Mobile feat permanently attached and it cannot be removed.
Hmm. Perhaps some wires got crossed when the initial issue occurred!
Can you try creating a copy of the character and seeing whether the issue persists there? If this solves it, and you are able to otherwise bring the copy up to the same state as the original, then that may be all that's needed! Otherwise, this might require that you submit a Support ticket to resolve.
Choosing the "mobile" feat in the character creator will cause the website to move to a page that states:
The character sheet will not save mobility as the feat. It resets to none selected. It also appears to be permanently attached to my character sheet and cannot be removed, though it doesn't appear to be granting the bonuses correctly.
Character sheet: https://www.dndbeyond.com/profile/bugbearmagic/characters/46115604
Please post the url to your character sheet so someone can take a look.
Helpful rewriter of Japanese->English translation and delver into software codebases (she/e/they)
-
View User Profile
-
View Posts
-
Send Message
AlumniI suspect this is an issue caused by the homebrew variant race. The variant tortle you’ve created uses the modifier Set > Speed (Walking) > 20:
I suspect you used that modifier after realizing that setting the innate walking speed did not work? This is because in the main tortle race, innate walking speed is 30, and so the character sheet will intelligently use the higher of the two. The reason this isn’t affected by the variant race’s Speed trait replacing the base race Speed trait, is that base racial speed is not a modifier in the Speed trait, but rather is defined in the race’s Basic Information section:
My suspicion in this case is that the Mobile feat is attempting to modify your character’s walking speed, but it having been “fixed” at 20 ft., the feat is unable to do so and encounters an unexpected error.
I’d recommend recreating the Garados Tortle as its own independent race, and grouping it under the Tortle race. This way you will be able to set your own innate walking speed, which should avoid this issue!
I created a new race and it now "applies" the movement bonus. However my character sheet now has the Mobile feat permanently attached and it cannot be removed.
-
View User Profile
-
View Posts
-
Send Message
AlumniHmm. Perhaps some wires got crossed when the initial issue occurred!
Can you try creating a copy of the character and seeing whether the issue persists there? If this solves it, and you are able to otherwise bring the copy up to the same state as the original, then that may be all that's needed! Otherwise, this might require that you submit a Support ticket to resolve.
A copy doesn't seem to resolve the issue. I'll open up a ticket.