Skip to content

Feature Request: Multiple Body Token types #9

@devinnasar

Description

@devinnasar
  • As a: GM
  • I want: Caterpillar-enabled enemies to have multiple 'body' segment images
  • So that: Caterpillar-enabled enemies can taper toward their ends

What I'm proposing is a refactoring of the Caterpillar interface to allow for creating more graceful transitions from the head token to the rear token. Please see the following mockup:

Length 50
Segment Token Image Segment Length % Segment HP % Is End? Controllable?
1 /path/to/lg_body_seg_image 50 50
2 /path/to/md_body_seg_image 35 35
3 /path/to/sm_body_seg_image 10 10
4 /path/to/tail-or-head_image 5 5 [+]

The plus sign adds another row to the table.

   ___
 /     \
 |      |    <-- Prototype Token (Head)
  \    /
 |      |    <-- Segment 1
 |      | 
 |      | 
 |      | 
  |    |     <-- Segment 2
  |    |
  |    |
   |  |      <-- Segment 3
   |  |
    \/       <-- Segment 4

  • Segment Token Image: Path. Tokens generated for this 'Segment' of the Caterpillar will use this image. This allows for a visual taper.
  • Segment Length %: Integer. Of the 50 token length specified above, this percent of the Caterpillar will use the image for the Segment. For example, the first segment would generate 25 Tokens.
  • Segment HP %: Integer. This percentage of the Prototype Token's HP will be divided among tokens generated for this Segment. For example, if the Prototype token has 100 HP, Tokens in the first segment would have 2 HP each (50 HP / 25 Tokens)
  • Is End?: Boolean. Designates the Segment as the end of the Caterpillar. A single Token is generated for this segment, ignoring Segment Length %.
  • Controllable?: Boolean. Only available if Is End? is checked. Allows the end token to be controlled independently of the Prototype token, in the case of two-headed creatures for example.

I think that this would allow for more dynamic Caterpillars that have more granular damage spreads as well.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions