Glovium Modules are drop-in blocks you bolt onto any Rayfield-based project. Request a key, pull a module, and it lands right inside your existing UI. No rewrites, no boilerplate, no visual drift.
Modules speak Rayfield natively. They inherit your window, theme, and layout instead of spawning a second UI on top of yours.
Each script gets its own key. The endpoint stays stable, and your integration keeps working even as modules grow behind it.
A single request and a single loadstring. No vendored files, no repo to clone, nothing to keep in sync.
Each module does one job. Pull in what you need, leave the rest. No monolith, no dead weight shipped alongside it.
Send a short note to invokexpression@duck.com describing your script and where the module would sit inside it. Keys are issued per script, not per person.
You'll get a reply with a bearer key that identifies your integration. Treat it like a password, since it's tied to your project, not your machine.
Paste the block below into your script, swap MODULE_KEY for the key you received, and the module runs inside your Rayfield window.
rayfieldWindow must exist before the module runs, since modules attach to it rather than creating their own window.
Set RequestedModule to the module name you want (for example "autofarm") before calling the loadstring.