*Template for Roll20 sheets for Blades hacks*
So I heard people are hacking Blades in the Dark, so I did a thing which may be of interest to someone here. This:
https://github.com/joesinghaus/Blades-template
is a combination of rough guide and stripped-down version of the Blades sheet suitable for modification for Blades hacks. There are some instructions on how to make common changes — obviously, the further the hack is from base Blades, the more work you have to do. I tried to make it as readable as possible in a reasonable timeframe, but it’s still a bit technical by nature.
The code is primarily in pug/SCSS (fancy and less work), but I’ve added a compiled HTML/CSS (“easy”, more work) version. You can’t get around coding for modifying it, obviously, but perhaps it’s not too complicated.
EDIT March 3: I have made some changes to the way the sheet is built in order to facilitate modification. However, this breaks compatibility with the first version I posted. It’s still available here: https://github.com/joesinghaus/Blades-template/tree/old-style-build.
WOW Jakob thank you so much! This is huge. You’re amazing.
That’s incredible and very helpful, thank you!
📌
Jakob Oesinghaus, it’s people like you that make this community greater.
Wonderful! 😍
cool, Cool, COOL!!! Now I have to buy this roll20 subscription to create those awesome sheets.
Jakob, this is truly incredible work. Roll20 should owe you back pay.
Haha I wish I’d had this about 2 weeks ago! I somehow stumbled my way into making working player sheets for my hack’s new Actions from a fork of your old work, but the readme should help me find locations for the items and faction sheets which is next on my target list. I guess you’re no longer using image files of the Action names for the roll templates? Are there any other substantive changes from the way the older roll20 sheets worked to this new more hackable version?
Charles Simon Sorry I didn’t have this 2 weeks ago then ;).
So yes, one of the changes is that the roll template titles are now all text, not images. I’ve also removed a couple of smaller things that are unlikely to be useful to anyone, but the compiled sheets work essentially the same with no large changes.
The larger change (apart from adding documentation) is porting the source code to pug instead of HTML, which I’d been working on for a while now.
Since generating the source code this way allows for iterating over objects and loops and variables and such, it makes it a lot easier to hack things without someone having to change the code in a hundred different places. (For example, changing actions is considerably simpler now).
Ok Jakob Oesinghaus, I’m trying to compile the code. Getting a reply of:
Error: Couldn’t find preset “minify” relative to directory “Source”
I am absolutely certain this is some failure on the part of Babel, but I can’t really follow what that means or the specifics of the workaround you offered (Changing line 173 of source\blades.pug doesn’t, to my untrained eye, actually look like the right hook).
Do you think you could clarify this final step of the process?
Charles Simon
Okay, sorry, it seems I messed up the line numbers somewhere along the way while changing things. The actual line to change is line 208!
Either way, if you want to get babel to run properly, perhaps it’s enough to install the minify preset via “npm install -g babel-preset-minify” instead?
I pushed an update to this that uses a build script to make it possible to change things in fewer places. However, it’s pretty incompatible with the previously released version. Old version is still there in a branch, see OP. I recommend using the newer one, however. (I haven’t actually tested if the new version works on windows … hopefully it does).
I transitioned to the new sheet, gave up on Babel and changed line 208 as you said, which did result in it successfully compiling a build! Unfortunately the output doesn’t work for roll20, unsure why. Maybe a CSS issue.
Everyone seems to be having problems with Babel!
I’ve made an update that adds two settings that allow one to:
a) disable babel to get rid of error messages; or
b) produce human-readable HTML/CSS at some point after you have made some changes in pug, because you don’t want to deal with my esoteric code anymore.
Both things should be easy to accomplish now by just changing flags in the build.js file.
*If you want to overlay this on existing changes without using some kind of tracking tool to merge it: the only significant changes are to blades.pug (at the end of the file) and build.js (and the README).
There was a nasty bug in the roll template part that I didn’t catch (and which is now also afflicting the roll20 live sheet), which would make the chat nonfunctional if the broadcast template was used. I’ve fixed it now in this code (just a small change to the rolltemplate.pug, missing bracket!). Sorry for inconveniences.