Portals
Create, publish, archive and restore portals, and route domains to them
A portal is one player-facing site with its own game servers, content and commerce. The plan sets how many portals the workspace can run.
Creating a portal
- After the first sign-in, complete Create your portal. For another portal, open Portals and choose New portal.
- Choose the game and enter the Portal name and Subdomain identifier.
The identifier uses lowercase letters, digits and hyphens and becomes
<identifier>.forgeport.net. A Tagline is optional. - Create the portal. Forgeport opens its Launch checklist in the admin portal.
Launch Checklist
Admin → Launch Checklist tracks the gates between a fresh portal and a launched one, with a completion percentage. Each row links to the page where it is completed.
| Gate | Required | Done when |
|---|---|---|
| Portal identity | Yes | The portal has its name and included address |
| Game server connected | Yes | A connector is connected and ready |
| Portal published | Yes | Players see the full portal |
| Payments | Yes | Stripe or at least one alternative gateway is ready |
| Coin packages | Yes | At least one coin package is enabled |
| Custom domain | Optional | A custom domain is active |
The payment and coin package gates appear where player payments are enabled.
Publishing
A Player Portal is Live or Not published. While unpublished, players see the Coming Soon page and its configuration remains unchanged. Use Player portal visibility on the admin dashboard to publish or unpublish it.
Public website
Admin portal → Website builds the public site on the portal domain. It can publish news, featured offers, downloads and server information, plus live rankings, sieges and boss status when the connector supports them. The same website requires the Player Portal to be published first. After that, the two visibility controls are independent, so the website can stay live while the Player Portal shows its Coming Soon page.
The integrated template loads published CMS content and live connector data from Forgeport. The static template keeps the content captured at download time. Self-hosted downloads unlock after the first paid subscription invoice, are licensed to one Portal, and cannot be resold or redistributed.
For a custom frontend, use the public website API to load the same published content and live Lineage 2 data without an API key.
Archiving and restoring
Archive on the portal page removes the portal from your workspace immediately; its content is deleted after 30 days. Until then it appears under Archived on Portals with a Restore button and the days remaining. Restoring returns the portal with the content it had when archived.
Purchases inside the refund window
Archiving keeps the refund route open. Purchases still inside the 14-day refund window are honored: affected players are emailed within an hour with a link to claim a refund, and refunds keep working while the window is open. Restoring the portal within that hour cancels the email.
Domains
Every portal ships with its included subdomain, <identifier>.forgeport.net.
Its switch lives on the portal page and under Domains → Included
subdomains. It can stay active alongside a custom domain.
Adding a custom domain
- On Domains, choose Add domain and enter the hostname, e.g.
play.example.com. The plan sets how many custom domains the workspace can hold. - Add the two DNS records the domain card displays at your DNS provider:
- a TXT record that verifies ownership;
- a CNAME record pointing the hostname at
customers.forgeport.net. This routes the domain to Forgeport and allows Cloudflare to issue SSL. Keep proxying off at your DNS provider.
- The domain shows Provisioning until ownership is verified and the certificate is issued, then becomes active.
- Assign the domain to a portal with its portal selector.
For a root domain, use ALIAS, ANAME, or CNAME flattening. Otherwise, use a
subdomain such as www.
An active domain has a status switch that pauses Forgeport routing while DNS and the certificate stay configured, and a Remove domain action that disconnects it from Forgeport for good.