Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.

what do you mean by that so I can do the same![]()
This happens often if your forager is also your master looter. TLDR: looting at the same time that foraging happens can make the undesired item go into inventory before MQ2Forage can execute a delete command.I have used this plugin for a long time and never really had a problem until lately. I completed all the ranks of forage and now the refresh timer is down to like 40 seconds. I thought this would be great. Only downside is for some odd reason it will not always destroy items I forage that are in the ini to destroy. So I end up having to manually delete the chunks of Velium. funny thing is some times this times when I forage and it will delete it on my cursor. So does the timing of the destroy needed modified?
yup, if you have other stuff autoinventorying stuff before forage can get to itThis happens often if your forager is also your master looter. TLDR: looting at the same time that foraging happens can make the undesired item go into inventory before MQ2Forage can execute a delete command.
No longer try and AutoForage while FD or Dead
you can have a .cfg file that unloads the plugin on those specific toons/classesSo after I start using MQ2AutoForage I get a new file now that I can add stuff in order to delete unwanted items correct?
Once I load this plugin, I know if i log out with it running when I log in it will make everyone i log in start foraging. Is there anyways to stop this as I only want certain toons foraging for me and not all 18 that i play
Support per server INI files to reduce the management of multiple per character INI files. If the MQ2Forage_.ini exists it will continue to use that. Otherwise it will create and use MQ2Forage.ini
![]()
Support for per-server INI file. (!409) · Merge Requests · RG Creators / VeryVanilla
Support per server INI files to reduce the management of multiple per character INI files. If the MQ2Forage_.ini exists it will continue to use that. Otherwise it will...gitlab.com
Have you tried reloading it? Have you tried restarting it after you loaded it? Does it say anything?My mq2 autoforage has stopped working on my 99 Ranger, can't figure out how I broke it![]()
did you /stopforage and now need to /startforage?My mq2 autoforage has stopped working on my 99 Ranger, can't figure out how I broke it![]()
That worked, thank you so much!did you /stopforage and now need to /startforage?
Added default [Global] section to INI:
Items will read from or write to a global section, unless a zone-specific line exists.
INI:[Global] Roots=keep
![]()
Add Global option to MQ2AutoForage (!425) · Merge requests · RG Creators / LegacyMQ2 · GitLab
Added default [Global] section to INI: Items will read from or write to a global section, unless a zone-specific line exists.gitlab.com
Love e lyRedbot updated MQ2AutoForage with a new update entry:
Add Global option to MQ2AutoForage
Read the rest of this update entry...
there is currently an eq bug - this is likely what you are seeing.Is it possible to get the buildin autoinventory to work flawless ? Sometimes it keeps the items on the cursor. it especially seems to do this if the client isn't in focus
you probably have your Max. Background FPS set to "min. CPU" which you absolutely do not want to do.this isn't foraging on background windows. the character just keeps standing and sitting until focus is put on that window then it forages fine.
any ideas?

you probably have your Max. Background FPS set to "min. CPU" which you absolutely do not want to do.
eq works on the "fps cycles" and setting to min cpu is basically saying "my background toon isn't going to be doing anything, so basically ignore it".
trying to automate toons in the backgorund but having your eq set to min cpu is going to cause undesired results like skipping instructions, overshooting things when you navigate, generally piss-poor response to things etc.
you can check this in alt-o, for options, then Advanced
For example:
View attachment 31002
I'm still having this same problem. Could Foraging Mastery and Luck be playing a part in why I am keeping things that are supposed to be destroyed?not sure for how long but tried using this a couple days ago to forage and its not writing to any ini's anymore for keep and destroy
Definitely, many items won't accept the command destroy, example is Small Chunk of Velium...single slot items are the devil...
DestroySmallChunk:
action: /destroy
condition: "${Cursor.Name.Equal[Small Chunk of Velium]}"
if it cant parse the command, the plugin isnt running.My auto forage is working fine but only on some characters at some times. It wont work on one toon but will on another. Then at another time it may work on that toon that is wasn't the day before. I was wondering what I may have running or why it wont work on certain toons at certain times. It reads DoCommand couldn't parse startforage. But works on others, Thx much
Appreciate the feedback.In addition to the loot.ini setting you can add a React statement too!
INI:DestroySmallChunk: action: /destroy condition: "${Cursor.Name.Equal[Small Chunk of Velium]}"
