iff-files

Printable View

15-01-11
chreadie

TH iff-files

Hey!

Notice: After almost getting bitchslapped by a friend of mine for using int where it should be int im going to change the definitions, i dont have time right away tho so please use the ints ive posted as ints.

This is what ive found so far (notice that i start counting at 0 and U# are unknown values):

Quote:

Originally Posted by Tsukasa

144 bytes IffCommon structure,
40 bytes model name,
2 byte for each stat modifier (only the high byte is used, 5 * 2 = 10 byte in total)
2 byte point marker

Quote:

int isValid = 0; // 0-3
int ItemID = 0; // 4-7
String ItemName = ""; // 8-47
byte lvlReq = 0; // 48
String Icon = ""; // 49-88
byte U2 = 0; // 89
byte U3 = 0; // 90
byte U4 = 0; // 91
int ItemPrice = 0; // 92-95
int DiscountPrice = 0; // 96-99
int usedPrice = 0; // 100-103
byte shopFlag = 0; // 104
byte moneyFlag = 0; // 105
byte timeFlag = 0; // 106
byte timeByte = 0; // 107
int Point = 0; // 108-111
short fYear = 0; // 112-113
short fMonth = 0; // 114-115
short fDayOfWeek = 0; // 116-117
short fDay = 0; // 118-119
short fHour = 0; // 120-121
short fMinute = 0; // 122-123
short fSecond = 0; // 124-125
short fMSecond = 0; // 126-127
short tYear = 0; // 128-129
short tMonth = 0; // 130-131
short tDayOfWeek = 0; // 132-133
short tDay = 0; // 134-135
short tHour = 0; // 136-137
short tMinute = 0; // 138-139
short tSecond = 0; // 140-141
short tMSecond = 0; // 142-143

This seems to be the basic structure of the .iff-files. 144 bytes telling us: id, name, shopflags etc.

The above is true for all files except:
CadieMagicBox.iff
CadieMagicBoxRandom.iff
CutinInfomation.iff
Description.iff
FurnitureAbility.iff
Match.iff
OfflineShop.iff
TikiPointTable.iff
TikiRecipe.iff
TikiSpecialTable.iff

byte 4-7 is a bitmask with the following values (its just my guess):

Quote:

I would print all 1's and 0's but it will take too much space.
Character ID: (itemID & 0x03fc0000) >> 18
Item Group: (itemID & 0xfc000000) >> 26
Item Type: (itemID & 0x001f0000) >> 16
Item Position: (itemID & 0x0003e000) >> 13
Item Serial: (itemID & 0x000000ff)

byte 104 (called shopFlag above):

Quote:

Tiki Report Paper, total value: 2
bit-value 128: 0
bit-value 64: 0
bit-value 32: 0
bit-value 16: 0
bit-value 8: 0
bit-value 4: 0 // Coupon?
bit-value 2: 1 // Non-giftable?
bit-value 1: 0 // Giftable?

This item has bit-value 2 as 1, "Time Booster" does not. This item is non-giftable but buyable. "Time Booster" is giftable and buyable.

byte 105 (called moneyFlag above):

Quote:

Tiki Report Paper - 19
bit-value 128: 0
bit-value 64: 0 // Banner: Special?
bit-value 32: 0 // Banner: Hot?
bit-value 16: 1 // Banner: New?
bit-value 8: 0
bit-value 4: 0 // Display only?
bit-value 2: 1 // Pang = 1, Cookie = 0?
bit-value 1: 1 // Show up in shop?

The data about start and end dates conform to this struct(SYSTEMTIME structure):

Spoiler:

typedef struct _SYSTEMTIME {
WORD wYear;
WORD wMonth;
WORD wDayOfWeek;
WORD wDay;
WORD wHour;
WORD wMinute;
WORD wSecond;
WORD wMilliseconds
;} SYSTEMTIME, *PSYSTEMTIME;

The following is the "extra" bytes apart from the ones above OR the whole structure if the file is found in the list above.

AuxPart.iff:

Quote:

Spoiler:

short U14 = 0;
short U33 = 0;
short U34 = 0;
short U35 = 0;
short U36 = 0;
short U37 = 0;
short U38 = 0;
short U39 = 0;
short U40 = 0;
short U41 = 0;
short U42 = 0;
short U43 = 0;
short U44 = 0;
short U45 = 0;
short U46 = 0;
short U47 = 0;

Ball.iff

Quote:

Spoiler:

short U14 = 0;
short U33 = 0;
short U34 = 0;
short U35 = 0;
String GFX1 = "";
String GFX2 = "";
String GFX3 = "";
String GFX4 = "";
String GFX5 = "";
String GFX6 = "";
String GFX7 = "";
String GFX8 = "";
String GFX9 = "";
String GFX10 = "";
String GFX11 = "";
String GFX12 = "";
String GFX13 = "";
String GFX14 = "";
short U36 = 0;
short U37 = 0;
short U38 = 0;
short U39 = 0;
short U40 = 0;
short U41 = 0;

Caddie.iff

Quote:

Spoiler:

int Salary = 0;
String Icon2 = "";
short Power = 0;
short Control = 0;
short Accuracy = 0;
short Spin = 0;
short Curve = 0;
short U39 = 0;

CaddieItem.iff

Quote:

Spoiler:

String GFX1 = "";
String GFX2 = "";
short price1Day = 0;
short U33 = 0;
short price7Days = 0;
short price30Days = 0;
short Amount = 0;
short U37 = 0;

CadieMagicBox.iff

Quote:

Spoiler:

int Index = 0;
int Valid = 0;
int showOnPage = 0;
int U4 = 0;
int levelReq = 0;
int prodItem = 0;
int numProdItem = 0;
int itemOne = 0;
int itemTwo = 0;
int itemThree = 0;
int itemFour = 0;
int numItemOne = 0;
int numItemTwo = 0;
int numItemThree = 0;
int numItemFour = 0;
int U16 = 0;
int U17 = 0;
int U18 = 0;
int U19 = 0;
int U20 = 0;
int U21 = 0;
int U22 = 0;
int U23 = 0;
int U24 = 0;
int U25 = 0;
int U26 = 0;

CadieMagicBoxRandom.iff

Quote:

Spoiler:

int numItemOne = 0;
int itemOne = 0;
int numItemTwo = 0;
int itemTwo = 0;

Card.iff

Quote:

Spoiler:

byte U1;
string Sprite2Name;
short U14;
short U33;
short U34;
short U35;
short U36;
short U37;
short U38;
short U39;
String UString1;
String UString2;
String UString3;
short U40;
short U41;
short U42;
short U43;

Character.iff

Quote:

Spoiler:

String Sprite2Name = "";
String GFX1 = "";
String GFX2 = "";
String GFX3 = "";
short firstPower = 0;
short firstControl = 0;
short firstAccuracy = 0;
short firstSpin = 0;
short firstCruve = 0;
byte U37 = 0;
byte U38 = 0;
byte U39 = 0;
byte U43 = 0;
byte U44 = 0;
byte U45 = 0;
int U46 = 0;
byte initPower = 0;
byte initControl = 0;
byte initAccuracy = 0;
byte initSpin = 0;
byte initCurve = 0;
int U52 = 0;
byte U53 = 0;
short U55 = 0;
short U56 = 0;
short U57 = 0;
short U58 = 0;
short U59 = 0;
short U60 = 0;
short U61 = 0;
short U62 = 0;
short U63 = 0;
short U64 = 0;
short U65 = 0;
short U66 = 0;
short U67 = 0;
short U68 = 0;
short U69 = 0;
short U70 = 0;
short U71 = 0;
short U72 = 0;
short U73 = 0;
short U74 = 0;

Club.iff

Quote:

Spoiler:

String Sprite2Name = "";
short Amount = 0;
short U33 = 0;
short U34 = 0;
short U35 = 0;
short U36 = 0;
short U37 = 0;

ClubSet.iff

Quote:

Spoiler:

int clubWood = 0;
int clubIron = 0;
int clubWedge = 0;
int clubPutter = 0;
short initPower = 0;
short initControl = 0;
short initAccuracy = 0;
short initSpin = 0;
short initCurve = 0;
short maxPower = 0;
short maxControl = 0;
short maxAccuracy = 0;
short maxSpin = 0;
short maxCurve = 0;

Course.iff

Quote:

Spoiler:

String enName = "";
String thName = "";
int bitFlag = 0;
short Amount = 0;
String xmlFile = "";
short U34 = 0;
short U35 = 0;
int U36 = 0;
String seqFile = "";

CutinInfomation.iff

Quote:

Spoiler:

int U1 = 0;
int U2 = 0;
int U3 = 0;
int U4 = 0;
int U5 = 0;
int U6 = 0;
int U7 = 0;
String picChar = "";
int U8 = 0;
String picBG = "";
int U9 = 0;
String picOverlay = "";
int U10 = 0;
String picUnknown = "";
int U11 = 0;
int U12 = 0;

Description.iff

Quote:

Spoiler:

int itemID = 0;
String ItemName = "";

Furniture.iff

Quote:

Spoiler:

String Sprite2Name = "";
short Amount = 0;
short U33 = 0;
short U34 = 0;
short U35 = 0;
short U36 = 0;
short U37 = 0;
short U38 = 0;
short U39 = 0;
short U40 = 0;
short U41 = 0;
short U42 = 0;
short U43 = 0;
short U44 = 0;
short U45 = 0;
short U46 = 0;
short U47 = 0;
short U48 = 0;
short U49 = 0;
short U50 = 0;
short U51 = 0;
short U52 = 0;
short U53 = 0;
short U54 = 0;
short U55 = 0;
short U56 = 0;
short U57 = 0;
short U58 = 0;
short U59 = 0;

FurnitureAbility.iff

Quote:

Spoiler:

int isValid = 0;
int itemID = 0;
int num1 = 0;
int num2 = 0;
int num3 = 0;
int num4 = 0;
int num5 = 0;
short numYear = 0;
short numMonth = 0;
short numZero = 0;
short numDay = 0;
short numHour = 0;
short numMinute = 0;
short numSecond = 0;
short numMilliSecond = 0;
short num6 = 0;
short num7 = 0;
short num8 = 0;
short num9 = 0;
short num10 = 0;
short num11 = 0;
short num12 = 0;
short num13 = 0;
short num14 = 0;
short num15 = 0;
short num16 = 0;
short num17 = 0;
short num18 = 0;
short num19 = 0;
short num20 = 0;
short num21 = 0;

HairStyle.iff

Quote:

Spoiler:

String Sprite2Name = "";
short Amount = 0;
short colorID = 0;
short numChar = 0;
short U35 = 0;
short U36 = 0;
short U37 = 0;

Item.iff

Quote:

Spoiler:

String Sprite2Name = "";
short Amount = 0;
short U33 = 0;
short U34 = 0;
short U35 = 0;
short U36 = 0;
short U37 = 0;

Mascot.iff

Quote:

Spoiler:

String Sprite2Name = "";
String Sprite3Name = "";
short price1Day = 0;
short U33 = 0;
short U34 = 0;
short U35 = 0;
short U36 = 0;
short U37 = 0;
short U38 = 0;
short U39 = 0;
short U40 = 0;
short U41 = 0;
short U42 = 0;
short U43 = 0;
short U44 = 0;
short U45 = 0;
short U46 = 0;
short U47 = 0;
short U48 = 0;
short U49 = 0;
short U50 = 0;
short U51 = 0;
short U52 = 0;

Match.iff

Quote:

Spoiler:

int isValid = 0;
int ItemID = 0;
String ItemName = "";
short lvlReq = 0;
String Icon = "";
String Icon2 = "";
String Icon3 = "";
String Icon4 = "";
String Icon5 = "";
String Icon6 = "";
String Icon7 = "";
String Icon8 = "";
Short U2 = 0;
Short U3 = 0;
Short U4 = 0;

OfflineShop.iff

Quote:

Spoiler:

int numRef = 0;
int ref1 = 0;
int ref2 = 0;
int ref3 = 0;
int ref4 = 0;
int ref5 = 0;
int ref6 = 0;
int ref7 = 0;
int ref8 = 0;
int ref9 = 0;
int ref10 = 0;
int ref11 = 0;
int ref12 = 0;
int ref13 = 0;

Part.iff

Quote:

Spoiler:

String Sprite2Name = "";
// The following bytes could be 6 shorts too
byte numStat1 = 0;
byte numStat2 = 0;
byte numStat3 = 0;
byte numStat4 = 0;
byte numStat5 = 0;
byte numStat6 = 0;
byte numStat7 = 0;
byte numStat8 = 0;
byte numStat9 = 0;
byte numStat10 = 0;
byte numStat11 = 0;
byte numStat12 = 0;
String Sprite3Name = "";
String Sprite4Name = "";
String Sprite5Name = "";
String Sprite6Name = "";
String Sprite7Name = "";
String Sprite8Name = "";
short U33 = 0;
short U34 = 0;
short U35 = 0;
short U36 = 0;
short U37 = 0;
short U38 = 0;
short U39 = 0;
short U40 = 0;
short U41 = 0;
short U42 = 0;
String UString1 = "";
int equipWith1 = 0;
int equipWith2 = 0;
short U67 = 0;
short U68 = 0;
short U69 = 0;
short U70 = 0;

QuestDrop.iff

Quote:

Spoiler:

short U20 = 0;
short U21 = 0;
short U22 = 0;
short U23 = 0;
short U24 = 0;
short U25 = 0;
short U26 = 0;
short U27 = 0;
short U28 = 0;
short U29 = 0;
short U30 = 0;
short U31 = 0;
short U32 = 0;
short U44 = 0;
short U45 = 0;
short U46 = 0;
String Sprite2Name = "";
short Amount = 0;
short U33 = 0;
short U34 = 0;
short U35 = 0;
short U36 = 0;
short U37 = 0;
short U38 = 0;
short U39 = 0;
short U40 = 0;
short U41 = 0;
short U42 = 0;
byte U43 = 0;
byte U47 = 0;
short U48 = 0;
short U49 = 0;

Skin.iff

Quote:

Spoiler:

public String Sprite2Name = "";
short Amount = 0;
byte U33 = 0;
byte U34 = 0;
byte U35 = 0;
byte U36 = 0;
byte U37 = 0;
byte U38 = 0;
byte U39 = 0;
byte U40 = 0;
byte U41 = 0;
byte U42 = 0;
byte U43 = 0;
byte U44 = 0;
byte U45 = 0;
byte U46 = 0;
short U47 = 0;
short U48 = 0;
short U49 = 0;
short U50 = 0;

TikiPointTable.iff

Quote:

Spoiler:

int ID = 0;
int ItemID = 0;
byte lvlReq = 0;
byte U2 = 0;
byte U3 = 0;
byte U4 = 0;
byte U5 = 0;
byte U6 = 0;
byte U7 = 0;
byte U8 = 0;
byte U9 = 0;
byte U10 = 0;
byte U11 = 0;
byte U12 = 0;
byte U13 = 0;
byte U14 = 0;
byte U15 = 0;
byte U16 = 0;
byte U17 = 0;
byte U18 = 0;
byte U19 = 0;
byte U20 = 0;
byte U21 = 0;
byte U22 = 0;
byte U23 = 0;
byte U24 = 0;
byte U25 = 0;
byte U26 = 0;
byte U27 = 0;
byte U28 = 0;
byte U29 = 0;
byte U30 = 0;
byte U31 = 0;
byte U32 = 0;
byte U33 = 0;
byte U34 = 0;
byte U35 = 0;
byte U36 = 0;
byte U37 = 0;
byte U38 = 0;
byte U39 = 0;
byte U40 = 0;

TikiRecipe.iff

Quote:

Spoiler:

int ID = 0;
int ItemID = 0;
byte lvlReq = 0;
byte U2 = 0;
byte U3 = 0;
byte U4 = 0;
byte U5 = 0;
byte U6 = 0;
byte U7 = 0;
byte U8 = 0;
byte U9 = 0;
byte U10 = 0;
byte U11 = 0;
byte U12 = 0;
byte U13 = 0;
byte U14 = 0;
byte U15 = 0;
byte U16 = 0;
byte U17 = 0;
byte U18 = 0;
byte U19 = 0;
byte U20 = 0;
byte U21 = 0;
byte U22 = 0;
byte U23 = 0;
byte U24 = 0;
byte U25 = 0;
byte U26 = 0;
byte U27 = 0;
byte U28 = 0;
byte U29 = 0;
byte U30 = 0;
byte U31 = 0;
byte U32 = 0;
byte U33 = 0;
byte U34 = 0;
byte U35 = 0;
byte U36 = 0;
byte U37 = 0;
byte U38 = 0;
byte U39 = 0;
byte U40 = 0;
byte U41 = 0;
byte U42 = 0;
byte U43 = 0;
byte U44 = 0;

TikiSpecialTable.iff

Quote:

Spoiler:

public int ID = 0;
int ItemID = 0;
byte lvlReq = 0;
byte U2 = 0;
byte U3 = 0;
byte U4 = 0;
byte U5 = 0;
byte U6 = 0;
byte U7 = 0;
byte U8 = 0;
byte U9 = 0;
byte U10 = 0;
byte U11 = 0;
byte U12 = 0;
byte U13 = 0;
byte U14 = 0;
byte U15 = 0;
byte U16 = 0;
byte U17 = 0;
byte U18 = 0;
byte U19 = 0;
byte U20 = 0;
byte U21 = 0;
byte U22 = 0;
byte U23 = 0;
byte U24 = 0;
byte U25 = 0;
byte U26 = 0;
byte U27 = 0;
byte U28 = 0;
byte U29 = 0;
byte U30 = 0;
byte U31 = 0;
byte U32 = 0;
byte U33 = 0;
byte U34 = 0;
byte U35 = 0;
byte U36 = 0;
byte U37 = 0;
byte U38 = 0;
byte U39 = 0;
byte U40 = 0;
byte U41 = 0;
byte U42 = 0;
byte U43 = 0;
byte U44 = 0;
byte U45 = 0;
byte U46 = 0;
byte U47 = 0;
byte U48 = 0;
byte U49 = 0;
byte U50 = 0;
byte U51 = 0;
byte U52 = 0;

Remember that me myself has named the variables, its just my thought on what its for!

I will report back with the rest of the bytes for the rest of the files later today.
15-01-11
mrNickname

Re: iff-files

I'm not sure how you look into it, but from my hex i see Item Name, zero-bytes until to the dataset.

Then about 35 or 36 zero-bytes down to the price then 10 more to shop tags. There are some additional data in between sometimes but i don't know what are those really for, can only assume as a mark for other purpose.

Anyway i'm new to the hex edit so i might said something in the wrong term maybe :P
15-01-11
Tsukasa

Re: iff-files

First off, there are repeating structures within the Iff files (hereby refered to as IffCommon struct). This file has them too, so it doesn't sport it's own record header and the structure comes down to:

144 bytes IffCommon structure,
40 bytes model name,
2 byte for each stat modifier (only the high byte is used, 5 * 2 = 10 byte in total)
2 byte point marker

No empty or reserved bytes in it, so it's pretty straight forward to edit.

mrNickname, comments like "I can only assume as a mark for other purpose" doesn't help anyone. It's like saying "oh there's data, it's probably there for a reason". Please do your homework and get your facts straight or refrain from posting such comments. It's simply not helpful if you don't have the facts to back up your statements for this sort of development.
15-01-11
chreadie

Re: iff-files

so basically 1 items is 190 bytes in Item.iff?

Im gonna look at some other iff-files and see what i can find.
15-01-11
Tsukasa

Re: iff-files

Where did you get that from? Adding up the numbers gets you to 196 bytes.

You can easily check the length of each record in the IFF files simply by calculating ((filesize - 8) / counter value at the beginning of a file). That'll show you the length of 1 record within that file.
15-01-11
Tsukasa

Re: iff-files

Good call chreadie :)

