• Hail, we're RedGuides. We want you to play six (yes, 6!) EverQuest characters at once. We have scripts and a friendly community to help, please join our playstyle and say hello! 👋
  • We've added LLM sections to our Terms & Rules and Resource Rules, for everyone's sanity & in-game safety.
    Read more
    a. Do not replace your voice with an LLM. This goes for your posts and your scripts. Drafting and editing with a tool is fine, but don't take you out of what you share.
    b. Do not replace your EQ character's voice with an LLM. We don't want scripts that speak over /ooc, /shout or other public channels. This has been an unwritten rule that's kept casino scripts off the site for decades, but we're now compelled to make it clear: keep automated communication private.

    Why Does RG Review Scripts?
    Nearly every LLM-written Lua script we see is making your character do impossible things, and rarely in a way that's beneficial to you. We've seen heavy server hammering, /target over impossible distances when /nav spawn would passively accomplish the same thing, a spawn search that fires 20+ times per second, and other pointless actions that are likely annoying GMs.

    You are welcome to use LLMs as a tool to structure, draft, and edit your work, but please read critically before hitting /lua run

Request - MQ2autoforage.ini all set up with goodies :)

janktron

Member
anyone willing to post their mq2autoforage.ini that is setup to keep/destroy all the good/crappy stuff? I just started using it anything would be better than what i got so far :)
 
what part has been a nightmare to setup?

if the item isn't on your destroy list, it gets added to save it
its just a lot of the same world wide common items end up filling my bags with the junk no one really needs, like roots and pods of water. staring with a blank ini i find myself spending a significant amount of time editing keep/destroy
 
Last edited:
@Sic - to turn the above in to a design question: can we configure AutoForage to automatically delete all EXCEPT what is set explicitly to keep? Aka whitelist approach v. blacklist?
 
@Sic - to turn the above in to a design question: can we configure AutoForage to automatically delete all EXCEPT what is set explicitly to keep? Aka whitelist approach v. blacklist?
rather not, new xpac comes out and people wonder why their forage gets destroyed, do a quest and your rare forage is destroyed (e.g druid epic). And you won't know to add them to the whitelist before you have not foraged and destroyed a few.
 
@Sic, @jande, - Wouldn't want it as default behavior by any means, it just solves the design narrative of the OP summarize d as:

"The list of items I value keeping are considerably smaller than the list of all foraged items so it would be quicker to specify what I want vs specify what I don't want and delete the item." This would also allow targeted forage INIs focused on /Baz useful items or /bar useful items. Again, not changing the default or current behavior, just wondering how it would work as a non-default mode.

Implementation would be a config item saying something like:
DefaultToDestroy=False

If set to True:
All items not currently in the INI set as destroy. A user can occasionally go through and select keep or add in their keeps before hand.

If that all makes sense?
 
Request - MQ2autoforage.ini all set up with goodies :)

Users who are viewing this thread

Back
Top
Cart