Loading furnidata (Question?)

[Damien]

I need help deciding the best approach to handling item_data on the emu.

1) Storing it via the database like how it's done on most emulators.
2) Loading the data from the furnidata and setting it that way.
3) Store it via the database, and generating the furnidata from the database.

The only downside to loading it via the furnidata is it doesn't contain the height attribute (which I can easily add). Opinions?

don't bother commenting if you're not going to back up you opinion with reasoning.

 

[Mikee]

I don't have an answer for you but I definitely don't recommend loading it from furnidata UNLESS the furnidata is sorted. Because if you did keep it sorted then you could do a bisection search and pull item data that way, which in return WOULD be a good idea. (But once again the data NEEDS to be sorted)

Why would a sorted furnidata with item data be a good chocie IF sorted?
A bisection sort has a complexity of O(Logn), While a database lookup has a complexitiy of O(n) therefore a bisection search aka pulling itemdata from furnidata file would be faster (IF SORTED!!).

Why do i emphasize sortment?
Because its expensive.
You'd need to sort the data once and keep it sorted or else it'll be a mess.
If you sort it each time you run a bisection sort it'll be more expensive than a db lookup.
So sort it once, keep it sorted, and its a great idea.

 

[Pinkman]

3.