Perl Import_Spells.pl - Page 2

**GeorgeS** · #16 07-15-2009, 09:38 PM

If it ran for that long, there should have been some progress indicated. On my laptop it loads 500 spells in 3 seconds. I cannot comment adversely otherwise without more details

Please backup your table first, before running this

Also, in addition, how do you all create the table? -- it should have 215 fields for SOF

GeorgeS

Krugus · #17 07-15-2009, 10:14 PM

the .sql for the spell table file is located in the eqemu/utils/sql/svn/ then look for the file 230_spells_table.sql that will be the sql needed to create the table for SoF.

Its listed in the change log as well as the directions on how to import spells via the perl script

**GeorgeS** · #18 07-15-2009, 10:49 PM

For those who use Ti, the program supports Ti spells.
Select the option for Ti when exporting, or if you select SOF when using a Ti spell set, it will export to SOF compatibility

GeorgeS

-- the above SQL is what I used. I hope everyone uses the same file

**trevius** · #19 07-15-2009, 11:10 PM

GeorgeS,

There isn't a need for Titanium exporting, only for Titanium importing. The spell files are backwards compatible, meaning that a Titanium client can use a SoF client spell file perfectly fine. The only problem is that it is not forward compatible, so an SoF client cannot use a Titanium client spell file. For any server wanting to share a customized spell file or a single spell file to use for both clients, they should only be sharing the SoF version, since it will work with both types. IMO, there isn't any need to export into Titanium format. The only possible use of it would be to slightly reduce the file size. The only other difference between the clients as far as the spell files go is that Titanium can only load spell IDs up to 9999, where SoF has a much higher limit (currently I am not aware of what the max is, but it should be at least 20K+).

**GeorgeS** · #20 07-15-2009, 11:37 PM

Ti export is for just re-creating the Ti spell file. You have the choice of exporting it to a SOF compat. format. I'll leave that end to the user to determine, but in any event, it should cover all bases.

GeorgeS

**trevius** · #21 07-16-2009, 12:07 AM

Yeah, no harm in leaving the option. Just wanted to give a heads-up mostly.

ChaosSlayerZ · #22 07-17-2009, 12:40 AM

Nice! I am looking forward to trying this out as soon as I done with Rev updates

rizzen · #23 07-30-2009, 09:04 PM

I also tried to run the application, it ran my processor at 100% until I killed it.

**GeorgeS** · #24 07-31-2009, 10:13 AM

Yes, the importation of that much data takes 100% of your CPU. Let it run till it's done.

It takes up to 5 min on my pc

GeorgeS

Yeormom · #25 08-21-2009, 01:30 AM

Grabbed the new version from your site tonight and it ran very well for exporting. The only note if no importance I can make is you can't export without at least having a blank spells_us.txt file. However, with one, all Titanium spells dumped, across the Internet, in less than 5 seconds, including extra latency from my port remapper since the MySQL port isn't configurable through your front-ends.

Saved me a few hours work so thanks George!

**GeorgeS** · #26 08-22-2009, 12:51 AM

Glad you like the tool!

Saves me quite some time as well when I make custom spells.

GeorgeS

Randymarsh9 · #27 11-08-2009, 09:32 PM

Do you still have to use the import_spells.pl to get new spells on your server? I noticed I'm already having trouble with it again and I want to know if you can still just use a spells_us for spells on your server.

leslamarch · #28 11-08-2009, 09:50 PM

Quote:

Originally Posted by Randymarsh9

Do you still have to use the import_spells.pl to get new spells on your server? I noticed I'm already having trouble with it again and I want to know if you can still just use a spells_us for spells on your server.

in spdat.h Find this (around line 42)

Code:

//#define NEW_LoadSPDat
#define DB_LoadSPDat    //load from DB vs spells_us.txt. for now, we're piggybacking NEW_LoadSPDat, so it will take precedence

change it to this

Code:

#define NEW_LoadSPDat
//#define DB_LoadSPDat  //load from DB vs spells_us.txt. for now, we're piggybacking NEW_LoadSPDat, so it will take precedence

Then it will use the spell file like it used to...

Randymarsh9 · #29 11-08-2009, 10:38 PM

Awesome, changed that, compiled. and now my toon has his 75 spells. Thanks again, lol

ChaosSlayerZ · #30 11-09-2009, 12:44 AM

i really wish they would have made that part into a rule, rather than define option...