Damage Grid?

[barrelv]

Looking for some inspiration on how to visually tackle an element of Iron Kingdom's RPG.

Player characters gets a 'damage spiral' that's made up of 3 groups of rows. Each group is 2 rows. And the number of boxes in each row is (Stat - 2) / 2 due to this odd way there are two boxes that are 'between' the two rows in the group. See the attached images for some visual idea of the madness I'm talking about.

The 'in between' boxes to the right are always there, and then it builds right-to-left. Most paper character sheets, you just black out boxes left-to-right as you don't need them.

Does anyone have any idea how I can script this? My ideas so far haven't turned out very well.

[Mathias]

I think I'd use two different portals per damage track - one to output the double-row, and the other to output the small bit at the right end. Then, have the right end portal be centervert aligned on the bigger portal, and use trial-and-error to find the right amount of left-right spacing to make it look as if it's all one thing.

[barrelv]

makes sense. Ideas about how to get the actual boxes in place? I've had bad luck trying to auto-swap images in the past based on formulas.

Strike that, I broke open the Savage Worlds character sheet source and it gave me some ideas....

[Mathias]

In this thread: http://forums.wolflair.com/showthread.php?t=51038 (post 4)

I pasted the code that generates the tracker boxes in Cortex - what you're doing will be similar.

[barrelv]

            @text &= "{bmpscale 3 output_box}"

that line alone is going to be so helpful. Thank you!

[barrelv]

Somewhat related - can you not have two portals using the same Component on a sheet?

[Mathias]

If the component="" in a table matches the component="" in another table, any items output in the first table will be marked as "already output" and won't be added to the second one. That's why it works to have spillover sheets that output everything that didn't fit on the previous page - the ones that fit on an earlier page get flagged as "already output" and therefore aren't printed twice.

[barrelv]

well . I'll have to create a new component called 'health' with 3 things instead of trying to store the stuff I need on the 3 attributes. Not the end of the world I suppose.

[Mathias]

Create a health component, move all the health-related fields to that, and then add that component to the attributes compset. Then, not only do you get to output separate lists on the printout, you can separate the health-related mechanics from the attribute mechanics, and make everything easier to debug because it's better organized.