Strings are usually 40 bytes long (like names, textures or models).
Please note that this is only true for TH and US IFF files. Haven't worked with KR files but JP has more space allocated for those values.
Initially one is probably tempted to think that the last byte for a string has to be 0x00 but this doesn't seem to be the case.

The stats (and actually the stat-specific slots on clubs and clothing as well) are all 2 byte long. There are 5 stat modifiers (Power, Control, Impact, Spin and Curve - exactly in that order). In the item.iff you won't find this but for instance when dealing with the part.iff you'll notice that following the 5 stat modifiers for the initial value there are 5 values for the maximum value. Depending on the file you edit those are either the amount of upgrade points you can spend on this (i.e. 3) or the max value of the item in it's most upgraded state (i.e. 13).

As I stated earlier those values are 2 bytes long, only the first byte is being used though (therefore the max value being 255), the second byte is always 0x00.
15-01-11
chreadie

Re: iff-files

Looking at item.iff, bytes 112 to 115 is my guess of itemtype.

Can someone confirm itemtype of 1 = can be bought for cookies, itemtype of 770 = can be bought for pang?

---------- Post added at 05:30 PM ---------- Previous post was at 05:24 PM ----------

Quote:

Originally Posted by chreadie

Looking at item.iff, bytes 112 to 115 is my guess of itemtype.

Can someone confirm itemtype of 1 = can be bought for cookies, itemtype of 770 = can be bought for pang?

oh i got the bytes wrong! it should be 104 to 107!

Better guess would be that byte 104 would be in shop or out of shop and 105 pang or cookies.
15-01-11
Tsukasa

Re: iff-files

Your edit is absolutely right, although backwards.

Offset 104 is the money byte.
It's one of those dirty little things ntreev uses; the value has to be treated as a bitmask. The lower 4 bits of the byte indicate whether the item has to be paid with cookies or pang, the upper 4 bits of the byte manage whether the item is salable.

As for 105, it's the value mrNickname already mentioned - the shop tag. This, too, is a bitmask, so the values 11 and 21 that you read about in other threads are nothing more than an incomplete representation of possible combinations of options.
16-01-11
chreadie

Re: iff-files

I think i have an idea about byte 104 and 105!

After checking some items i found:

Byte 104:

Tiki Report Paper, total value: 2
bit-value 128: 0
bit-value 64: 0
bit-value 32: 0
bit-value 16: 0
bit-value 8: 0
bit-value 4: 0 // Coupon?
bit-value 2: 1 // Non-giftable?
bit-value 1: 0 // Giftable?

This item has bit-value 2 as 1, "Time Booster" does not. This item is non-giftable but buyable. "Time Booster" is giftable and buyable.

Byte 105:

Tiki Report Paper - 19
bit-value 128: 0
bit-value 64: 0 // Banner: Special?
bit-value 32: 0 // Banner: Hot?
bit-value 16: 1 // Banner: New?
bit-value 8: 0
bit-value 4: 0 // Display only?
bit-value 2: 1 // Pang = 1, Cookie = 0?
bit-value 1: 1 // Show up in shop?

I would love feedback in this!

Also, if you need to edit this in the .iff-files:
Add the numbers of the bit-value and it should be alright.

So playing with this:

I want an item that shows up in shop and costs pang and has the "New" banner would give me an item with byte 105 of value 19!
18-01-11
chreadie

Re: iff-files

Does anyone know anything about byte 106 and 107?
Caddies seem to have values here, wonder why!
19-01-11
sky0165

Re: iff-files

Ok , my iff explanation.

The Syntax has 512 bytes (part.iff)

The 1st byte it's just to know where it begin , normaly 01 , but when it's 00 , the game read it like a "hide" item.

The 5th byte = the value position of the item , like , we have 3 clothes , the yellow red and blue. y=00 r=01 and b=02. If we want add Green to it , we must add there 03 and it will be ok.

the 6th , 7th , and 8th = i never be interested about them

the 9th to 47th = the name of the item.

the 49th byte = the level , 00 = Rookie F 01 = Rookie E 02 = Rookie D

the 50th to 91st = the item image - TGA Image

the 93rd , 94th and 95 = the Price of the item

the 105th and 106th = if the item will be Points/Cookies pang or Hide

the 145th to 186th = the name of the MPET

the 188th , 189th and maybe the 190 = the sommation of the default items. like , if we will add a Dress , the dress uses the TS and PV , TS = 04 (ficticious) and pv = 02 , then the value will be 06 , becuz if we put just 04 , we can use a PV item , it will be weird.

the 197th = the name of the image (JPG not TGA) of the 3D material.

237th = when a 3D model is very complex , they use sometimes 2 image material , and there is the place where you put the second image material.

317th = the name of the first image material in flow. like , if we will add e_ts_27_05.jpg , we will put this thing in the 197th byte and we will put e_ts_27_01.jpg (the first image material in flow) here.

357th = the name of the second image material in flow.we will add something here if the model has 2 image material.

the byte of atribute , and the qty i don't know on season 4

the 505th = if i remember , this is where you set if the item will be tradeable or not. 02 00 01 = non-tradeable 01 00 01 = tradeable .-.

if someone have questions , just ask.

---------- Post added at 01:01 AM ---------- Previous post was at 12:15 AM ----------

my caddie.iff explanation

the 1st byte = as i explain , the initial byte , 01 = unhide 00 = hide

the 5th byte = like tiki , her value = 06 , if we want to add a new caddie , it will be 07

the 6th byte = the name of the cadie

the 49th byte = the level required to purchase , as i said , 00 = rookie F 01 = Rookie E 02 = Rookie D

the 50th byte = the caddie image (TGA)

the 93rd byte = the caddie price

the 106th byte = if the caddie will be cookies/points , pangs or hided

the 145th byte = the value of re-employment , when the caddie is on "vacancy" there will be the price of re-buy it

the 149th byte = the name of the caddie's .PET

the 189th byte = there you set the amout of POWER the caddie will add for you

the 191st byte = there you set the amout of CONTROL the caddie will add for you

the 193rd byte = there you set the amout of ACURRACY the caddie will add for you

the 195th byte = there you set the amout of SPIN the caddie will add for you

the 197th byte = there you set the amout of CURVE the caddie will add for you

the 199th byte = there you set the amout of CONTROL the caddie will add for you
19-01-11
chreadie

Re: iff-files

As Tsukasa stated earlier the first 140ish bytes are the same thru all iff files (except Desc.iff and maybe 2-3 more), just a thought.

Thanks for the ideas about the files, ill compare it to what i have and see what i can figure out!
24-01-11
burningchr0me

Re: iff-files

Here's what I've found so far... I've only really concentrated on the bits that make an item show up in the shop. I've successfuly imported all the US stuff that wasn't in the TH .iff, clothes, caddies, clubs, aztecs...

US and TH part.iff files:

Spoiler:

When I say x # out of 4474 have this, it's based upon the part.iff I was looking at at the time, which had 4474 lines in it.
Pair01-04: Dunno, almost always 00
Pair05: Valid Item? This is one that needs to be on for the item to show in the shop
Pair06-08: All 00
Pair09-12: Item Number - Reverse these numbers and convert from Hex to Decimal to get item ID (1D080008 -> 0800081D = 134219805)
Pair13-52: Item Name
Pair53: User Rank
Pair54-93: Shop Icon (filename without extension)
Pair:94-96: All 00 (combined it with the shop icon in my database)
Pair97-100: Price
Pair101-108: Dunno, only 165 lines out of 4474 have anything set here and most of those only in Pairs 101 and 102
Pair109: Points (01) or Pang (02)
Pair110: Enabled In Shop (01 & 03 - Normal, 10 & 11 - New, 21 & 22 - Hot!, There's more, but I don't know what they do)
Pair111: Dunno, only 4 items have this set
Pair112: Dunno, only 2 items have this set
Pair113-116: Nothing, all 00
Pair117-148: Dunno, but ~300 items have this set. I think it's a time limited setting, because items won't show up in the shop unless you set these to all 00
Pair149-188: MPET file (without extension)
Pair189-200: Dunno, can't see a clear pattern
Pair201-240: Texture File 1
Pair241-280: Texture File 2
Pair281-320: Texture File 3
Pair321-360: Texture File 4
Pair361-400: Texture File 5
Pair401-440: Texture File 6
Pair441: Power Boost
Pair442: Dummy
Pair443: Control Boost
Pair444: Dummy
Pair445: Impact Boost
Pair446: Dummy
Pair447: Spin Boost
Pair448: Dummy
Pair449: Curve Boost
Pair450: Dummy
Pair451: Power Slot
Pair452: Dummy
Pair453: Control Slot
Pair454: Dummy
Pair455: Impact Slot
Pair456: Dummy
Pair457: Spin Slot
Pair458: Dummy
Pair459: Curve Slot
Pair460: Dummy
Pair461-463: Dunno, it's either 302E30 (~1000items) or it's 000000 (the rest) can't see a pattern
Pair464-500: Dummy (all 00)
Pair501-504: some sort of serial number? only 319 items have these pairs set
Pair505-508: follows a similar pattern to the previous, but only 9 items have this set
Pair509: # of Character Card Slots
Pair510: Dummy
Pair511: # of Caddie Card Slots
Pair512: Dummy

