its not about the speed at which the hash tables preform its the clutter that it creates, i try not to clutter my tables with useless items. If the item values are ganna be huge then sure, i give them an item, otherwise i use the method im talkin about.
And about ini and hash tables being the same, i mean format wise. Its still Group, Item Value. May be called dif things but thats what it is. Cept with ini you get another step if you will, File, Group, Item, Value.
My whole reasoning behind this is that i dont want xxxxx amount of items in a hash table that i may need to read through, i like it sorted nice and easy. Anyway.. thanks.
Btw i went through the same thing at
http://www.mircscripts.org/forums.php?cid=3&id=102402#102402lol
*edit*
And in replies to me using the hash tables inefficiently, basically theres a MuD made, with thousands of room and its been in hash form for a while. This discussion about sub items was just to see if someone could code one more efficiently than me which the saubject is going in discussion at mircscripts.org but none the less its for basically info tracking, almost the same as variables in a sence.
The MuD has a table for each room and each table is small but i just did it that way, i could use my method im talkin about above or the way i thought about doing it way back when which is like Table, Item_SubItem=Value
That would take the thousands of rooms, put it into one hash, but for every room you would have anywhere from 10-20+ items, so overall i found just making tables for each more effective. It used to be in ini form but overall im liking it in hash form more.