ACKS Character Sheet (Unofficial)

This is my custom character sheet for Autarch's Adventurer Conqueror King System RPG, published under OGL 1.0.&nbsp; <a href="https://github.com/omonubi/ACKS-by-omonubi" rel="nofollow">https://github.com/omonubi/ACKS-by-omonubi</a> While this is currently 'Unofficial', I'm working with the game author (Alexander Macris) to use this sheet as a starting point for an official, published version that supports translation and compendium features. It's not fabulous-looking, but (IMO) it's simple, more-or-less complete, and easy to read/use. Being this is my first published anything (in GitHub or Roll20), I'm open to feedback on how to improve what I've offered. In particular, I'm interested in styling tips and un-realized architectural issues that might impede the sheet's further implementation with more advanced Roll20 features. If you find issues or missing features that you'd like to see added, please use the Issues log on the git. Post usage questions here and I'll try to respond. Bonus Question: How do I get this 'published' to the Roll20 character sheet git?

omonubi said: Bonus Question: How do I get this 'published' to the Roll20 character sheet git? The wiki can help you there. Also my site has a step by step guide: <a href="https://cybersphere.me/publishing-sheets-to-github/" rel="nofollow">https://cybersphere.me/publishing-sheets-to-github/</a>

GiGs said: The wiki can help you there. Also my site has a step by step guide: <a href="https://cybersphere.me/publishing-sheets-to-github/" rel="nofollow">https://cybersphere.me/publishing-sheets-to-github/</a> Thanks! However, under "Publishing Your First Sheet", Step 7, after I enter a name and description and click "Commit to master ", I receive this error: &nbsp; A little research indicates that the files and folder I copied into the roll20-character-sheets fork/clone are not added to the git index. I tried using 'git add' to do this and it appeared &nbsp;to work, but I'm still receiving the error in git desktop. My editor is VS Code (which also immediately saw the folder I added to the repo but doesn't indicate there's anything unstaged.) I'm new to git/GitHub so please exucse my ignorance if I'm overlooking something obvious.

I figured it out. When I copied over my folder into the fork, I copied the stand-alone repo, posed above. This contained the hidden .git folder. After removing the folder and trying again, it worked fine.&nbsp; However, after the pull request to Roll20, they declined the submission, recommending that I instead revise the currently un-maintained ACKS sheet posted to in the repo. I wouldn't necessarily mind doing this, but I'd be required to maintain current field names for backwards compatibility. That might require more effort than its worth on my part. Besides, I'm also trying to go the "official" sheet route w/ the game publisher, in which case a community-posted version is probably not necessary.&nbsp; Thanks again for the help!

I missed your earlier post, I'm glad you figured it out but its sad that the sheet was rejected. If your sheet has the support the game creator, you can suggest that this be treated as officially licensed sheet. Roll20 generally allows one licensed sheet, and one community sheet to exist alongside each other. There might need to be some communication with the game's creator, but this is a posisble avenue to proceed Alternatively, if your sheet is better than the existing community sheet, you can replace it with your sheet. But it's best to include a versioning script that swaps attribute names from the old sheet to the new sheet, so people don't lose data. This process would be: Create a sheet worker that runs on sheet:opened, it checks the current value of a version attribute (the is created just for this check) If the version attribute doesnt exist or is below the desired version, run a version update sheet worker This sheet worker create copies of the existing attributes with the new names for the sheet, and does any other necessary initialisation You need the version check so that this worker doesn't keep running and overwriting any new changes with old values In this way you can easily transfer data from the old sheet to the new. As an alternative, you could also use the same attribute names as the old sheet used, if they make sense - but the version change method above handles that.

The publisher status approach is making progress, so I'll try that first. If it washes out, then I'll definitely take a look at using sheet:opened &nbsp;to update the community version in the git. Thanks!