Znote is a common search name for Znote AAC. This route preserves that exact terminology while documenting the same project lineage, verified dates, source record, and compatibility context under its canonical product name.

A surviving OTLand support thread shows Znote AAC in active use on February 3, 2013. The current GitHub repository was created on August 28, 2013. Because an exact first-release announcement was not verified, this page uses February 2013 as the earliest confirmed community-use date rather than claiming a more precise launch.

The upstream project defines Znote AAC as a full website used with an Open Tibia server, emphasizing easy installation and compatibility with popular distributions. Its public repository and wiki became the durable reference point for installation, schema conversion, configuration, and features.

Evidence classification: Forum and repository-backed. The date shown in the reference box is phrased to match what the surviving source actually proves.

Znote AAC arrived after years of tightly forked account makers and pursued broader distribution compatibility. Its configuration layer recognizes several TFS and OTHire families, while helper scripts and a special conversion area support adapting existing databases.

Over time, the expected AAC surface expanded from account creation into two-factor authentication, account recovery, support tickets, server configuration displays, kill and death feeds, item lists, houses, guilds, character profiles, and custom vocation or town support.

Owners use Znote AAC to provide registration, login, account management, character creation, downloads, server information, online data, highscores, guilds, houses, news, and community-facing game records.

The project can parse server configuration and data such as config.lua, stages.xml, and items.xml to present rates, PvP settings, experience stages, and item information. This makes the site a view onto both the SQL database and the server's file configuration.

Operational setup includes selecting the correct server engine, importing or converting the database schema, configuring mail when verification or recovery is enabled, securing the web server, and testing every write path against a non-production database.

Znote AAC is notable for documenting a broad compatibility promise in the README instead of existing as one unnamed server fork. That made it easier for new owners to identify a supported engine and follow a repeatable installation path.

Its feature list demonstrates how AACs became community platforms rather than simple account forms. Two-factor authentication, tickets, dynamic server settings, and detailed character or guild pages moved the website closer to a full service layer.

Check the repository branch, commit age, PHP and database requirements, selected ServerEngine value, schema converter, mail library, and open security issues. README requirements can lag behind current hosting platforms, so verify them in staging.

Use HTTPS, modern password storage supported by the target engine, least-privilege database credentials, protected configuration, rate limits, CSRF defenses, and tested backups. Remove installation or conversion surfaces that are not needed after setup.

This page separates a confirmed public date from an assumed development date. Its release statement is: Earliest verified community use: February 3, 2013.

The recorded lineage is Created and maintained as an independent PHP AAC. The source links preserve the repository, release page, official documentation, publisher archive, or contemporary discussion used to support that description.

Project activity, compatibility, and security can change. Readers should use the linked upstream repository or official documentation to confirm current support before adopting the resource.