Old food tables: Finish, or replace?

Where it would get the data from: We could either add parameters for each spirit type to the current item data templates, or make separate data templates for the spirit food stats. A separate template might be easier on the server since all the item's other data would not be getting passed to the table that doesn't use it, and it would be easier to add data to it since there'd be less scrolling/searching, but we'd be making a lot of new pages for these templates, and there would be a redundant price parameter(both the regular item data template and the food stats template would include the item's price). If there are any items where the differently priced versions give different stats, (afaik there are none, but I'd like to be prepared for anything) the separate template method may be cleaner; if we just append the current data templates, then we may still have to add a separate template for the special version of that item with just the food parameters(with the same parameter names so it can use the same style template in the table). Also, the parameter names would probably be shorter(in a template just for feeding stats, we can just name the parameters as weapon category plus M or F (example: bowM, bowF, bluntM, bluntF...) but if we put food data with the regular data, we may have to add something to the names to avoid confusion (example: egofoodBowM, egofoodBowF, egofoodBluntM, egofoodBluntF...).

I should probably have done this when I proposed the data/style method, but I was tired: Pros (of using data/style)

1. easier for editors to add data(with named parameters, the contributor doesn't have to keep track of the order the columns are in and count the pipes in the row)
2. it may be easier to change the format of the table when we need to (just edit the row style template and maybe the header, instead of changing each row individually)
3. we can more easily add conditional formatting (for visual efficiency), ie. make the text color vary depending on the stat, or make the cell background color represent the efficiency rank of that stat for that spirit.
4. we could use the info in more than one place without having to copy/paste each detail manually. For example, we could also add tables that only display info for one spirit coming from the same data templates, and we could add individual item tables (similar to what's at the bottom of Littlesnow's userpage) to the item's page.

I think I had more, but these were the main ones.

As for cons, nothing significant comes to mind so far. If anyone is worried that the coding may be complicated, don't be; I will probably take care of most if not all of the style code unless someone faster or with more free time beats me to it, and code for data will be fairly simple, and more user(data editor) friendly than a plain table would be.