Considering furnidata is usually cached anyways (requiring a refresh, either live or with a server restart to change the data), it's honestly not that bad of an idea, given what a total clusterfuck state that table is currently in. But he's right about the Z-height, that's not in there.
Habbo actually renders the furnidata, productdata and figuredata XML/JSON from their database, it's not maintained as a separate copy. The smart move would be to put
all data in the furniture table and use a PHP script or something to render it (cached copy of course) based on the info in the database. Perhaps have the server regenerate it when it starts (through like an API task to communicate with the web server), and have :refresh_whatever trigger that same task.
Just food for thought. @
Charlotte Potts idea isn't retarded, but it
is backwards. It's significantly more convenient to have the records in the database anyways, makes it easier to modify or add customs.