clandestine
Member
- Joined
- May 5, 2012
- Messages
- 350
About
This is my first public plugin, I'm not really a C# coder so this is stitched together from various sources. Mainly from GrindZoneChanger and ExVaults QuestBot. Anyone feel free to improve upon this mess.
Upon entering The Dried Lake, combatrange is set to 0 and it's left up to OldGrindBot to explore the area. Once Voll is found, combatrange is increased to 50 and Voll is killed, looted then the bot returns to town to start a new run.
A run takes anywhere from 30s to 3min, depending on how quick Voll is found.
Your character should be tanky and strong enough to survive Dried Lake without dying and killing Voll in a short amount of time. The bot will not engage in combat unless Voll is nearby, you will get hit, you will take damage, you might die - make sure your character can handle it.
This plugin is released as-is. It works for me, it might not work for you. If it doesn't work for you then the source is there for you to make it better.
This Plugin was only tested with the OldRoutine combat routine. It will probably not work with any of the other community routines out there.
Setting things up
Required Plugins:
- EXtensions (comes bundled with Exilebuddy now)
- CommunityLib
Recommended Plugins:
- Alcor75PlayerMover
-- Make sure to check Ignore Mobs in Alcor75PlayerMover settings. Else the bot will dance around Voll like Michael Jackson
- AdvancedItemFilter
Copy VollFarmer-0.0.0.X.zip to 3rdParty
Create an empty 3rdparty-required.txt in the following plugin:
3rdParty\OldRoutine
Start ExileBuddy
Settings > Plugins > VollFarmer > Enable
Settings > Bots > OldGrindBot > GlobalChestsToIgnore > Check All
Settings > Bots > OldGrindBot > TakeCorruptedAreas > Uncheck
Settings > Plugins > Alcor75PlayerMover > Ignore Mobs > Check
Known Issues:
It's a bit spammy, so logs will grow.
There's a log4net error when making portal to town, it is safe to ignore (and I have no clue why this error comes up, if you know, halp pls):
Support
It doesn't work for you? Attach a Log, maybe I can help maybe not. There are many more smarter people here then me, maybe someone else can help you out. But as always, ATTACH A FUCKING LOG IF IT DOESN'T WORK FOR YOU.
I do not recommend running this for hours on end. Be smart, don't get banned.
Changelog
This is my first public plugin, I'm not really a C# coder so this is stitched together from various sources. Mainly from GrindZoneChanger and ExVaults QuestBot. Anyone feel free to improve upon this mess.
Upon entering The Dried Lake, combatrange is set to 0 and it's left up to OldGrindBot to explore the area. Once Voll is found, combatrange is increased to 50 and Voll is killed, looted then the bot returns to town to start a new run.
A run takes anywhere from 30s to 3min, depending on how quick Voll is found.
Your character should be tanky and strong enough to survive Dried Lake without dying and killing Voll in a short amount of time. The bot will not engage in combat unless Voll is nearby, you will get hit, you will take damage, you might die - make sure your character can handle it.
This plugin is released as-is. It works for me, it might not work for you. If it doesn't work for you then the source is there for you to make it better.
This Plugin was only tested with the OldRoutine combat routine. It will probably not work with any of the other community routines out there.
Setting things up
Required Plugins:
- EXtensions (comes bundled with Exilebuddy now)
- CommunityLib
Recommended Plugins:
- Alcor75PlayerMover
-- Make sure to check Ignore Mobs in Alcor75PlayerMover settings. Else the bot will dance around Voll like Michael Jackson

