Quote:
Originally Posted by Dylan1994
Could someone please tell me how to set up EQExtracter so that i am able to use it... For some reason im am unable to get it to work.... Help would be appreciated
|
You need to install the .NET Framework 4 from Microsoft first, I think this is the right link:
http://www.microsoft.com/downloads/d...displaylang=en
After that, install Wireshark
http://www.wireshark.org/download.html
And finally download EQExtractor2
http://projecteqemu.googlecode.com/f...actor2-211.rar and use Winrar to extract the files into a folder of your choosing.
To capture packets for a zone you are interested in, get your character to that zone and then camp to character select.
Start Wireshark and in the Capture/Interface List on the left hand side, click on the name of the network interface that you are using to connect to the Internet.
Back in your Live EQ client, enter the zone. If you just want to collect spawns, you can stop the Wireshark capture as soon as your character appears in the world. To collect pathing, just sit around for a while, or if you want to collect merchant inventory, move around the zone clicking on merchants.
When you are done, in Wireshark, select Capture/Stop then File/Save As to save the captured packets into a .pcap file.
Fire up EQExtractor2, select File/Load PCAP (or press CTRL-L) and select the .pcap file you saved in the previous step.
You should get a message that the client version that was used to make the .pcap was recognised and also the name of the zone you where in.
Next, select File/Generate SQL (or Ctrl-S) and then on the next screen click on the Generate SQL button and give it a file name to save the generated SQL.
You can then use the mysql command prompt or Navicat or whatever, to source this into your database, however be aware that the generated SQL may delete data already in your database.
If you still can't get it to work, let me know what error messages, etc, you are seeing. With the latest EQExtractor2 version, pressing Ctrl-D will bring up a sort of debug-window which may have more detail of what went wrong.