There's 4 places you have to concern yourself to make the items show in the shop. The 5th pair, which seems to be like Valid Item or something; Pair 133, which is the Pang or Points bit; Pair 134, which is the Enabled In Shop bit; and Pair 135-176, which seems to be something related to a "Time Restricted" bit, or maybe it's a frequency of rare thing... dunno. I could make the items show in the shop by setting all 00 in that range.

JP part.iff file:

Spoiler:

Pair01-04: Dunno, varies in JP file
Pair05: Valid Item? This is one that needs to be on for the item to show in the shop
Pair06-08: All 00
Pair09-12: Item Number - Reverse these numbers and convert from Hex to Decimal to get item ID (1D080008 -> 0800081D = 134219805)
Pair13-76: Item Name (Double-byte characters of Japanese requires more space)
Pair77: User Rank
Pair78-118: Shop Icon (filename without extension)
Pair:119-120: All 00 (combined it with the shop icon in my database)
Pair121-124: Price
Pair125-132: Dunno
Pair133: Enabled In Shop (01 & 03 - Normal, 10 & 11 - New, 21 & 22 - Hot!, There's more, but I don't know what they do)
Pair134: Points (01) or Pang (02)
Pair135-176: Dunno, but I think it's a time limited setting
Pair177-216: MPET file (without extension)
Pair217: Dunno, but most have this set (only 900 do not)
Pair218-220: Dummy, all 00
Pair221-223: Dunno, can't see a clear pattern
Pair224: Dunno
Pair225-227: Dunno
Pair228: Dummy
Pair229-268: Texture File 1
Pair269-308: Texture File 2
Pair309-348: Texture File 3
Pair349-388: Texture File 4
Pair389-428: Texture File 5
Pair429-468: Texture File 6
Pair469: Power Boost
Pair470: Dummy
Pair471: Control Boost
Pair472: Dummy
Pair473: Impact Boost
Pair474: Dummy
Pair475: Spin Boost
Pair476: Dummy
Pair477: Curve Boost
Pair478: Dummy
Pair479: Power Slot
Pair480: Dummy
Pair481: Control Slot
Pair482: Dummy
Pair483: Impact Slot
Pair484: Dummy
Pair485: Spin Slot
Pair486: Dummy
Pair487: Curve Slot
Pair488: Dummy
Pair489-498: Dunno, it's hex that spells out in katakana "ワンピース(One Piece)"
Pair499-528: Dummy (all 00)
Pair529-532: some sort of serial number? only 319 items have these pairs set
Pair533-536: follows a similar pattern to the previous, but only 11 items have this set

I didn't spend much time on the japanese stuff yet, though I did import the Hatsune Miku outfit from it (before getting around to the US one, which also had it, and in the right format of the TH .iff file).

I created an access database that I can import a hexdump of the iff file, and then it converts the hex to string and numbers for me. It's helped me figure out what some of the stuff is:

Spoiler:

http://img820.imageshack.us/img820/7808/databasecx.jpg

Don't forget that the first 4 pairs in the file are the number of items in the file, and the last 4 pairs are just 00. Look at an existing one, and you'll see how the first part goes.
24-01-11
chreadie

Re: iff-files

Nice explanation but i would rather have which bytes are concerned then the "pair".

Nice program!
24-01-11
burningchr0me

Re: iff-files

Quote:

Originally Posted by chreadie

Nice explanation but i would rather have which bytes are concerned then the "pair".

Nice program!

I think what I'm calling a pair may actually be called a byte... I'm just learning this stuff, and those are notes I've been keeping from the beginning.
24-01-11
Diovannel2

Re: iff-files

Quote:

Originally Posted by burningchr0me

JP part.iff file:

Spoiler:

Pair133: Enabled In Shop (01 & 03 - Normal, 10 & 11 - New, 21 & 22 - Hot!, There's more, but I don't know what they do)
Pair134: Points (01) or Pang (02)

JP is not like Thai.
Thai have a unique code difference, i work with .iff's since season 3 on KR,JP,US... So, when i touched to thai, i had to learn the new codes.