- AdvancedItemFilter
Copy VollFarmer-0.0.0.X.zip to 3rdParty
Create an empty 3rdparty-required.txt in the following plugin:
3rdParty\OldRoutine
Start ExileBuddy
Settings > Plugins > VollFarmer > Enable
Settings > Bots > OldGrindBot > GlobalChestsToIgnore > Check All
Settings > Bots > OldGrindBot > TakeCorruptedAreas > Uncheck
Settings > Plugins > Alcor75PlayerMover > Ignore Mobs > Check
Known Issues:
It's a bit spammy, so logs will grow.
There's a log4net error when making portal to town, it is safe to ignore (and I have no clue why this error comes up, if you know, halp pls):
Code:
<log4net.Error>Exception during StringFormat: Index (zero based) must be greater than or equal to zero and less than the size of the argument list. <format>[TakeClosestPortal] The portal to interact with is xxx at {xxx, yyy}.</format><args>{}</args></log4net.Error>
Support
It doesn't work for you? Attach a Log, maybe I can help maybe not. There are many more smarter people here then me, maybe someone else can help you out. But as always, ATTACH A FUCKING LOG IF IT DOESN'T WORK FOR YOU.
I do not recommend running this for hours on end. Be smart, don't get banned.
Changelog
v0.0.1.1
- Fix in timeout where the value wasn't reset.
v0.0.1.0
- Fix to not get lost when moving out of Volls range after looting. You should see the following in the log if it happens:
[VollFarmer] Looks like we moved out of range of Voll. Presume looting is done and start new run.
- Fix in looting timeout, should be a bit tighter now.
- More logging added for now, in case something still goes wrong. Should help debugging things.
- Ran extensive tests with Whirling Blades, Leap Slam and Lightning Warp to make sure moving out of range of Voll after looting gets caught and run gets reset.
- Ran extensive tests with EK, Flicker Strike, Static Strike to make sure things work as planned. I don't have a ranged Char at the moment to test further, but so far things look like they're working as they should.
- Please attach a log if something still goes awry
v0.0.0.7
- Remove depdendency of QuestBot
- Fix GUI, still shows nothing but now it's properly implemented
v0.0.0.6
- Fix where bot would move out of range of Voll after it's been killed and would continue exploring.
v0.0.0.5
- Plugin now has a dynamic looting timeout. Instead of a fixed time to wait it will check if there are items to loot and will only return to town after all items to be looted have been looted. This is still experimental, if it doesn't work right for you please use v0.0.0.4 and post a log.
Thanks to ToNyx and urgent2009 for the help in getting this implemented!
v0.0.0.4
- Small bugfix about restoring CombatRange
v0.0.0.3
- Store and restore previous values for CombatRange so the bot won't be stuck on CombatRange 0 when stopping the plugin
- Fixed the dependency hell and complicated setup.
v0.0.0.2
- Fix to work with StuckDetection/Chicken/AutoLogin
- Increase looting timeout from 5s to 10s
v0.0.0.1
- Initial release
- Fix in timeout where the value wasn't reset.
v0.0.1.0
- Fix to not get lost when moving out of Volls range after looting. You should see the following in the log if it happens:
[VollFarmer] Looks like we moved out of range of Voll. Presume looting is done and start new run.
- Fix in looting timeout, should be a bit tighter now.
- More logging added for now, in case something still goes wrong. Should help debugging things.
- Ran extensive tests with Whirling Blades, Leap Slam and Lightning Warp to make sure moving out of range of Voll after looting gets caught and run gets reset.
- Ran extensive tests with EK, Flicker Strike, Static Strike to make sure things work as planned. I don't have a ranged Char at the moment to test further, but so far things look like they're working as they should.
- Please attach a log if something still goes awry
v0.0.0.7
- Remove depdendency of QuestBot
- Fix GUI, still shows nothing but now it's properly implemented
v0.0.0.6
- Fix where bot would move out of range of Voll after it's been killed and would continue exploring.
v0.0.0.5
- Plugin now has a dynamic looting timeout. Instead of a fixed time to wait it will check if there are items to loot and will only return to town after all items to be looted have been looted. This is still experimental, if it doesn't work right for you please use v0.0.0.4 and post a log.
Thanks to ToNyx and urgent2009 for the help in getting this implemented!
v0.0.0.4
- Small bugfix about restoring CombatRange
v0.0.0.3
- Store and restore previous values for CombatRange so the bot won't be stuck on CombatRange 0 when stopping the plugin
- Fixed the dependency hell and complicated setup.
v0.0.0.2
- Fix to work with StuckDetection/Chicken/AutoLogin
- Increase looting timeout from 5s to 10s
v0.0.0.1
- Initial release
Attachments
Last edited: