Troubleshooting

This page covers common issues you may encounter when building, exporting, or testing your character sheet. Most troubleshooting tips below reference Roll20 as the current export target.

Layout Issues

Sheet looks different on Roll20 than in the editor

Roll20 applies its own base stylesheet to all character sheets. Small differences in spacing, font rendering, and default styles are normal. We try to ensure that all Roll20 default styling is reset before applying your sheet's styles, but Roll20 may have updated their styles. To minimize differences:

Always test your exported sheet on Roll20 after major layout changes
Avoid relying on browser-specific CSS features

Components are not visible on the canvas

If you added a component but cannot see it on the canvas:

Check the Element Hierarchy -- it may be inside a collapsed container
The component may have zero dimensions. Select it in the hierarchy and check its styles (width/height)
It may be hidden behind another element. Try reordering in the hierarchy

Canvas zoom and scroll

The Layout Editor canvas supports scrolling to navigate your sheet preview. If the canvas seems unresponsive, click on the canvas area first to ensure it has focus.

Logic Issues

Calculations not updating on Roll20

If your logic graph works in the editor but calculations do not update on Roll20:

Check attribute names -- The attribute names in your logic nodes must exactly match the name attributes on your layout components. Case matters.
Verify the trigger -- Sheet workers fire when their watched attributes change. If a calculation depends on an attribute that is not being watched, it will not update. Make sure your Attribute nodes read from the correct source attributes.
Check the browser console -- Open developer tools (F12) on Roll20 and look for JavaScript errors in the Console tab. Sheet worker errors appear here.

Logic graph looks correct but produces wrong values

Check the order of inputs on Subtract and Divide nodes. These are order-dependent: A - B is not the same as B - A.
Verify Floor vs. Round -- D&D typically rounds down (Floor). Using Round instead can produce different results for values like 2.5.
Check for type mismatches -- If an attribute stores a value as text (e.g., "14" instead of the number 14), math nodes may not process it correctly. Use a Parse Number node to convert text to a number.

Tab Switching Issues

Tabs not switching on Roll20

The tab system uses a CSS checkbox technique. If tabs are not switching:

Make sure each tab button and its corresponding content container reference the same control attribute
The control attribute must be a hidden input (radio button or checkbox) in your layout
Check that the CSS for showing/hiding tab content is correct -- tab content containers need display: none by default and a rule that shows them when the matching radio button is checked

Roll Template Issues

Roll template not showing in chat

Check the template name -- The name in your roll button macro (&{template:name}) must exactly match the template name you defined in the Roll Template Editor
Verify the template is exported -- Roll template HTML is embedded at the end of sheet.html. Open the file and search for <rolltemplate to confirm it is there
Check field names -- The {{fieldname=value}} entries in your macro must match the field names in your template layout

Conditional sections not appearing

Verify that the scenario data matches the conditions you set up. For example, a "rollWasCrit" block only shows when the roll is flagged as a critical hit
Check if the condition is inverted when it should not be (or vice versa)
Use ghost mode to see all conditional blocks and verify their settings

Export Issues

Validation errors preventing export

See the Validation page for a complete list of validation errors and how to fix each one.

Exported CSS not applying

Make sure you pasted the contents of sheet.css into the CSS Styling tab in Roll20 game settings (not the HTML tab)
Check that your selectors include the .charsheet prefix
Roll20 has CSS size limits. If your stylesheet is very large, some rules at the end may be truncated

Close browser developer tools if they are open (they can slow down complex pages)
Consider splitting very large logic graphs into batch nodes to reduce the total node count on the canvas

Getting More Help

If you cannot find a solution here:

Check the Roll20 wiki for Roll20-specific issues
Review the relevant section of this documentation for detailed feature explanations
Test your exported files in Roll20's Sheet Sandbox for faster debugging iteration
Post a bug report on the Kurohyou Studios Discord