On JP:
"Pair133" is how it'll be showed and bought on shop.
01 is gacha rare, 02 is papel shop rare (to allow mail and lounge stuff, but don't show on shop)
22 is tradeable + sold by pang on shop, 20 is not tradeable + sold by pang on shop.
21 is points.

"Pair134" is the tags (new, hot, etc...)

An image to explain better the JP & other: http://i53.tinypic.com/2dgni94.jpg

The unique main difference between thai and others, are the numbers used to identify pang or rare stuff.
24-01-11
chreadie

Re: iff-files

Quote:

Originally Posted by Diovannel2

JP is not like Thai.
Thai have a unique code difference, i work with .iff's since season 3 on KR,JP,US... So, when i touched to thai, i had to learn the new codes.

On JP:
"Pair133" is how it'll be showed and bought on shop.
01 is gacha rare, 02 is papel shop rare (to allow mail and lounge stuff, but don't show on shop)
22 is tradeable + sold by pang on shop, 20 is not tradeable + sold by pang on shop.
21 is points.

"Pair134" is the tags (new, hot, etc...)

An image to explain better the JP & other: http://i53.tinypic.com/2dgni94.jpg

The unique main difference between thai and others, are the numbers used to identify pang or rare stuff.

This is what i discussed here
02-02-11
bubbastic

Re: iff-files

Quote:

Originally Posted by sky0165

The Syntax has 512 bytes (part.iff)

The 1st byte it's just to know where it begin , normaly 01 , but when it's 00 , the game read it like a "hide" item.

The 5th byte = the value position of the item , like , we have 3 clothes , the yellow red and blue. y=00 r=01 and b=02. If we want add Green to it , we must add there 03 and it will be ok.

the 6th , 7th , and 8th = i never be interested about them

1st byte is 01 for "active" or 00 for "hidden". This part is ok

Bytes 5-6-7-8 are the ItemID! Nothing to do with colors:lol:
13-02-11
hvdaedalus

Re: iff-files

great thanks chreadie. I am still looking into this, and if it's ready, I will release my little iff editor (will be a reader at first :))
13-02-11
chreadie

Re: iff-files

cant wait for it! Java is a bitch when it comes to unsigned stuff (its not available natively)
16-02-11
hvdaedalus

Re: iff-files

IFF Structure for Card.iff is wrong. Corrected one here:

Code:

string Sprite2Name; short U14; short U33; short U34; short U35; short U36; short U37; short U38; short U39; String UString1; String UString2; String UString3; short U40; short U41; short U42; short U43;
16-02-11
chreadie

Re: iff-files

Thanks for noticing this! Updated!
22-02-11
hvdaedalus

Re: iff-files

chreadie could you please post how long those values are? Some of your shorts are only bytes and others are 2 bytes. I'm still stuck on this.

btw, little size bible:

byte => byte
short => 2 byte
int => 4 byte
long => should be 8 byte (see definition for that one, some weird things are going on with this)

unsigned => same sizes (Remember: short 0xFFFF = -1, ushort 0xFFFF = 65535)
22-02-11
chreadie

Re: iff-files

The reason im using shorts for bytes is Java, if à byte larger then # then the value turns negative.

Im currently correcting this while adding write support, ill post back with more exact definitions when im done with this.
Posted via Mobile Device
24-02-11
chreadie

Re: iff-files

Updated Part.iff and added spoilers around the different filedefinitions

---------- Post added at 07:59 AM ---------- Previous post was at 07:31 AM ----------

Updated QuestDrop.iff definition

---------- Post added at 08:39 AM ---------- Previous post was at 07:59 AM ----------

Updated TikiPointTable.iff definition

---------- Post added at 09:10 AM ---------- Previous post was at 08:39 AM ----------

Updated definition for Skin.iff, Tiki*.iff
24-02-11
PHOENIXXXX

Re: iff-files

Here are the details of a clubest.iff

http://img833.imageshack.us/img833/6...bsetiff.th.jpg
08-03-11
kanin983

Re: iff-files

Quote:

Originally Posted by burningchr0me

http://img820.imageshack.us/img820/7808/databasecx.jpg

Don't forget that the first 4 pairs in the file are the number of items in the file, and the last 4 pairs are just 00. Look at an existing one, and you'll see how the first part goes.

Can I have your Program

Please
08-03-11
bubbastic

Re: iff-files

Yeah this one is awesome. I wish BurningChrome would release it <3
08-03-11
hvdaedalus

Re: iff-files

Yeah, that would be awesome. He would become the Awesemechr0me if he releases that one. :'D
08-03-11
bubbastic

Re: iff-files

lol XD
09-03-11
chreadie

Re: iff-files

updated with itemid specification
10-03-11
PHOENIXXXX

Re: iff-files

Based on a 8 bytes line (0-7)in winhex (or other hex editing prog)
An item from Part.iff th has 64 lines
An item from Part.iff Jp has 67 lines
10-03-11
Tsukasa

Re: iff-files

We're talking bytes here, not lines (this isn't Microsoft Word, I mind).

What you probably mean is that a JP part record is 528 bytes long, as opposed to the 512 bytes TH record.
Since an item name in the JP records is 64 bytes long (as opposed to the 40 bytes in TH) and we only have 528 bytes, we're short 8 bytes somewhere in the record when assuming the record has the some properties.
10-03-11
chreadie

Re: iff-files

Quote:

Originally Posted by PHOENIXXXX

Based on a 8 bytes line (0-7)in winhex (or other hex editing prog)
An item from Part.iff th has 64 lines
An item from Part.iff Jp has 67 lines

If you open a file with FileXplorer it will give you the size of every item in the file. This can then be used with any normal hexeditor, in my editor if i select a few bytes it shows how many bytes i have selected. tada.

---------- Post added at 06:33 PM ---------- Previous post was at 06:32 PM ----------

Quote:

Originally Posted by Tsukasa

We're talking bytes here, not lines (this isn't Microsoft Word, I mind).

What you probably mean is that a JP part record is 528 bytes long, as opposed to the 512 bytes TH record.
Since an item name in the JP records is 64 bytes long (as opposed to the 40 bytes in TH) and we only have 528 bytes, we're short 8 bytes somewhere in the record when assuming the record has the some properties.

Is JP newer then TH? if so it might be that they removed some unneeded columns which were supposed to be used for something.
10-03-11
PHOENIXXXX

Re: iff-files

Jp with the Kr version are the oldest versions. Pangya Jp was launched like 6 month afet the Kr release.
10-03-11
Tsukasa

Re: iff-files

Quote:

Originally Posted by chreadie

If you open a file with FileXplorer it will give you the size of every item in the file. This can then be used with any normal hexeditor, in my editor if i select a few bytes it shows how many bytes i have selected. tada.

---------- Post added at 06:33 PM ---------- Previous post was at 06:32 PM ----------

Is JP newer then TH? if so it might be that they removed some unneeded columns which were supposed to be used for something.

