Fletching data

[zs4yswtf]

I made a personal fletcher for cutting logs into useless bows and this is data from that. (Incase anyone doesn't feel like collecting it)

//Logs ID, Uncut ID, Parent interface, child interface.
int[][] fletchingData = { 
{1511, 52, 305, 8}, //Shafts
{1511, 50, 305, 12}, //Shortbow
{1511, 48, 305, 16}, //Longbow
{1521, 54, 304, 7}, //Oak Shortbow
{1521, 56, 304, 11}, //Oak longbow
{1519, 60, 304, 7}, //Willow Shortbow
{1519, 58, 304, 11}, //Willow longbow
{1517, 64, 304, 7}, //Maple Shortbow
{1517, 62, 304, 11}, //Maple longbow
{1515, 68, 304, 7}, //Yew Shortbow
{1515, 66, 304, 11}, //Yew longbow
{1513, 72, 304, 7}, //Magic Shortbow
{1513, 70, 304, 11}, //Magic longbow
};
//Exp correlates with fletchingData
float[] fletchingExp = {
0.33f*15f, 5, 10, 16.5f, 25, 33.3f, 41.5f, 50, 58.3f, 67.5f, 75, 83.3f, 91.5f
};

[Swizzbeat]

Looks good, but you could convert that to an enum.

[DarkAngel]

Why not use an enum?

[Pseudo]

Makes just as much sense, if not more, to use a 2d array than an enum here..

[zs4yswtf]

I didn't use an enum for reasons of simplicity in the code. To be honest, I don't even use the XP but I had it anyway.

 

And besides, it's not really important how the data is setup if it is there, this is just to give people numbers, not how to set up these numbers in any way.

Edited June 18, 2014 by zs4yswtf

[Swizzbeat]

Makes just as much sense, if not more, to use a 2d array than an enum here..

explain corey with an e

[Khaleesi]

I didn't use an enum for reasons of simplicity in the code. To be honest, I don't even use the XP but I had it anyway.

 

And besides, it's not really important how the data is setup if it is there, this is just to give people numbers, not how to set up these numbers in any way.

 

Ya thx for the data! I'm sure people would like that!

 

And ofcourse enums makes the code more readable afterwards

But an Array works too!