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 .
×

RuneQuest 6 character sheet bug

Hi there, when I enter the personal information for the character in the upper left (like name, age, weight, homeland, etc.) it vanishes after closing the sheet (via "x"-ing for example). Other information is still there (like combat styles, armour information etc.). Does anyone experience similar troubles? Thanks for any help!
I am not familiar with this sheet, but it is important to enter the information then tab/click off the field, frequently my players would update a field, then close it before doing this, so often not all of the information gets saved.
Hi Kevin, thanks for the reminder. I did that (clicking off the field) but none of the information entered into the above mentioned fields (basically ALL the fields in that section, let's call it "personal information") was saved when I closed the sheet and re-opened it.
It's definitely a bug in the sheet. Looking at it, it seems all of the fields in the Character Info Section do not have "attr_" associated with them, therefore the attributes are not created to store the information. Unfortunately, I am not terribly familiar with how github works to make a pull request to fix this... let me see if I can figure it out.
Thanks a lot, Kevin. Any help is appreciated!
There were several attributes that were not classified as type="text" and many attributes did not have the "attr_" prefix. When I made the changes to these items and used the custom sheet it seemed to be saving things properly. I forked the file via github, made the changes, then sent the pull request. I "think" I did it right... but honestly I am not 100% certain. Hopefully when the development team merges the pull requests this will fix the problem... I hope...
Actually it looks like the original sheet designer made a pull request 2 days ago to redesign the sheet, he also noted the issue I intended to fix, so likely when those changes are merged in, mine are irrelevant.
1421961315

Edited 1421961381
Cool stuff, thanks a lot! As soon as I have more experience with how things work I hopefully will be able to address such problems on my own. Again, thanks for your time, effort and help, Kevin! :)
1422007718
Finderski
Pro
Sheet Author
Compendium Curator
I'm not the sheet creator, but the change was simple enough that I went ahead and made the necessary changes to those fields. They should be updated with the next synch. For those interested, it's Pull Request #579 on github.
Hi all. I wrote the original sheet. Sorry for the bugs it was my first attempt at a sheet. As stated above, I put in a pull request a little while ago which represents a major resign of the sheet and I just saw the merge notice. <a href="https://github.com/Roll20/roll20-character-sheets/" rel="nofollow">https://github.com/Roll20/roll20-character-sheets/</a>... I have learned a lot since the original version was made. Hopefully the redesign will introduce quite a few improvements that people find useful. I have a post in the Runequest 6 forums with more details on the changes made. Probably would have made a lot more sense to post that here as well: <a href="http://designmechanism.freeforums.org/fedback-for-roll20-sheet-redesign-t919.html" rel="nofollow">http://designmechanism.freeforums.org/fedback-for-roll20-sheet-redesign-t919.html</a>
Thanks for your diligent work, Matt! Very much appreciated! You don't know by any chance whether there is a BRP sheet in the making? In any case, I am highly anticipating your improved sheet. Over at the designmechanism forum I have taken the liberty to commend on some typos I have found. Again, thanks!
1422546596
Michael B.
Pro
Sheet Author
I have been considering putting together a BRP (gold book) inspired sheet. I have experimented with sheets for Mongoose Legend on Cakebread & Walton "Renaissance". I am pretty good with the tech part, I tend to loose patience with the fussy XML stylistic and formatting portions (which is why I have not submitted any of my previous efforts).
Out of curiosity, how does one tell when a pull request has been completed? It looks like it has, to my untrained eyes, but my sheet in my campaign is still the old layout. Does a GM need to do something specific to update sheet versions?
A BRP sheet would also be awesome. And I'd really like to see one for RIVER OF HEAVEN.
The Passions/Cults section of the sheet seems to be bugged. When you close the sheet the names of the passions disappear, although the percentages remain.
1426514270
Lithl
Pro
Sheet Author
API Scripter
Maina C. said: Out of curiosity, how does one tell when a pull request has been completed? It looks like it has, to my untrained eyes, but my sheet in my campaign is still the old layout. Does a GM need to do something specific to update sheet versions? If you are following the pull request (the person who submits it automatically follows it by default, while anyone else with a GitHub account can go to the pull request page and click the Follow button), you get an email when it's merged. Looking at <a href="https://github.com/Roll20/roll20-character-sheets/pulls?q=is%3Apr+runequest+" rel="nofollow">https://github.com/Roll20/roll20-character-sheets/pulls?q=is%3Apr+runequest+</a> it appears there have been 3 total pull requests mentioning "Runequest". 2 have been completed and one is open; the open one adds roll templates to the sheet. So long as the campaign isn't customizing the sheet, the GM does not need to do anything to keep it up-to-date. (Non-Mentor GMs don't even have the option to customize the sheet.)
Hi everyone, sorry I need to check these forums more often. The fix for the passions names disappearing has been merged. In addition I just put in a patch to re-add the static field preceding the repeating ones, like the legacy sheet had. I have found that though have repeating fields is great ensuring I never run out of room there are certain things you just can't do with them like static fields. I think this is a good mix of both worlds.