The use of the fields is different, they have fields for Gacha and other stuff we miss in TH.
10-03-11
PHOENIXXXX

Re: iff-files

Quote:

Originally Posted by Tsukasa

The use of the fields is different, they have fields for Gacha and other stuff we miss in TH.

Still working on it: but no i don't think so... the main difference like has said Chreadie is for the name which is longer.
Some bytes have also changed places.
I should finish cross checking with other part.iff soon.
10-03-11
chreadie

Re: iff-files

Ive noticed that by using my bitmask for item position i get different values for different characters items:

Nuri Shoes is 5 while Hana shoes is 6, anyone have any ideas?
10-03-11
hvdaedalus

Re: iff-files

Do a cross check with other characters, maybe you will encounter the same.
10-03-11
chreadie

Re: iff-files

i did and i found that most have the same as hana but not all, maybe they are related to the 3d-model?
11-03-11
chreadie

Re: iff-files

All long's should be treated as int's.
13-03-11
PHOENIXXXX

Re: iff-files

I have just checked the Kr part.iff.
It has 516 bytes. Seems very close to the TH and US part.iff.
All the 1st 144 bytes and all textures are the same.
Only the Hidemask has moved (?)
Flags (shop and money) could be like those on the jap version.

http://img850.imageshack.us/img850/3...orrecteng2.jpg

http://img852.imageshack.us/img852/2622/partiffeng.jpg
16-03-11
chreadie

Re: iff-files

Card.iff is a little bit different than i originally thought, first byte custom to card.iff defines (what i believe to be) what type of card it is.

I will update my application soon to support this.
17-03-11
Tsukasa

Re: iff-files

Quote:

Originally Posted by chreadie

Ive noticed that by using my bitmask for item position i get different values for different characters items:

Nuri Shoes is 5 while Hana shoes is 6, anyone have any ideas?

This is normal. The PosMask value within the IFF is different for each character. Here's a somwhat complete mask for Kooh:

Spoiler:

Code:

Kooh 32 28 24 20 16 12 8 4 ____Ž`____ ____Ž`____ ____Ž`____ ____Ž`____ ____Ž`____ ____Ž`____ ____Ž`____ ____Ž`____ 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `- Hair | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `---- Ears (Face?) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `------ Upper Body | | | | | | | | | | | | | | | | | | | | | | | | | | | `--------- Sleeves | | | | | | | | | | | | | | | | | | | | | | | | | | `------------- Gloves | | | | | | | | | | | | | | | | | | | | | | | | | | `---------------- Panties | | | | | | | | | | | | | | | | | | | | | | | | | `------------------- Legs | | | | | | | | | | | | | | | | | | | | | | | | `---------------------- Shoes | | | | | | | | | | | | | | | | | | | | | | | `------------------------- Cannon (?) | | | | | | | | | | | | | | | | | | | | | | `---------------------------- (?) | | | | | | | | | | | | | | | | | | | | | `------------------------------- Dress Bow | | | | | | | | | | | | | | | | | | | | `---------------------------------- (?) | | | | | | | | | | | | | | | | | | | `------------------------------------- Hair Ribbon | | | | | | | | | | | | | | | | | | `---------------------------------------- Hat | | | | | | | | | | | | | | | | | `------------------------------------------- (?) | | | | | | | | | | | | | | | | `---------------------------------------------- (?) | | | | | | | | | | | | | | | `------------------------------------------------- Wings | | | | | | | | | | | | | | `---------------------------------------------------- Glasses | | | | | | | | | | | | | `------------------------------------------------------- Blushies | | | | | | | | | | | | `---------------------------------------------------------- Left Face War Paint | | | | | | | | | | | `------------------------------------------------------------- Right Face War Paint | | | | | | | | | | `---------------------------------------------------------------- Ears/Headset/Feathers | | | | | | | | | `------------------------------------------------------------------- Tail | | | | | | | | `---------------------------------------------------------------------- Motion Item | | | | | | | `------------------------------------------------------------------------- (?) | | | | | | `---------------------------------------------------------------------------- (Unused?) | | | | | `------------------------------------------------------------------------------- (Unused?) | | | | `---------------------------------------------------------------------------------- (Unused?) | | | `------------------------------------------------------------------------------------- (Unused?) | | `---------------------------------------------------------------------------------------- (Unused?) | `------------------------------------------------------------------------------------------- (Unused?) `---------------------------------------------------------------------------------------------- (Unused?)

As you'll notice the Pos marker you extract from the TypeID gives you the bit position (starting from 0) of the primary item type (i.e. Blushies or Feathers). This is important to note when dealing with items that take multiple slots.

I assume that due to the different model structure of each character, we'll have to run 9 different PosMasks.

A more interesting aspect is the Type value one can extract from the Type ID - it seems to be constantly increasing (just like the Serial, where I do expect this behaviour). For Nuri it's 0 for all upper body and lower body parts and many hats (if sorted by TypeID "Halloween (Nuri)", 134223885 will be the last item with type 0) - but suddenly starts fluctuating for newer hats (starting with the "Tomahawk Headset", 134293504 [type: 1] and goes on with the "Gentleman Hairdo", 134348800 [type: 2]). Begs the question whether or not the choice important. Every character has 4 numbers reserved, starting at 0. Some numbers are not being used, though.

It seems generated Type IDs with 0 as Item Type will still work fine - but as with the UCC shirts (where some of the DB values from the Type ID have been nulled) there might be problems later on (currently you can only buy one UCC shirt - so I guess the values are wrong).
18-03-11
chreadie

Re: iff-files

Nice explanation!

From what ive seen:
Position it a digit between 0 and 20 and type is a digit between 0 and 4.

More research will teach us more!
15-07-13
chreadie

Re: iff-files

updated with more details about base structure