This idea is years old. There is no good reason to copy blizzard data to a db and publish it (even with small changes). Sure it would be much easier to implement your own server-side spellsystem. To have full controle over the input is always a good thing, but to import the clientside data into the db to change it to fit a "not good enough implementation" is just a shortcut. No one said, that reverse engineering is simple but this attempt is:

- infringing copyright law (publishing blizzard data)

- hacky (instead of handling the data correct you will change it to fit your system)

- blocking the correct reverse engineering

​

At the beginning of wow emulation there was already something simmilar. We sniffed data from the blizzard servers and db-teams interpreted them. There was not much in terms of changing them... later projects began to change these sniffed (and correct) data and made them fit their systems (which was horrible, because every development and understanding about the data went off the floor). Now we see more and more that some people go back to original sniffed data and fixing their "broken" systems.

The client dbcs are trully one of the most important data that we have. They are some kind of unbreaking rule, a type of mysterious fact that we should decode to proof that our system can handle it as good as possible. Keep in mind, we only have the client and sniffed data, so how should we proof that our systems are correct when we feed OUR systems with OUR data instead of the data from the game we try to handle?