Eximius Direct Connect Hub Software

Eximius is a proprietary Windows NMDC hub server whose name remains visible in current public hublist statistics. Surviving historical comparisons describe it as a graphical Windows application using C# and Lua, with project activity around 2007. The former project website is no longer a verified current source.

DCHUBLIST marks Eximius as an outdated software family and currently observes hubs reporting versions 3.0.2 and 3.0.5. No current project-controlled repository, release archive, manual, or support channel has been verified for those builds.

The article therefore documents the public evidence without inventing a developer, data format, release timeline, or support service. A surviving Eximius installation must be identified from its own files and runtime state.

Overview And Status

Historical Record

Historical Direct Connect software tables list Eximius as a Windows-only NMDC hub with a graphical interface. They classify it as proprietary freeware and associate the implementation with C# and Lua. Those details come from secondary comparison records rather than a surviving project-controlled manual.

The former project address en.rs2soft.nl appears in older references, but it is not a current verified support or download site. Do not link users to an unrelated replacement page or mirror simply because it reuses the domain or software name.

Version Evidence

DCHUBLIST currently groups two public hubs under Eximius and reports versions 3.0.2 and 3.0.5. These values show that deployments using the name remain online. They do not establish when those versions were released or whether the binaries are unchanged originals.

A long-running hub can preserve an executable after the public project disappears. It may also include private patches, Lua scripts, modified configuration, or a custom software string. Each installation must be documented independently.

Source And License

The available historical records classify Eximius as proprietary freeware rather than open source. No verified public source archive has been located. That limits the ability to audit, rebuild, or patch the server when operating-system or network behavior changes.

Freeware distribution does not grant permission to redistribute modified binaries or abandon original license conditions. Preserve any license, README, installer text, and attribution included with the existing package.

Current Status

Eximius should be treated as historical software with surviving deployments and no verified active upstream project. It may still function in a controlled environment, but it is not a suitable default choice for a new internet-facing hub.

Operation And Recovery

Identify The Package

Record the executable name, file version, product version, digital signature, installation path, startup method, and hash. Capture the version shown in the graphical interface and compare it with the value sent to clients and hublists.

Search the installation for README files, license text, changelogs, Lua scripts, configuration, account data, and logs. Do not assume that one file contains all state simply because the program has a graphical interface.

Isolate The Server

Clone the installation into a Windows virtual machine before testing it. Keep the listener private, block unnecessary outbound traffic, and use test credentials. Monitor which files and registry locations change during startup, configuration updates, and user registration.

If the server depends on an obsolete .NET runtime, install that runtime only inside the isolated environment. Do not weaken the security configuration of a current workstation to accommodate the old application.

Scripts And Local Modifications

Inventory every Lua script and identify which commands, moderation rules, bots, or persistence features it implements. Disable one extension at a time when diagnosing a failure. Preserve the original script set before changing interpreter or API behavior.

A support request must distinguish the Eximius core from a local script. Include the exact version, Windows release, runtime, failing command, relevant log, and whether the problem remains with optional scripts disabled.

Migration

Export registrations, permissions, bans, redirects, hub text, and script-owned data while the original server still runs. If the storage format is undocumented, create a read-only copy and document each conversion step.

Recreate the hub on maintained software using test accounts before switching the public address. Keep the old environment offline until account counts, roles, bans, encoding, and operator workflows have been compared.

Verified Resources

The resources below are historical or observational. No current project-controlled Eximius repository or download site has been verified.

Related Direct Connect Reading

YnHub, UfoHub, and SDCH document other historical Windows hub-server environments. Their surviving evidence differs, so do not copy installation or migration assumptions from one product to another.

Support provides the support-request format for an unidentified or privately modified legacy build. Include hashes, screenshots, runtime information, and a complete local file inventory.