Lucian said:
Script 6.x includes a new command !shaped-expand-spells . If you run this with a token selected that represents a character, it will search for "empty" spells, such as those that result from dragging in from the compendium, and fill them out from any JSON database of spells that you may have installed. If you're using compendium drag to make your creatures, you almost certainly want a macro that does this + !shaped-apply-defaults
Gozer the Gozerian said:
This has possibly been answered before, but is it necessary to copy and paste all three files (html, css, and translation) every time there is a new update, or just the html?
Thanks for checking and submitting the ticket!Jim W. said:
I see the same behaviour on my test campaign - just added armour to an empty char!
ac_armored_calc is 16
ac is 10
yet no AC listed
Edit: Testing in Shaped Testing will log issue after that test
Edit 2: logged as https://bitbucket.org/mlenser/5eshaped/issues/293/adding-armor-does-not-update-ac-properly
DM_Steel said:
I might be overlooking something simple, but I'm using Shaped Sheet 9.2.1 and Companion Script 6.1.1 and I keep getting an error on my spells (The Character's name is Rufio):
No attribute was found for @{Rufio|cast_as_level_1ST_LEVEL}
This happened after I updated to the latest versions of both the sheet and the script. I tried deleting the spells and re-importing them via the Companion script and the error is still there. The spell works fine, but that error pops up each casting.
This also shows up in the spell stat block in chat:
Hunter's Mark
1st-level (as Rufio|cast_as_level_1ST_LEVEL) divination
This happens with all spells I've tried.
HLazar said:
Thanks for checking and submitting the ticket!Jim W. said:
I see the same behaviour on my test campaign - just added armour to an empty char!
ac_armored_calc is 16
ac is 10
yet no AC listed
Edit: Testing in Shaped Testing will log issue after that test
Edit 2: logged as https://bitbucket.org/mlenser/5eshaped/issues/293/adding-armor-does-not-update-ac-properly
H
Marcloure said:
Is there a way to clear all fields of a sheet without deleting it?
Kryx said:
If you have previously taken 9.2.2 please take it again to get the forced recalculation of all spells which fixes existing spells for #298: higher_level_query_1ST_LEVEL attribute not being created
It was meant to be part of 9.2.2, but was overlooked.
It is up to you to determine if you think it's stable enough.Kryx said:
Stable, but with minor bugs.
There is likely never a point where this sheet will be feature complete. There is always something to do.Robert D. said:
How close do you think you are to feature-complete?
Looks like we might have taken a step backward on some of the more complicated monsters on the newer sheets (Dragons and Vampire didn't seem to import well from the new monster manual). Do you have people reporting bugs on that or do I need to track that down and give you a report in the reporting tool?Since you're Pro make sure to use the latest version. You can also test on my test campaign.
Robert D. said:
Hey. So with all these updates to the sheet. None of my saving throws work. Every monster or PC who was created before the recent updates, when they save, adds the stat in twice. To fix it, I have to go in and toggle and untoggle every save. Anyone seen this and have a better fix. I have HUNDREDS of broken monsters. Also, I have duplicates, for organizational reasons, and that fix doesn't work if there are two monsters with the same name. Anyway, I'm hoping there's an easier fix than manually spending dozens and dozens of hours correcting them all. I already have to do that with every attack and spell. :(
!modattr --all --strength|2- wait until it finishes, then
!modattr --all --strength|-2Do this for every ability score. That should do the trick.
Your GM can roll back the data using roll20's new feature as I mention above. If you're experiencing major issues then 9.2.2 is a better option. The majority of regular users of the sheet are not experiencing major issues. I'm not trying to diminish the issues you're experiencing as several others experienced them as well, but I'm clarifying the state of the 9.0.1.Greg said:
So we're pretty much helpless, but I don't think we're in a niche scenario.
As far as steps to reproduce it, the only thing that happened is that the sheet was automatically upgraded and a number of things were suddenly broken. We signed on, started playing, and we quickly encountered these problems. Weapon attacks are empty on at least one sheet and possibly all of them (we haven't had combat yet, so I can't be sure). Spells are empty for at least one player and maybe more. Strange characters are being sent with the sheet output. I wouldn't even know what else to report at this stage.If your goal is solutions then I'd firstly recommend to roll back your data, use 9.2.2, and then report any issues to my issue tracker.
TypeError: Cannot read property 'split' of undefined
TypeError: Cannot read property 'split' of undefined
at Object.versionCompare (apiscript.js:6967:21)
at apiscript.js:5039:16
at /home/node/d20-api-server/api.js:2134:5
at Function._.each._.forEach (/home/node/d20-api-server/node_modules/underscore/underscore.js:153:9)
at handleSheetWorkerComplete (/home/node/d20-api-server/api.js:2133:5)
at later [as _onTimeout] (/home/node/d20-api-server/node_modules/underscore/underscore.js:828:25)
at Timer.listOnTimeout (timers.js:92:15)
Testing on the stable version has little value for me beyond making it more stable. Generally unless the issue is major I don't resolve it on that version, but resolve it on the latest version to prevent new bugs.TheWebCoder said:
My latest plan is once 9.x stabilizes (to the point of 7.12), I'll switch to a custom version of the sheet, so it doesn't manually update. Then I can help test new stuff on the test server until v10x is at the same point. Wash, rinse, repeat.
One question though: is it possible to switch back from custom to Roll20 version of a sheet, or is it forever manually after you go that route?You can switch to any version that is equal to or greater than your current version. It doesn't matter if it's hosted by Roll20 or if you've installed it yourself.
See the instructions in the OP. You've missed the translation file.bgb said:
I just updated to Sheet 9.2.3 and there's lots of red - haven't seen this happen for while. Is this expected? Is there anything I can do to fix the colors?
<hangs head in shame> I hate it when I forget to read all the instructions. Thanks.Kryx said:
See the instructions in the OP. You've missed the translation file.
I think you misunderstood me? I'll still help test whatever version you're testing on your test server, while only updating my personal campaign when each major version stabilizes. This is also a recommendation to fellow DMs with Pro account and players who don't like unexpected changes.Kryx said:
Testing on the stable version has little value for me beyond making it more stable. Generally unless the issue is major I don't resolve it on that version, but resolve it on the latest version to prevent new bugs.TheWebCoder said:
My latest plan is once 9.x stabilizes (to the point of 7.12), I'll switch to a custom version of the sheet, so it doesn't manually update. Then I can help test new stuff on the test server until v10x is at the same point. Wash, rinse, repeat.