Homebrew World Character Keeper Ready for Use!

After some help getting started from @Michael_G_Barford, I’ve finished a (fancy schmancy) character keeper for Homebrew World, my drift of Dungeon World (a sort of DW2.0 streamlined for one-shots and mini-series style play).

It’s actually all of HBW converted into Google Sheets format, including the GM stuff, basic moves, etc.

I’d be all sorts of interested in feedback, either from folks just poking around at the sheets or using them for actual online play.

Specific questions:

  • Are the character sheets on the PCs tab actually useful in play?
  • Do you find yourself wanting to (or just accidentally) needing to edit content? Copy/paste stuff? Otherwise break the spreadsheet? :slight_smile: If so, what and why?




This looks great! I flipped and read through it, but didn’t actually use it in play, so take that into consideration.

Stream of consciousness thoughts:

Most of it works really, really well. I was thrown by the Shield having two checkboxes for a moment (you can’t check the second one), but that makes sense. Having clickable checkboxes is far easier than writing and erasing, too (for example, for Experience)!

Being able to choose between Backgrounds and having those populate the fields below works really well. This kind of touch makes using this really quick and really space-efficient, which is fantastic.

Under “GM Stuff”, the “Damage” box is too small, and doesn’t line up quite right with the one beside it.

The spreadsheet is nicely set up so that it’s not tempting to do anything game-breaking, but some more space for notes could be useful, perhaps (not just at the bottom, but in other spaces, too). I’d have to try it in actual play to see! Having the character sheets that vertical could be awkward (as opposed to having them as rows or as separate tabs), or it might be just great; I’m not sure.

(I’m sure people will find ways to ruin the spreadsheet, but they should be able not to!)

I have no idea what +advantage or -disadvantage does for monsters. They don’t roll, do they?

Some of the font size (especially the reference material) is really small, but I suppose someone with poor eyesight might have some Zoom settings engaged on their browser or Google Sheets settings already.

Excellent work! I would definitely use this. Lots of nice little touches, like how the Debilities, when selected, highlight the relevant stats.


Thanks for taking the time to review it, Paul!

Weird. It looks off for when I first load it, but then quickly corrects. I added a little more buffer space. Maybe that will help.

Oh! Also, I was missing an entry on the left hand box. Fixed.

Good point. It’s tough, cuz I don’t want to add more vertical scrolling the whole thing.

Two reasons for the vertical orientation:

  1. Having 10 tabs to sift through seems overwhelming and bad
  2. From my experience playing with folks on the Gauntlet, people really like having the ability to see everyone’s character sheets all in one place. And I generally agree. Being able to see your sheet while you’re playing gives me time to think about ways I can riff on your Drive or our relationships or your moves.

I’ve thought about trying to make something that gives you, like, 1 tab for each player, with a “HUD” section displaying abbreviated contents of everyone else’s playbook. But I’m not sure that’s even possible, much less feasible.

Small font size is definitely a sacrifice to the constraints of space. I expect folks might have to zoom in a bit.

Someone rolls damage for monsters in DW/HBW. Standard rule is that the player rolls the damage that they take, but plenty of folks drift that to the GM rolling damage. Either way: 'vantage here works the same as elsewhere… roll an extra die, discard the lowest or highest.

1 Like

Good answers, Jeremy! I agree with all of that. And thanks for the clarification on the damage roll for monsters! Makes total sense.

I think you’ve created an amazing tool - very impressive! Like your playbook sheets, this makes playing your game far more accessible, and means more people will ‘get it to the table’. Three thumbs up!

Will definitely share this with my players, as not all of them really liked printing PDFs and marking them up, old-school style. (I personally dig that, but to each their own…)

By the way: the Damage box looks great now!

Excited to see this, @Jeremy_Strandberg!

Here’s a novice-to-apprentice-user-level bug (or PEBKAC), presented in the classic reporting pattern:

Steps to repeat

  • Follow link to the Google Sheet.
  • Use “File > Make a copy” of the Google Sheet.
  • Select the “PCs” tab.
  • Click the respective [-] icon above any of the texts reading “If unused, click the [-] icon above the column headers to collapse.”

Expected experience

  • The column of content below the indicator “collapses” or disappears in some way.

Actual experience

  • A modal box appears with the mesage " Heads up! You’re trying to edit part of this sheet that shouldn’t be changed accidentally. Edit anyway?"
  • Clicking OK produces creates a new spreadsheet column to appear to the left of the column with the [-] icon. (i.e. as if the command “Insert > Column left” had been selected.


Unfortunately, the “Heads up! You’re trying to edit part of this sheet…” warning is unavailable. It appears to happen there are any protected-with-warning cells in the group being collapsed. (Well, not any… it’s kind of inconsistent. But I couldn’t make it go away and keep the warning messages for accidental edits.)

The “inserted row” behavior was a bit of an illusion, i think. I had an extra empty column between each playbook, so when you collapsed the playbook, it ended up with two empty columns instead of one. I just cleared out the extra column. You still end up with a stray column for each playbook, but it’s not as bad.

For what it’s worth, I get the “Heads up!” warning every time I choose from a field, as well (which is a pain in the butt). Does that not happen for other people?

That definitely should not happen. Is it all of them, or just a specific few? If a specific few… can you give me some cell references (e.g. “B23”)?

Hmmm! It felt like it was every single one. But let me try it again, and I’ll pay closer attention this time. I’ll report back!

Ok, reporting back:

That “Heads up!” message pops up anytime I edit the sheet, pretty much. Writing in my name didn’t trigger one, but choosing from any pick lists, hitting “Enter” after entering text (in the Equipment section), filling out my stats, and checking any box on the sheet (equipment, moves, XP, debilities, etc) all triggered that message.

It’s not a huge deal, because you can hit “ignore for the next 5 mins”, but it’s kind of odd.

No, that is a big deal, because dismissing that warning means you end up unlocking all the cells, even ones that are supposed to be protected.

Can you share a link to your copy of the spreadsheet with me? Ideally with edit access? (either open it up entirely or share it specifically with me… jack underscore blackfoot at the yahoo).

Is anyone else seeing this problem?

Right! And of course. I’ll share with you immediately.

It should be open to anyone.

Here’s what I’m noticing:

It seems to work correctly for most character types/playbooks (I haven’t tried them all!). However, for the Wielder (which was the first one I tried), I get the message with any field I try to select or modify.

EDIT: Check out the Druid’s Drive. I chose one, but it’s unhappy for some reason. This doesn’t seem to happen with other playbooks!

I hope this is more helpful than frustrating!

1 Like

For the record, I am a bit chagrined to report that my original note was indeed a PEBKAC issue. Columns of content are “collapsing” as expected when I click the icon; I was just losing track spatially of which column was which.

I could blame the unexpected modal box for causing pattern interruption, but that would be informed by my dinged pride as much as my interface assessment. :slight_smile: Sorry for the wasted bandwidth!

(Jargon reference for “PEBKAC”)

1 Like

Fixed the issues with the Wielder and the Druid’s drive (the Wielder had the same issue… not sure why, but F2ing in the selection lists made the validation error go away).

Also added conditional formatting to all the Advances.

Thanks for the feedback!

1 Like