[CocoaSpud]

We'll probably have to work this out on a case-by-case basis.

For walls, the FRUA has 16 slots I think? But then you can choose from several wall images to populate your 16 slots. When I import, I get two values that let me determine the image group and group index for each slot's image, then convert that to a filename.

For small pics, it might be the same thing. Looking at the hack docs for FRUA (SlotDef.txt) I see:

PICTURES:
Monsters--
1==Bit Of Moander
2==Bulette
3==Carrion Crawler
4==Dolphin
5==Dracolich
6==Ancient Dragon
...
45=Vampire Lord
46=Vampiress
47=Vidruand

Clerics--
1==Kallithrea
2==Lunit Bdufe
3==Dark Cleric
4==Dwarf Priest
5==Temple Priest

Fighters--
1==Alias
2==Fejyelsae
3==Grunschka
4==Jagaerda
5==Jovena
6==Shal

and so on. Which leads me to believe that I need to examine two values to figure out the image group and image index to determine which file to use.

Icons, Sprites, and BigPics appear to have groupings also.

These image types look straightforward to figure out:

OVERLANDS:
1==Moonsea Realms
2==Southern Ksoh
3==The Dalelands
4==Web Realm
5==Western Cormyr

DUNGEON COMBAT WALLS:
1==Adobe
2==Cave
3==Coral
4==Lava
5==Rock

WILD COMBAT ART:
1==Forest
2==River
3==Swamp
4==Wasteland

So I'm not sure about the small pics. I guess I need to compare the exported pics with what FRUA shows in each slot (using defaults). Then export a test design that uses the default slots, then import it into DC to see what I get. From there I can work out the proper indexing on each filename.

I agree with you on the camp/treasure file naming. If they follow the small pic indexing scheme, then they should be loaded properly during import. That is, if the camp event indexes to the camp pic, then it will be loaded, else whatever else the designer put there will be loaded.

Edit:

Also, the small pic filename indexes will be totally sequential, they won't start indexing at 1 for each image group as indicated by the hack info above. The import code will be able to offset group and index to figure out the correct filename.

Also Part 2, I guess I need to examine the files you exported in order to test how the indexing works in the FRUA design files. Perhaps it would be better if I exported them myself rather than get a big zip in email. I think figuring this out will require debugging the import code in DC, which you're welcome to do if you feel inclined [img]smile.gif[/img] If not, I'll be happy to do it [img]smile.gif[/img]

I think the combat and overland images won't require special import code. If they are exported to DC format and renamed in sequence as indicated above, then the import can reference them without any fiddling with indexes.

[ 04-04-2006, 09:34 AM: Message edited by: CocoaSpud ]