vince-roll20
92a75e80d2
Some Highlights 1. removed the preset attack buttons(no longer necessary) 2. drag/drop sheet rolls to the quick bar 3. In accordance to the latest Roll20 update, old ability macros will need to be updated to include "$X", where X is the row number of the repeating item 4. added more ability-based skills/info and gave them rolls 5. added Surprise and Initiative rolls (both rolls use @SurpriseBonus as modifier) 6. added editable macro-text for attacks (allows you to customize your macros) 7. added many new sections; 8. Movement: with auto-calc rates and current load indicators based off of carrying capacity vs total weight carried 9. Wealth: with coins total and carried 10. Equipment: repeating rows with auto-calc cost/weight. Armor, coins carried, and weapons costs/weight are included elsewhere and do not need to be included as equipment. 11. Sheet worker javascript was used for weight, cost, and encumbrance (thanks to Aaron's TAS script) 12. The encumbrance function sets a checkbox to the current load. Current load is determined by comparing the total weight carried to the amounts entered for a character's carrying capacities (normal, heavy, very heavy, and max). Currently these limits are entered by the sheet user. These limits may be automated in future updates. 13. Special Abilities: repeating rows w/roll and macro-text 14. Spells: repeating rows w/roll and macro-text 15. Notes 16. added Footer with sheet info 17. option to /w gm to-hit table info to the DM when making an attack 18. option to toggle a parchment background (void of coffee or Jolt Cola stains). ;-)
Roll20 Character Sheets
This repository is the collection of all the community-contributed character sheets that are available for use on Roll20.
Contributing
If you want to help improve an existing sheet, just clone this repository, make your changes, and submit a pull request. If you would like to contribute a new sheet for the community to use, just clone this repository and create a new folder with the name of the game system that the sheet is for. Then send a pull request. If you have any questions or aren't familiar with Github or git in general, feel free to drop us a line at team@roll20.net and we can help you get set up.
Creating a sheet.json File
When you are ready to submit your template for public use, create a sheet.json file in your sheet's folder (see the kitchensink folder for an example sheet.json file). The file has the following fields:
html: The name of the HTML file for the sheet (e.g.kitchensink.html)css: The name of the CSS file for the sheet (e.g.kitchensink.css)authors: A simple string telling who contributed toward the sheet (e.g.Riley Dutton)roll20userid: A simple string telling the Roll20 User ID's of the authors (e.g.1or45672,145678). Just used so we know who to credit internally, won't be shown publicly on the site.preview: The name of an image file which should be included in your sheet folder showing a preview/screenshot of the sheet (will be displayed in-app at 500x500 resolution) (e.g.kitchensink.png)instructions: Markdown-formatted instructions for using the sheet. If there are any particular setup steps, special rolls you want to make the player aware of, etc., this is the place to put that info. Try to be succinct.
After we have reviewed your sheet if we approve it we will add it to the approved.yaml file in the root directory which will cause it to be available to everyone on the main Roll20 site. If we reject your sheet, we will comment on your Github commit and let you know what changes need to be made before it can be accepted.
PLEASE VERIFY YOUR SHEET.JSON IS VALID JSON at http://jsonlint.com before you submit it!
Guidelines
Here are a few guidelines that you should follow when contributing sheets for the community:
Make it Familiar
The sheet for each game type should be familiar to players who are used to seeing the paper version of that sheet. It shouldn't be identical or violate any copyright, but it also shouldn't be laid out in such a crazy way that players will have a hard time understanding how to use it. Design for ease of us first and foremost. Along those lines, keep your UI changes simple -- please don't change the basic functionality of how a checkbox works, for example.
Add Rolls
The best sheets not only keep track of character stats, they have most of the rolls for the game system embedded in them. This makes it much easier for new players to play the game (just "click on that button on the sheet" versus "Make a macro, okay put slash roll one dee twenty..."). While you don't have to include every roll in the whole system, including the most common ones where appropriate can really help elevate your sheet to the next level.
Don't Duplicate Work
We only need one sheet for each system. For some major systems like Pathfinder or D&D, we may allow more than one sheet if they are different enough, but contact us in advance before you spend a lot of time working on a new sheet for a game we already have a sheet for. We should focus on improving existing sheets, not creating totally new ones. Along those lines, this is a community effort, so if you want to help improve an existing sheet, just jump in and do so.
Use Standard Attribute Names
Whenever possible, use standard names for attributes, spelled out. For example, "Intelligence", "Strength", and "Wisdom". This is important so that if a Character is imported into a game with a different sheet, most of the values will be able to transition. If the attribute names are all different, then nothing can be imported. Your best bet is to look at existing sheets and whenever possible use the same attribute names that are already in use.
No Character Creation or Advancement
Due to copyright restrctions, please don't attempt to include functionality for advancing a character automatically to the next level or creating a new character from scratch automatically. It's fine to have attributes that auto-calculate based on other attributes (including the current level). We'll let you know if your submitted sheet violates this rule.
License
All of the code (HTML/CSS) of the sheets in this repository is released under the MIT license (see LICENSE file for details). If you contribute a new sheet or help improve an existing sheet, you agree that your contribution is released under the MIT License as well.