Aokromes

dbc to sql

May 16th, 2011
377
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 2.10 KB | None | 0 0
  1. [18:08:51] <Aokromes> btw
  2. [18:08:57] <Aokromes> ref dbcs crap
  3. [18:09:04] <Aokromes> we need sometimes to overwriting them
  4. [18:09:05] <Aokromes> :P
  5. [18:09:16] <Aokromes> ie shadow vault flypoint bugged for alliance
  6. [18:09:29] <Machiavelli> We already sometimes do
  7. [18:09:34] <Machiavelli> Just not very generically atm
  8. [18:09:47] <Aokromes> imho the best is sqlize them :P
  9. [18:10:54] <Aokromes> also, if we use sqlized dbcs, we can cof modify blizzards values on db and core modify them to get desired blizzlike values :P on that way less blizzard files are used
  10. [18:10:55] <Aokromes> P:
  11. [18:10:56] <Aokromes> :P
  12. [18:12:00] <Aokromes> and since the values on sql aren't the ones from blizzard... they can say crap
  13. [18:12:00] <Aokromes> xd
  14. [18:12:14] <Machiavelli> It's still their intellectual property :P
  15. [18:12:23] <Machiavelli> (most of the values)
  16. [18:12:32] <Aokromes> what IP? XD 10000*2? :P
  17. [18:12:32] <Aokromes> xd
  18. [18:12:44] <Aokromes> also
  19. [18:12:45] <Machiavelli> lo
  20. [18:12:47] <Machiavelli> l
  21. [18:17:02] <Aokromes> it can help to have more features :)
  22. [18:17:04] <Aokromes> ie new FP
  23. [18:17:25] <Nayd> ability to path GOs in DB would be cool
  24. [18:20:37] <Aokromes> yeah
  25. [18:20:53] <Aokromes> or new transports :)
  26. [18:21:02] <Shocker> i don`t think that's a good idea
  27. [18:21:06] <Shocker> (19:10:56) ~ (+Aokromes) also, if we use sqlized dbcs, we can cof modify blizzards values on db and core modify them to get desired blizzlike values :P on that way less blizzard files are used
  28. [18:21:06] <Shocker> (
  29. [18:21:16] <Shocker> we will always re-extract dbcs and will lose our old overwritten data
  30. [18:21:35] <Machiavelli> unless we add a column
  31. [18:21:41] <Machiavelli> named "CustomEdit" or something
  32. [18:22:02] <Machiavelli> to mark which data has been altered
  33. [18:22:07] <Machiavelli> and don't overwrite that
  34. [18:30:37] <Shocker> still not good
  35. [18:30:45] <Shocker> value may completly change
  36. [18:30:47] <Shocker> in dbc
  37. [18:31:04] <azazel_kon> So, sql will change with each new version of dbc
  38. [18:31:22] <azazel_kon> And yeah, custom data and original data should not be mixed as it is done now
Advertisement
Add Comment
Please, Sign In to add comment