Foreword:
This is based on Version 3.12 of the script. It will be updated to reflect changes as they come.
These instructions were kind of lost on page 4 of the discussion thread, moving them out to their own thread. I will try to incorporate suggestions from the main discussion thread into here as possible.
I have personally run this for over 8 hour stretches harvesting a 39 waypoint path. It runs smooth, and very human looking with the possible excepton of smacking into the occasional tree but never getting totally stuck.
Firstly, Meet the following preconditions:
- You have a UI window behind the scripts dialog.
BIG tip here for first timers, you need a UI window BEHIND the scripts dialog to get the buttons to actually work. The persona (P) window works great for this. If this paragraph doesn't make sense, stop here. You MUST understand this. Theres something about mouse events in EQ2 where if it's just the 3d landscape behind an XUnleashed window, it can't receive the mouse clicks, you gotta put an EQ2 UI window back there like Persona. The crafter, radar, and all of these scripts have exactly the same issue. If nothing happens when you click < or > buttons on the script window, this is probably your problem.
- Your Free Look Controls is set to avatar centric (Options->Controls->View Options->Free Look Controls)
- Your viewpoint is zoomed out, back and up a little so you are looking down on your toon from above and behind.
- You HAVE successfully got mouse demo to do it's thing. If that doesn't work, dont waste your time fighting with this until you have that much working first. Your problems are NOT related to this script if you cant get mouse demo to work.
- Your keys are set up just like mine are
If they are not, then you will have to adapt the instructions.
- You have logging turned on. Turn logging on by typing /log the first time. Actually to get this script to work, once you turn it on the very first time only, you have to restart EQ so that the log file is where this script expects it to be due to an EQ bug that hopefully gets fixed some day. I'd rather this was handled like it is in the hunter bot but thats another argument.
Double check:
Did you satisfy ALL the prerequisits?
Did they all make sense or did you just rush past them?
The community reserves the right to dish out atomic wedgies to all that skipped past a problem above!
Installation and Configuration steps:
- Download the rar file and extract it into the scripts folder. You should have HarvestBot_v312.ini, HarvestBot_v312.vbs, and ding.wav in your scripts folder as well as a subfolder called EQ2HarvestBot containing 9 more files. (WinRar extracter
http://www.download.com/3000-2250-10007677.html)
- Open HarvestBot_v312.ini and change the following keys to these values:
(!empty($user->lang['CODE'])) ? $user->lang['CODE'] : ucwords(strtolower(str_replace('_', ' ', 'CODE'))):
[Harvester]
; Required as the author uses this change to FORCE you to edit your ini.
DeleteMe = False
; Change to not use hotbar/hotkeys for harvests. It simplifies configuration and doesnt waste a hotbar.
; Later, once you have this thing rolling some feel that it is "safer" to use a hotbar here. I actually do use a hot bar now, less chance of accidentally sending ODD tells.
Hotbar = 0
; I used the default path for EQ2
EQ2Path = c:\program files\sony\Everquest II\
[KeyConfig]
; NUMLOCK is my AUTORUN forward key.
Forward = {NUMLOCK}
; I have the standard default WASD keys still mapped. Dont use them but havent changed them.
Backward = S
Left = A
Right = D
;The rest of the default movement keys are fine for me.
[Resources]
; Change what you want here, I'm not interested in harvesting everything but the default
; now appears to be to harvest all which is nice and clean and a good starting setting.
; Mess with this section AFTER you have everything else working
[JohnnyDoe]
; Also ignore this section until everything else is working. This is where you set up your buffs.
Leave everything else as defaults NOTE, there are lots of new settings, at least since the last version I used, 3.0 so start fresh from the 3.12 sample.
- Now start the game, go to a nice safe zone like commonlands, get near some resources and give this a try. If you are going to try it in antonica, change [Antonica]->UseWayPoints=false so that it doesn't try to use the path.
- Once you have this much working you can start the fine tuning...
- set up your harvest filtering so you don't harvest everything, just what you want.
- set up some harvesting paths
- set up a hotbar if you want, possibly works a bit more efficiently but you waste a hotbar.
- set up buffs
- mess with pet stuff
Known Issues:
- I had problems getting this to work without a path, seemed to go to max CPU usage and lag out. YMMV A simple 2 location path gets around this easily.
- Some of the trapping nodes are now misnamed due to a game change.
Cheers,
RedMan
Harvest Bot 3.xx Instructions : EverQuest 2 Premium Discussions
RSS Feed
Sitemap
