Stephanie B. said: Thanks for the investigation! Can you tell me what game you tested this on? Garret W said: I did a little bit of investigating on my end. One of my players wanted to make a character that was a monk with a custom race and a custom background. It froze on 1 out of 13. I went back myself and made the same character as a DM, and it did the same. I then tried changing the custom background to one supplied by Charactermancer, and it did the same thing. I then went back and changed the character race to one supplied by the Charactermancer, and changed the background back to something custom, and this worked fine. It is my theory that the issue, in my case, is that there is something wrong with the creation of the custom race. The game is 5th Edition ( OGL by Roll20 ). I found out what my issue was. She made a race that was based on the Tabaxi (same ability score increases, same languages, armor, and tool proficiencies), but with several significant changes. It has a higher movement speed, dagger as a weapon proficiency, a tweaking of one trait (upping the climb speed from 20 to 25 feet and changing the modifier from Strength to dexterity for the trait 'Cat's Claws'), and changing two traits outright from normal Tabaxi. However, after doing some more testing, I figured out that the issue is that she still called it a Tabaxi in the name of the race. As soon as I changed the name of the race to something else, such as Cheetah, it started working just fine. My guess is that there is some kind of conflict when she tried to call it the same thing as a race in the system already since there is already data for that particular name. Just for giggles, I changed the race name to Lizardfolk, and it did the same thing. It just looks like you can't name your race the same as something already in the system, which is easy enough to fix. Once again, just for grins and giggles, I changed the name of the custom background to something that I know is already in the system (Urchin), and it froze there as well, and I'm guessing it's for that same reason. I don't know if that is on purpose, or if its a bug, but it's useful to know.