I'd have to ask what you do currently when you want to update to the most recent version of the PEQ database, but don't want to lose your custom changes? Do you have queries made up already that source all your changes back in? That's definitely the best way to go, as it lets you keep current, but lets you customize it the way you see fit.
Depending how many changes you have, I recommend you go back and turn all the changes you made into queries that will re-create the work. To get all the information for just those two zones is a lot of work, though that's from my perspective; I'm sure there are people who know tricks with the databases that I can't even fathom :) Of course, it's easy for me to suggest you do things the way that I do them =P Every time I update the database, I source in a .sql file with these queries and more: Code:
### This allows the rogue epic to be equipped in the range slot like it used to be ### |
I would be interested in this and I'm sure others would too. Would be nice to see more.
Thanks. |
Thanks for splitting this off, though I have to confess I don't have any more than those =/ I have more, but they're all just customizations for the server, unfortunately; nothing else classic-related.
I'm willing to fix up some more, if anyone has suggestions. Kind of embarrassing seeing that there's more interest in this and that I've got nothing else :oops: I think my favorite is the Ragebringer change. That was only changed to not be range slot equippable because rogues kept accidentally throwing them =P |
Anyone else have any classic / custom queries they always use when they set up there database? could get interesting :P
|
This is also how I do it. When upgrading there is always the possibility of a conflict between your SQL commands and the changes done on PEQ, but if you are lucky you will get warnings and you will read them ! At worst you will find out about the conflict when you play :D
Writing the scripts is not hard, but requires a lot of rigor. In the scripts I also precede each change with the command to "revert", or "delete" the change to ensure the script can be run as many times as you need. Ideally what would be needed is a bit of tooling for this : a tool that starts from a fresh PEQ install, applies a few specified scripts with widespread effects (see below) and then compares the modified-PEQ with your current database and outputs the proper SQL commands. That would be great. You want to apply a few SQL commands to the standard PEQ first if you do general changes in the DB, like making all items droppable and such. Otherwise you would end up with a script changing every entry. The use of this tool would be to cope with micro-changes. Anyone feels like writing that ? Eh eh... |
So... Im sorry for reviving this thread... But ive been trying to get the manastone back into the Evil Eye's loot list for a while and I realized that this SQL command is out of date. Is there still a way to do this? Im sure its the 47116 number but I cant seem to find the correct one for the updated SQL.
|
Quote:
|
Yes, sorry. It's not possible for me to edit the original post, unfortunately. This one will do it for you, though:
Code:
### This sets the Evil Eye in Guk to drop the Bag of Sewn Evil Eye 75% and Manastone 25% ### |
All times are GMT -4. The time now is 12:47 PM. |
Powered by vBulletin®, Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.