Chronicles and protocols

Check project compatibility before purchase

Strix-Guard is issued for a selected Lineage II client or chronicle. This page explains which builds are available for purchase, which details are required for the license, and what to do with a custom client.

Supported builds

The list below comes from the website catalog and is used in the purchase form. The buyer selects one available option before creating an invoice.

Scions of Destiny Protocols: 656, 658
Interlude Protocols: 744, 746
Gracia Part 1 Protocols: 83, 87, 146, 148, 152
Freya Protocols: 216
High Five Protocols: 253, 267, 268, 271, 273
Glory Days Protocols: 488
Lindvior Protocols: 531, 532
Ertheia / Dimensional Strangers Protocols: 606, 610
Infinite Odyssey: Underground / Hymn of the Soul Protocols: 28
Helios: Lord of Bifrost Protocols: 64
Grand Crusade Protocols: 109, 110
Salvation: First Chapter Protocols: 140, 152
Fafurion NA RU Protocols: 166, 196, 228, 235
Shadow of the Kamael / Prelude Of War Protocols: 245, 272, 286, 306, 311, 338
Vanguard / Master Class Ch. 2 / RE:MEMBER Protocols: 362
Hore's Tome / Master Class Ch. 3 Protocols: 388

Required details

  • a supported chronicle or client from the list;
  • a public domain or public IP address of the login/auth server;
  • correct project technical parameters if the purchase form requires them;
  • the buyer account that will own the license;
  • a working email for notifications and support requests.

Not accepted

  • localhost, 127.0.0.1, private, local, or reserved addresses;
  • public DNS resolver addresses instead of the project address;
  • URLs with http://, https://, paths, ports, or extra parameters;
  • builds that are not listed in the purchase form without prior checking;
  • third-party project details when the license is not being issued for that project.

How the check works

The check helps create the license for the correct client and the correct project address.

Client selection

The user selects a chronicle or client from the available list. Name and protocol are shown before payment.

Address validation

The form accepts only a public domain or public IP address and rejects local, private, and reserved addresses.

Parameter locking

Selected details are stored in the order so the license is issued with the same parameters after payment.

File access

After payment confirmation, files are available in the license owner customer account.

If the required build is not listed

Do not create an invoice for an unsuitable chronicle. Send a request through the contact form and include the chronicle name, client protocol, and a short project description. We will reply whether an existing option can be selected or a compatible build needs to be added first.