Skip to main content
No. The release is limited to themes/lucentui, the LucentUIEditor extension, and published theme assets. Supported extension views live under the theme’s vendor override directory.
No. The release ZIP contains a prebuilt public/lucentui bundle. Node.js is needed only when a developer changes the source CSS or JavaScript.
Paymenter uploads extensions but themes are installed in the themes directory. The Editor ZIP is structured for Upload Extension; the theme ZIP contains the lucentui theme root and its prebuilt assets.
Yes. Select Colors → Appearance Mode → Flat UI, then choose Bordered, Filled, or Quiet surfaces. The same content and layout remain in use.
Yes. Set Default Theme to Auto, Light, or Dark and leave Force Theme at Let users choose. Forcing a mode hides the visitor toggle.
LucentUI uses it as the fallback for both light and dark mode. A mode-specific upload overrides a URL for the same mode.
The Editor follows Paymenter’s Allowed Languages list. English is always included as the source/fallback; there is no fixed four-language limit.
File replacement does not intentionally remove settings because they live in Paymenter’s database. Export settings and back up files before every update anyway.
Usually. Generic Paymenter components inherit the theme where possible. Extension markup with custom fixed styling may look different until a dedicated override is added.
The 3.0 release includes theme-side views for Proxmox and the Pterodactyl SSO service surface used by BetterPterodactyl. The extensions remain responsible for server-side provisioning and API behavior.
Follow the troubleshooting checklist, remove sensitive data, then contact the Zaqua community with versions, reproduction steps, logs, and console output.
Last modified on September 10, 2026