A player portal and donation store for Lineage 2.
Launch a branded Lineage 2 website and web panel where players buy coins, spend them in your store and receive purchases in the game. Works with L2J sources and with L2Off/PTS retail binaries, each through its own connector.
- L2J sources
- L2Off / PTS binaries
- Delivery through a connector
One platform for the whole server web presence.
Everything runs from one owner console, on your own domain and branding.
Public website
Publish a themed Lineage 2 website with news, offers and live game data, or export the template for self-hosting.
Player portal
Players register a master account, link their game accounts and manage characters, orders and rewards.
Store and wallet
Players buy Portal Coins through your payment account and spend them on items, skills and bundles.
Vote rewards
Votes on the top-lists are verified by provider API or signed callback before any reward is credited.
How vote verification worksCharacter tools
Offer rename, gender change and unstuck as paid services where the connected server supports them.
Owner console
Manage catalog, orders, players, providers and analytics for every portal from one workspace.
The public website, included.
A real page from the built-in Lineage 2 template, published on the owner's domain.

The template ships with the platform and can also be exported for self-hosting under the template license.
Two server families, two connectors.
Lineage 2 packs split into sources you compile and retail binaries you configure. Forgeport treats them differently because they are different.
L2J sources
Connector core inside the game server
A connector core JAR runs inside your game server process and connects outbound over WSS. You implement a small GameBridge class against your exact revision, so the code touching the game world is code you compiled.
- Complete aCis 409 and Mobius CT_2.6 High Five examples to adapt
- Delivery reaches the live player object, with a replay-safe grant journal
- Java 17 or newer, no inbound ports
L2Off / PTS binaries
Standalone connector beside the server
Retail binaries have no source to compile into, so the connector runs as its own process, configured through one portal.toml file. Purchases are queued in a documented delivery table that your extender polls and applies in-game.
- No code injected into the game binaries
- Public delivery-queue contract with replay protection
- Node 22 on the host, outbound WSS only
What happens when a player buys.
- The player buys Portal CoinsPayment goes through your own connected payment account. Forgeport takes 0% of the sale.
- The player picks an item, skill or serviceFrom the store you configured, priced in coins, with purchase limits you control.
- Forgeport creates a delivery commandEach grant has a stable command id, so a retried delivery can recognize itself.
- The connector applies or queues itOn L2J the bridge grants to the live player object. On L2Off/PTS the command waits in the queue until your extender applies it in-game.
- Forgeport records the resultOrders show queued, delivered or refused states, so support questions have an answer.
Not a typical Lineage 2 donation panel.
Read the integration before you trust it.
Flat pricing, 30-day trial.
No card required to start, and no commission on player sales on any plan.
One portal and game server.
Up to 3 portals, 3 game servers each.