Pros of consolidation:
If all classes that share a common ability are using the same spell_id (record), you can change the single record and effect all other classes immediately. You do not have to go change all the other records, too. This simplifies maintenance and customization. The other bonus is less data in the database (negligible) and thus less overhead for the server engine.
Cons of consolidation:
Right now, every class has their spells ID'd by class_id * 1000 (so class 1 would have spell_id's 1000-1999, class 40 would be 40000-40999 etc). This was to simplify grouping and identification. However, if we decide to consolidate common spells, that means identifying each possible ability that might be used by some other class, and creating a "common" version of all 9(ish) tiers. Lots of manual effort, but it is done once up front. The second "con" is, what if you want Taunt to work differently for Bruisers than you do Monks? With a common record, you'd have to either split the record during your customization, or hard code something in your source to deal with the differences. Eww...
We already have a huge effort ahead of us to "clone" the spells list we have into multiple tiers. I am not opposed to either way, though consolidation makes sense for the base emulator. For Customization, maybe the work needs to be on the admins themselves and not us.
I am asking for general feedback on what you think is best before we get started. Thoughts?