PtokaX NMDC Hub Software

PtokaX is an NMDC hub server for Direct Connect networks. A compatible DC++ client connects to the hub to see users, chat, run searches, and receive hub messages. The hub does not carry the actual peer-to-peer file transfer, so a healthy hub does not prove that one user can upload or download from another peer.

PtokaX is not an ADC or ADCS server, and it is not a DC++ client. Choose it when the users, scripts, and integrations you operate require classic NMDC behavior.

PtokaX History And Scope

PtokaX has a long-running place in the classic NMDC hub community. Its public project area links the project website, downloads, wiki, and forum. An independent project index records a GPL-3.0-only listing and the upstream Subversion source location. Published 0.5.x material and older forum discussions are useful release records, but they do not prove that a script or configuration sample matches your installed build.

Keep the protocol boundary clear. NMDC is a text protocol for client-hub and client-client communication. PtokaX coordinates the hub side of that network. A client still needs its own active or passive connectivity and usable transfer slots for peer transfers to succeed.

Operating A PtokaX Hub

1. Download the release from the project source, record its version, and keep the original archive and any published checksum with the deployment record.
2. Run the hub under a dedicated operating-system account. Keep the executable, configuration, logs, and Lua scripts in locations owned by that account, not in a shared desktop folder.
3. Open only the listener ports that the configured hub uses. Test login, chat, search, registration, and a real client-to-client transfer from the network path users will take.
4. Back up configuration and script data before a version change. Test an upgrade or script change on a disposable hub first, then keep the previous working release available for rollback.

The exact startup files and settings vary across PtokaX releases and operating-system builds. Read the documentation shipped with the selected release before copying an older forum example into a public hub.

Administration And Lua Scripts

PtokaX has a large Lua-script ecosystem. Scripts can change moderation, registration, chat behavior, statistics, and database access. Treat a script as executable server-side code, not as a theme file. Review its source, author, required Lua API, required libraries, stored data, and failure behavior before loading it.

• Use !help on the installed hub to inspect the command set available to the logged-in administrator. Do not assume that a command from another PtokaX release exists or has the same arguments.
• Test one script change at a time. Keep a copy of the prior script and configuration, then verify login, main chat, private messages, registrations, bans, and restart behavior.
• Do not paste passwords, database credentials, or private user records into chat commands, forum posts, or script logs.
• When a script fails, save the full error, PtokaX release, Lua version, script revision, triggering action, and the smallest reproducible configuration before asking for help.

Security And Troubleshooting For NMDC

The NMDC protocol reference documents $MyPass as plain-text protocol data. Do not treat an NMDC administrator login as encrypted merely because a password is configured. Restrict administrator accounts, limit access to trusted operators, protect logs and backups, and rotate a credential that has appeared in a transcript or support request.

If a hub fails to start, first confirm the exact release, operating system, listener port, and log path. If clients can connect but transfers fail, separate hub login and search from active/passive client connectivity, NAT, firewall, slot, and peer-transfer problems. If the project website or wiki is unavailable, use the official forum to identify the intended resource. Do not replace an unavailable project download with an unverified binary mirror.

Verified PtokaX Resources

These resources are classified by ownership and purpose. Project endpoints and legacy community material can change availability, so verify the release and compatibility before using a download, script, or administration tool in production.

Historical project metadata records the upstream checkout as svn://www.ptokax.org/PtokaX. It is a Subversion source location, not a browser URL. Use an SVN client only after confirming the destination and release branch you intend to inspect.

Related Direct Connect Reading

Use Direct Connect for protocol and client context, Verlihub and uHub when comparing other hub-server families, Articles for the wider article library, and Hubs to inspect public hub records.