Module packages

Vortexus is split into two PHP packages (Paymenter extensions). Each has a clear job. You usually enable both if you sell game servers end to end.

Vortexus Marketplace (`Others`)

Path in your project: extensions/Others/VortexusMarketplace/

Role:

Marketplace front and admin tools (categories, templates, regions, images).
Hooks that link orders and billing to server creation.
Flows that keep your catalog aligned with what customers can buy.

Think of it as the shop and the rules that turn a sale into a server request.

Vortexus Web (`Servers`)

Path in your project: extensions/Servers/VortexusWeb/

Role:

Embeds the customer-facing server panel inside Paymenter (console, files, databases, backups, etc., depending on Pterodactyl support).
Bridges Paymenter users to the right Pterodactyl server context.

Think of it as the control room after the server exists.

Folder names Others and Servers are standard Paymenter extension groups — not random vendor folders. If an extension is in the wrong group path, Paymenter may not list it.

Enable in admin

Paymenter Admin → Extensions
Under Others, enable Vortexus Marketplace.
Under Servers, enable Vortexus Web.

After copying files, if something does not appear:


composer dump-autoload

(from your Paymenter project root)

How to know it is installed

Both extensions show as enabled in admin.
Marketplace UI loads (routes depend on your configuration).
A service using Vortexus Web opens the embedded panel for an existing server.

Next step

Read Usage for the day-to-day workflow: categories, templates, pricing, deploy, and troubleshooting.