My Lovely Planet Migrates Web3 Mechanics to Dedicated Portal in Build 3.3.0

CET and resolved several hours later, with the studio confirming the new environment live on X. For GameFi practitioners, the move is an architectural decision with real implications: it separates the casual match-3 surface from the on-chain rails, forcing a clearer mental model of where value accrues and where the trust boundaries actually sit.

What the portal actually contains

The change, telegraphed earlier in a video from a team member identified as Clément, consolidates the project's Polygon-based mechanics into a single addressable environment. MLC, an ERC-20 utility token, remains the settlement layer — it buys seeds, tickets, bonuses, skins, and NFTs, while holders retain voting rights over NGO payouts from the Environmental Treasury. Lovely Protectors NFTs continue to gate exclusive items and bonus MLC, though the studio has not specified which contract-level integrations migrated versus which stayed embedded in the game client. That distinction matters operationally: if the NFT check now lives server-side in the portal, composability with external marketplaces and third-party indexers improves; if it remains client-side, the separation is largely cosmetic.

Conversely, the treasury mechanics are unchanged. The studio continues to route 85% of in-app purchase revenue and 5% of advertising revenue into open-market MLC buys, and earmarks 15% of global revenue for an environment fund whose payouts are decided by DAO vote. The $100 staking floor that gates the conversion of in-game diamonds into MLC likewise persists, therefore remaining the single friction point any developer building complementary tooling around this economy needs to design around.

What to verify before treating this as infrastructure

Assuming the portal is operationally stable, the practical questions for anyone integrating against MLC or reading Lovely Protectors metadata are narrow. First, confirm whether the portal exposes a distinct RPC endpoint or session token versus the main game, because that determines whether existing API wrappers continue to function. Second, watch for contract address disclosures — the studio has not published a migration manifest, so any tooling that hardcoded the prior integration path will need to be re-pointed once addresses are confirmed. Third, track the next patch notes; build 3.3.0 follows a predictable cadence (3.1.0 on June 9, 3.2.0 in late June, 2.9.1 on April 9), meaning a 3.3.x follow-up with integration specifics is likely within weeks rather than months.

For the broader GameFi stack, My Lovely Planet's split is worth watching as an architecture pattern. Isolating tokenized mechanics behind a dedicated frontend reduces surface area for compliance review and lets the casual client iterate on content — the project cleared 200 new levels and added the Diamonds currency in 2.2.0 and 2.1.0 respectively — without redeploying the value layer. The trade-off, as ever, is interoperability: any feature that lives exclusively inside the portal cannot be exercised by external smart contracts without an explicit interface, which means the next patch notes matter more than this one.