I'm removing the need to edit 200+ fields of data. I don't mind the size, I'm using a smaller size as a selling point ^-^.
Tell me what the following fields do, as they don't seem to have a use.
Code:
augslot1unk - 40 items = 0, the rest = 1, Field is an Integer
augslot2unk - 336 items = 0, the rest = 1, Field is an Integer
augslot3unk - 494 items = 0, the rest = 1, Field is an Integer
augslot4unk - 233 items = 0, the rest = 1, Field is an Integer
augslot5unk - 99 items = 0, the rest = 1, Field is an Integer
unknown002 - Always = 0, Field is an Integer
unknown003 - Always = 0, Field is an Integer
unknown005 - Always = 0, Field is an Integer
unknown007 - Always = 0, Field is an Integer
unknown018 - Always = 0, Field is an Integer
unknown019 - Always = 0, Field is an Integer
unknown020 - Always = 0, Field is an Integer
UNK012 - Always = 0, Field is an Integer
UNK013 - Is either -1,0,1
unknown061 - Always = 0, Field is an Integer
UNK054 - Always = 0, Field is an Integer
unknown067 - Always = 0, Field is an Integer
unknown069 - Always = 0, Field is an Integer
UNK059 - Always = 0, Field is an Integer
UNK061 - 0 or 1, is integer
unknown081 - Always = 0, Field is an Integer
unknown105 - Always = 0, Field is an Integer
unknown122 - Always = 0, Field is an Integer
unknown123 - all 0, is varchar(11)
unknown124 - all 0, is varchar(11)
UNK123 - Always = 0, Field is an Integer
UNK124 - 0 and 1, is integer
unknown133 - Always = 0, Field is an Integer
UNK127 - Always = 0, Field is an Integer
UNK134 - Is varchar and all entrys are empty
UNK137 - Always = 0, Field is an Integer
UNK142 - Always = 0, Field is an Integer
UNK147 - Always = 0, Field is an Integer
UNK152 - Always = 0, Field is an Integer
UNK157 - Always = 0, Field is an Integer
serialized - All entrys are null
serialization - All entries are null
UNK033 - Always = 0, Field is an Integer
UNK014 - -1 0 and 1
svcorruption - Should be next to the other resists and name should be or since c is cold.
UNK038 - Always = 0, Field is an Integer
UNK060 - Always = 0, Field is an Integer
augslot1unk2 - Always = 0, Field is an Integer
augslot2unk2 - 61762 are 0 rest are 1, Field is an Integer
augslot3unk2 - 61613 are 0 rest are 1, Field is an Integer
augslot4unk2 - 62113 are 0 rest are 1, Field is an Integer
augslot5unk2 - Always = 0, Field is an Integer
UNK098 - 18753 are 0, rest are 70
UNK109 - Always = 0, Field is an Integer
UNK120 - -1,0,4
UNK121 - Always = 0, Field is an Integer
UNK131 - Always = 0, Field is an Integer
UNK132 - is one of the following, 0,0000000000000000000,00000000000000000000000000000000000000 and is a TEXT field
clickunk5 - Always = 0, Field is an Integer
A lot of the list is always 0, it would be faster to have the program assume a 0 than to query. Also, when looking down the defaults in the item table, they aren't the defaults.
Classes for instant, is more likely to be 65535 than anything else. I know its a bit field, but lets face it, 60% of items are ALL/ALL.
Then theres the fact that so many of the fields are using INTEGER when they should be using BOOLEAN, some even use varchar which is a big no no on entries that will only use numbers.
The database needs work, a lot of the work is DB only. Things like field type, and defaults. I'm willing to do the DB work if the community will accept and use it, not as a small cult following but as true integration.
As for removing unused columns, I figure someone will argue that they may be used in the future. Well, thats the future. In the future there might be space ships that run on poo, should we start saving our poo now or wait till that day comes? I think it would be best to assume those entries are useless and to remove them until they are used. At which point, adding them back is a simple process of adding it to the query, removing the programs default, and pushing it in. Takes about two minutes if you know what your looking for.
Anyway, continue.