Rev664

blackdragonsdg · #1 06-15-2009, 04:18 AM

First off I sourced in the 230_spells_table.sql from the svn and it went into the database with no problems but when I attempted to import the spells_us.txt using the command perl import_spells.pl from the command prompt nothing happened. There is not a single spell in the database after running that script. Any specific method to this or am i just unlucky.

**trevius** · #2 06-15-2009, 07:11 AM

Did you move the import script to your server folder where your spell file and config file are located before running the script? And after moving it, did you run:

Code:

perl import_spells.pl

From the command prompt?

If you are running Windows, you might even be able to just doubleclick that file once it is in your server folder and it may run it automatically.

Here is a post with a bunch more details on what to do:
http://www.eqemulator.net/forums/sho...9&postcount=45

Also, make note that it is always a good idea to make a backup copy of your spells file before doing anything like this. Another thing worth mentioning is that the PEQ DB now comes with the spells_new table and it is fully populated, so there is no need to mess with these scripts for newer servers using the PEQ database.

blackdragonsdg · #3 06-15-2009, 07:55 AM

Yes, I put the script in my server folder and ran the perl import_spells.pl command from the run menu and I also just double clicked it and ran it from the folder where it was at and the same thing happened both times. It started then exited and no changes were made to my database. This was all done with administrative privileges.

I am using Vista x64 so it is possible that there is a difference in the way scripts such as this are handled when compared to other operating systems. I guess I will just update my entire database instead of trying to figure out why Vista doesn't like this script, probably far less of a headache that way.

Is there some sort of changelog for the peq database because knowing what was implemented and when it was implemented would go a long way towards preventing problems like this.

**trevius** · #4 06-15-2009, 08:04 AM

PEQ has so many frequent changes that it would probably be near impossible to have a decent changelog of it other than maybe some really vague entries of what was done/changed.

If running the script like you did didn't work, you can always try:

Code:

perl import_spells.pl -h

That will output the help messages to show you how to use the file properly. If you read the post I linked though, it explains what actually needs to be set. Maybe on Vista for some reason, you have to actually set the paths and such to the file names you use for your config file and your spells_us.txt file. Again, if you read the post I linked, it explains all of that pretty well. It is fairly simple to use, though I haven't used it on Vista 64.

Also, if you want to just use the spells file and you are compiling your own source, you can change the define to load it the old way from the spell file very easily. Just do the #define change listed in this post:

http://www.eqemulator.net/forums/sho...3&postcount=72

blackdragonsdg · #5 06-15-2009, 09:03 AM

I did read over that link you posted and it is quite simple as to what the script actually does but I am not the least bit familar with how to write perl scripts even though it did look alot like C99. I think I will leave the script writing to those who know what they are doing.

I just updated by database to the most recent revision of peqdb and all is well with the spells table now.

Thanks for the help!