• 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
BuffBot2
Why is there a hard coded command - The only hard coded command is list, which lists those commands (keywords) in the SpellExternalKey# variable. The rest of the commands YOU configure in the INI, specifically in the SpellInternalKey# variable.

Why use Spell-ID - I normally don’t write macros using Spell-ID, which is not mandatory, versus Spell-Name but considering I found at least one spell (the druid port to old Cobalt Scar and new Cobalt Scar) worded exactly the same, I added the ability to use Spell-IDs to load the proper spell. If you don’t like using Spell-IDs, take it up with the Everquest developers for allowing duplicate names in their spell name database.

Why disable AFK - The macro disables AFK at startup because the macro uses direct /tells in addition to /say and I prefer to avoid a potential conversational endless loop scenario.
Back
Top
Cart