how you manage your repacks?

[locksoft]

I mean, I always see that in new releases lot of people write "wow, thanks" and try them. for me that I'm a new, a new release means restart everything from scratch:

- create new db
- import sql files
- configure config files
- recreate dbc/maps (if client/server is a different version)

what scares me more it's the DB update. most of repacks use two DB, one for login and char info and one for game data. but sometimes a db also update something in login DB and/or uses a different format (according to emu program: ascent/mangos, etc...).

is there a good faq about how to integrate different DB? or a script to dump all account/user data from old DB and integrate it in the new one? so far I always recreate manually my account/char/reps/items and so... and it's so slow...

I also wonder why there are so many different standards with emulators. I mean, mangos db is one way, ascent another one and so one. isn't it possible to have some collaboration between dev teams just to use a standard format? then everyone can choose the emu they like more but at least they could easily bind the DB they like more. utopy? :]

thanks. :]

[project anthrax]

is this a question or a help thread?

[marcelo_20xx]

The safest way for try a new repack is to dump your current database into a sql batch, bear in mind that it will NOT work under SQLyog but in Navicat (the only reason I use that program). The resulting file should be like 90MB and the data dumped in 15-60 min depending on Pc specs. Do this with your chars tables and you are ready to go.