Big trouble with little ninjas...

[Thrull]

> >>> snow ninja, though, which applies to a lot of other icons that have
> >>> been done in the past - when you make a wide icon to have more
> >>> room to work with, that means that whatever monster/NPC that
> >>> wide icon is used to represent is going to take Large damage from
> >>> weapons, which can be a pretty hefty penalty sometimes (for
> >>> example, 3d6 vs 1d10 in the case of a two handed sword). I
> >>> realize you probably couldn't do a naginata wielding ninja in the
> >>> space of a normal icon, but I wanted to bring it up anyway in case
> >>> it was being overlooked.

> There must be simpler ways to maintain gameplay in her case. If she
> had a cold fire shield active, her vulnerability would not seem such a
> liability, perhaps. ----> Let the further suggestions begin!!!

Touche'

Does it strike anyone else as silly that you can specify "large even if icon 1 x 1",
but not the inverse (ie "small no matter what size icon")

Do we know what byte(s) control this? Will any of the editors (character, etc.)
allow you to specify the size (large, medium, or small) of a monster or npc?

Thrull :<>

[Kaviyd]

In a message dated 98-01-06 02:32:39 EST, thr...@atlantic.net writes:

> Does it strike anyone else as silly that you can specify "large even if icon
1
> x 1", but not the inverse (ie "small no matter what size icon")
>
> Do we know what byte(s) control this? Will any of the editors (character,
> etc.) allow you to specify the size (large, medium, or small) of a monster
or npc?

We know exactly which byte is involved -- it is byte 130 in the character or
monster record. What we don't know is where in CKIT.EXE that byte is
interpreted to determine whether to apply "S-M" or "L" damage. If somebody
were to find that byte, we could hack CKIT.EXE so that it would apply "L"
damage only if "large even if icon 1x1" button is selected regardless of
actual icon size.