Roll20 uses cookies to improve your experience on our site. Cookies enable you to enjoy certain features, social sharing functionality, and tailor message and display ads to your interests on our site and others. They also help us understand how our site is being used. By continuing to use our site, you consent to our use of cookies. Update your cookie preferences .
×
Create a free account

Level+ Charactermancer bug

One of the players in my game is multiclassing, and the charactermancer is reporting that it will change their level from Cleric 2/Wizard 1 to Cleric 3/Wizard 0, instead of Cleric 3/Wizard 1 (They have a 4th level character, for reference, and are levelling up from 3rd level) The link below is a picture of what the Charactermancer is telling them, and the second is the choices they made before completing it. <a href="https://cdn.discordapp.com/attachments/549686579178766338/586648660473937948/unknown.png" rel="nofollow">https://cdn.discordapp.com/attachments/549686579178766338/586648660473937948/unknown.png</a> <a href="https://cdn.discordapp.com/attachments/549686579178766338/586648794624425994/unknown.png" rel="nofollow">https://cdn.discordapp.com/attachments/549686579178766338/586648794624425994/unknown.png</a> This is strictly a visual bug , as when they complete the charactermancer, it does not actually change their class to read Cleric 3/Wizard 0
Hey there Andriel, Thanks for bringing this to our attention! Has your player tried: clearing their cache disabling all extensions/add-ons ensuring they're using the latest version of Chrome/Firefox? It may only be a visual bug, but we'd still like to help take care of it. Please keep us informed.
After asking them to go through those steps, they can confirm that they are still experiencing the issue. When they level up, it shows Cleric 3/Wizard 0 in the charactermancer level+, but their character sheet after clicking finish will show Cleric 3/Wizard 1
Thank you for your (and your player's) patience - A Charactermancer fix has just been rolled out as of a few minutes ago, hopefully this will help to take care of the issue. If you still end up experiencing this bug, please let us know!