[Exalted 2e] Manipulation error

I am trying to start a game of Exalted 2e, and I am working with the character sheet.   I have noticed that there is no direct way to roll Attributes or Skills directly from their listing, so I tried just using a Generic Attack/Damage window to set up the roll I needed.   I tried Charisma + Presence "Attack", and it gave me proper results I think Attack! Attribute ( 5 ) + Ability ( 1 ) + Specialty ( 0 ) + Accuracy ( 0 ) + Bonus Dice ( 0 ) + Bonus Successes ( 0 ) = 4 Successes But when I try Manipulation + Presence (or Manipulation + anything really) you get  No attribute was found for @{Character|Maniuplation} the error is that it is looking for maniUplation, not Manipulation...  there is a misspelling...  I have tried adding "Manipulation" to the Attributes and Abilities tab, but to no effect. so I think whoever has access to the back end just needs to fix the typo of Maniuplation to Manipulation.. Thank you.

Hi Agonar,&nbsp; I suggest contacting the creators of this sheet: <a href="https://app.roll20.net/users/235259/lithl" rel="nofollow">https://app.roll20.net/users/235259/lithl</a> <a href="https://app.roll20.net/users/442/ranko" rel="nofollow">https://app.roll20.net/users/442/ranko</a> <a href="https://app.roll20.net/users/2861257/briteblade" rel="nofollow">https://app.roll20.net/users/2861257/briteblade</a> <a href="https://app.roll20.net/users/4952661/adrail" rel="nofollow">https://app.roll20.net/users/4952661/adrail</a> If you don't get a response from the creators then I'd post a request for someone to update the sheet.&nbsp; Edit: With that said, I was not able to replicate the issue. @{selected|manipulation} worked correctly for me.&nbsp; I checked the checkbox and the radio elements, they are all spelled correctly (Manipulation).

that is weird.. I went to the html file in the github directory, and found the lines where it is misspelled "Maniuplation".. lines 722 and 778 So, in the meantime, I am taking the code and pasting it to my game as a custom sheet with the correction, but just wanted to keep this problem from happening to anyone else.&nbsp; So I will definitely try to contact those users.. Thank you for the links.

Okay, went to the next step and forked the files and fixed the typo, then submitted a pull request...&nbsp;&nbsp; So maybe that will make sure that it gets fixed for everyone else.