Roll20 uses cookies to improve your experience on our site. Cookies enable you to enjoy certain features, social sharing functionality, and tailor message and display ads to your interests on our site and others. They also help us understand how our site is being used. By continuing to use our site, you consent to our use of cookies. Update your cookie preferences .
×
Create a free account

I would like to revise the L5R Sheet (4th Ed).

Would small incremental PRs be preferred, or a larger fuller substantial revision: I'm working on: Firearms and Spell Weapons <-- simply enabling someone to use the weapons section to roll for attacking and damage, instead of manually. Add Teppudo as a skill to the Bugei Weapons Add Teppudo as a skill option to the weapons section Add Shugenja School Rank as a skill option to the weapons section Adding repeating sections for: Kata, Kiho, and Skill Masteries (for now very simple sections, as there is no place for them on the sheet right now) Migrating Advantages, Disadvantages, and School Techniques to repeating sections, scrolling through a text area is a PITA... and its not much effort to do this. Bigger Changes: Update the roll buttons to use roll actions which can more cleanly implement the rule of 10.  Update the Clans dropdown to use a display list so... people can enter in minor clans or custom clans. Have Skills be the default initial tab Have Traits and Rings be only in the Skills tab, they take up a huge amount of space... and are not relevant outside of that tab. Have Initiative, Void Points, Armor TN, and Wound Penalties / Current Wounds be available in all tabs. Make weapons a repeating list instead of just... six and six bows... some of us run out of weapons :/ Migrate to pug, and typescript because... its easier to maintain (imho) and roll20 seems to have lots of guides on pug. I have a pro account and have been testing things myself atm. I can split these off into smaller PRs or just do one big one. 
I would LOVE a  larger, substantial revision. It's been years since I last used the current version of the sheet, but I remember thinking back then that it was quite clunky and limited. Unfortunately it felt a bit like a hindrance to enjoying the game, one that you just had to put up with, not enhancing but lessening the experience - at least for me. Even a smaller revision and some modernization would be very welcome, but if at all possible, revising it thoroughly would be grand!
I've made a Draft PR for some changes: <a href="https://github.com/Roll20/roll20-character-sheets/pull/14454" rel="nofollow">https://github.com/Roll20/roll20-character-sheets/pull/14454</a> &nbsp;as I've never made a PR for roll20 before, I did try to use the same email as my account for the commits, but making the actual PR is using my github account instead.&nbsp;
I have a year-long campaign running in L5R and we noticed the Teppudo change. We thought we were suffering from the Mandela Effect! Would you be open to other change suggestions? I know my players have opinions on the sheet.&nbsp;
1761771679

Edited 1761771717
Yes, but the sheet is in a pretty bad state html/css wise, so I make no promises on what I will change next. I'm also weighing how much to add to this sheet vs. build a beacon version of the sheet.
Cool. I will get back to you as soon as I can. If you build another sheet, that would be cool too. Less clunky would be nice, and I appreciate your giving it a run.&nbsp;
1763787891
Mago
Pro
Sheet Author
as a sheet dev myself, i recommend small incremental PRs if you are unsure of new features or if you are gonna add a large amount of new Attrs to the sheet. this is a measure to protect user info. Now if you are experienced and have a solid plan or vision of what you want to do, do extensive play testing and launch a big revision when ready.&nbsp; As for Github, just make sure you follow the rules for submitting PRs to the repo, it doesnt really matter which account you use, just make sure your fork is updated before you start.
1763843921
GiGs
Pro
Sheet Author
API Scripter
kimurae said: Migrate to pug, and typescript because... its easier to maintain (imho) and roll20 seems to have lots of guides on pug. I'm probably the lone stand out who thinks migrating to pug is a bad idea. Anything that makes the sheet harder to edit for people who come after you is a bad idea IMO. That's why I prefer templating systems that need make no changes to the published sheet (i.e. handlebars). Ditto Typescript. But for the rest - make whatever changes are easiest or you. If you mess the sheet up badly, people who use it can complain and it can be rolled back.
I made a PR that adds: Kata Kiho Skill Masteries Multiple School Techniques Multiple Advantages Multiple Disadvantages When it does get merged, at first you'll see the original text areas for the Techniques, Advantages, etc. I used CSS to only&nbsp; hide the legacy boxes when empty , I wanted to make sure: Nothing gets lost Ensure, having it changed to repeatable items is an&nbsp; improvement .&nbsp;