11 replies to this topic

[AnnabelleRose]

I think I asked this once before, but I cannot remember where. Might have been though PM or IM. Either way, I cannot find it.

When I go to Shadow Keeper, I get one set of hex colors. The template I stole borrowed from SConrad shows two sets. How do I find the second, or is the second the one shown in SK?

If possible, would I be able to do this with only the first set from SK as well?

[SConrad]

My template shows you... two sets? Uh, how can that be?

[igi]

IIRC, the code had 1 offset and 1 colour (both were specified in hex).

IIRC, the code had 1 offset and 1 colour (both were specified in hex).

[SConrad]

Ah, that'd explain it.

[AnnabelleRose]

Ah, that'd explain it.

Not to me it doesn't.

Still need some help.

[SConrad]

Show me an example code of what it is you don't understand, and I'll help you.

[AnnabelleRose]

I'll use the PGK script as an example:

COPY_EXISTING ~J#Klsy09.CRE~ ~override~
  PATCH_IF (SOURCE_SIZE > 0x71) THEN BEGIN
	WRITE_BYTE 0x32 0x42 // Metal colour
	WRITE_BYTE 0x2d 0x2e // Minor colour
	WRITE_BYTE 0x2e 0x15 // Major colour
	WRITE_BYTE 0x2f 0x69 // Skin colour
	WRITE_BYTE 0x32 0x42 // Leather colour
	WRITE_BYTE 0x32 0x42 // Armor colour
	WRITE_BYTE 0x32 0x42 // Hair colour

I figured out how to get the first one (though ShadowKeeper), but I have no clue how to get the seecond part. Can't remember if I guessed or copied on that one.

[SConrad]

Ah, yeah, just as I (and igi) thought.

The first offset is not a colour, but a location in the creature file. If you open up a creature in NI and have enabled Options -> Show Hex Offsets, you will see that all different information are located in different places of the file. So, first, you need to specify *what* in the file you want to change, before you can enter the new value. Just putting up values doesn't really make any sense - WeiDU can't guess what you want to patch. It can easily be the saving throws or the deathvariable instead of colours.

Also, the second value isn't just the colour - it's the hex value of the colour, which is not quite the same thing.

I'll explain it with my own code from BGothII:

COPY_EXISTING ~aerie.cre~ ~override~
  PATCH_IF (SOURCE_SIZE > 0x71) THEN BEGIN
	WRITE_BYTE 0x2c 0x1b // Metal colour
	WRITE_BYTE 0x2d 0x2e // Minor colour
	WRITE_BYTE 0x2e 0x15 // Major colour
	WRITE_BYTE 0x2f 0x69 // Skin colour
	WRITE_BYTE 0x30 0x16 // Leather colour
	WRITE_BYTE 0x31 0x1d // Armor colour
	WRITE_BYTE 0x32 0x42 // Hair colour
  END
BUT_ONLY_IF_IT_CHANGES

is the full code, but I'll just grab one of them as example:

WRITE_BYTE 0x2c 0x1b // Metal colour

The first value is the location, 2c, in the file. We can see that the next 'entry' in NI is at 2d, which means that the field we want to edit is only one byte (hence WRITE_BYTE instead of SHORT or LONG).

The second value is the color in hex. 1b is the same as colour number 27. To check what the hex value of the desired colour is, simply right-click in NI and select "Edit as hex".

[AnnabelleRose]

So just to check myself (so I can get some more of my projects released, finally), The second value will always be the same?

[SConrad]

No, the second value is the colour code you want the colour 'slot' to have, in a hexadecimal format.

The first values are always the same; 0x2c for metal colour, 0x2d for minor colour, 0x2e for major colour and so on.

[AnnabelleRose]

Glad I asked. That could have been a disaster....

[SConrad]

Possibly, yes.