Ah, ok, in that case, you don't want the readonly on it. Autocalcs are finicky about how you enter attribute calls for them to resolve properly. I'd recommend putting something simple in the pm-formula field to test your basic html; something like just "4" to see if it propagates to your pm_max correctly. I think that this should work, as I don't see anything wrong with your disabled setup. If that simple test is the case, then the problem is likely with your fomula. I would do a few different troubleshooting steps to investigate the formula: output the formula to chat in a roll and out of a roll. Do this by sending a chat message of @{test character|pm-formula} = [[@{test character|pm-formula}]] . This lets you easily see what each value of the formula is resolving to and what the total is. If the above gives you the results you expect, try wrapping attribute calls in parentheses (e.g. @{carac-0-pm} becomes (@{carac-0-pm}) ) Unfortunately, I don't use autocalcs in my sheets, so I'm not sure where to go for troubleshooting after this. EDIT: and actually, the readonly tag on your pm-formula attribute may be what's causing the issue. autocalcs and sheetworkers don't play nicely together, and readonly is to sheetworkers what disabled is to autocalcs. You also don't want that attribute to be readonly as then there's no way for players to edit it, and therefore no reason to display the pm-formula attribute or even have it as a separate attribute. EDIT 2: And, sorry, I realized you put that readonly tag in there because of my previous post. That was a typo, and should have read disabled; although you don't want this attribute to be disabled either since it looks like you want it to be player editable
