Review the products, share your files structure and clarify a compatible delivery scope before approval.
Filter by category, read the product details and check compatibility with your files before requesting delivery.
The system's primary purpose is to seal a character from its current account, making it...
Hunting mission system with resume support, job rewards, EXP_PERCENT and mission list...
For Metin2 systems, server files customization and launcher tools, we define the delivery scope before work begins.
Offline shop, security panel, missions, boss tracker and custom in-game interfaces.
Files adjustment and clean installation for oldschool, medium progression or PvP structures.
Patcher, manifest, pack management, web panel and admin-side helper solutions.
First, your files and source structure are reviewed. Adaptation, testing and delivery follow after compatibility is clear.
Source, client and DB structure are reviewed.
Required source, client and SQL changes are adapted to the existing structure.
Patch, SQL and pack files are applied in the planned order.
It is tested in-game and delivery notes are provided.
A Metin2 system depends on the server source, client source, Python interface, SQL structure and version in use. Before quoting, we review your current structure and clearly define the files included in delivery.
On CortexLoad you can review offline shop, security panel, hunting missions, launchers, server files and custom development. We use a quote conversation instead of instant checkout to avoid incompatible deliveries.
Browse Metin2 SystemsDuring the quote, we review your files version, source structure and client setup. Required adaptations are added to the delivery scope.
Each system has a different scope. The product page gives the base delivery details, and the final file list is confirmed during the conversation.
After approval, the system is assigned to your account. Delivery files, setup notes and updates are available from My Systems.
Support scope is defined during the quote. Adaptations and required test steps are documented in the delivery notes.
Share your files version, source structure and requested system. We will define the delivery scope and required adaptations during the conversation.