• 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

Problem - Assisting Issue

Brogin

New member
Ok so I am boxing an Enchanter, Mage, Necromancer. I'm using both the Mage and the Necromancer set with /mac kissassist PetTank and I'm pulling with the Enchanter. The Necromancer targets the incoming mob instantly and works great. But the Mage will not target the mob at all and will just sit there. If while in combat I use the /end and then restart the macro the mage lights up and starts working but the next pull equals the same result. I had on my other computer the same system and both the Mage and Necromancer did exactly what they were supposed to. I have went over my INI file top to bottom and I see no problems. I have even removed the INI file and started a blank one with the same result. I just don't think it has something to do with my INI file. Can someone please help?
 
Did you do a /kisscheck? This type of thing happens when I have a buff or something misspelled.
 
geEQ, Thanks a ton I ran the check although /kisscheck didn't seem to work I used /kissnamechecker and it found a problem. after fixing the issue the macro seems to work great now. Thanks so much for the reply..... now back to work =)
 
Problem - Assisting Issue

Users who are viewing this thread

Back
Top
Cart