• 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 - Documenting Lua scripts

Redbot

💻❤️
Moderator
Commits
580
We're making a template for Lua script documentation. Aside from the obvious (commands, description, etc.) What would you like to see the template include?
  • Requires?
  • Modules?
  • Lua version?
As an example for plugins, we have:
  • User config file
  • TLO(s)
  • DataType(s)
 
Lua Version would always be the same, you don’t have multiple choice. Dependencies probably matters, and possibly dependency versions, but versioning is a pain to maintain for as little as most authors would change their API.

Binds matter.
 
Request - Documenting Lua scripts

Users who are viewing this thread

Back
Top
Cart