Client-Editor Memorium Release

06/04/2026 19:13 Slin-#1
We are releasing a free version of our tool. Initially, this tool was not intended for the public. However, we have decided to release the client modding section. We believe that such tools benefit the community as a whole and simplify client handling.

Another reason for sharing this project is the open nature of many community resources. Projects such as OnexExplorer and other publicly available tools have helped make client modding more accessible.

We will continue to provide updates and optimize various aspects within this free version.



How to Get Started

Requirements
  • Docker Desktop
  • Node.js version 22.22.3 or any version 22 or newer (recommended because the tool features auto provisioning and will automatically download and cache the exact V8 bytecode compatible version it needs on first run. You do not need to manually switch patch versions.)

Installation

After installing Docker and Node.js, we recommend creating a dedicated folder. Alternatively, you can install or update the tool globally using the -g flag.

Navigate to your desired installation path and run

Code:
npm install memorium-editor-cli
Or for a global installation

Code:
npm install -g memorium-editor-cli@latest
Once the installation is complete, you can launch the tool by running

Code:
memorium-editor
or

Code:
mem-e
If you encounter any errors during this process, the terminal should provide the appropriate solution for your specific case. If the issue persists, feel free to report it here or join our Discord server.



Preview


Core Functionality and Configuration

Very Important Note

It is strongly recommended not to host this project directly on a live or public server. The tool is built exclusively for local use.

The tool is fully automated and creates all necessary structures for you except for the required configuration folders for the source and client files.

Important Note

Currently, the tool reads the .dat and .txt language files directly from the source and not from the .nos archives. This is because the tool was originally designed as an automated web interface that could restart the server after changes for instant testing. Full integration for reading and writing directly from .nos archives will be added in a future update.

Please keep in mind that while other configuration options such as server files are visible, they are strictly limited and not fully functional in this free version.



Current State and Support

Please do not expect a polished release or a complete feature set. There are still several areas under development. While the core functionality is fully verified and tested, some bugs and unfinished elements remain.

Feel free to submit bug reports on our Discord server. Please note that we do not offer instant updates or direct support. The main features should be self explanatory.

Discord Link

[Only registered and activated users can see links. Click Here To Register...]

credits to @~Teiko~
06/14/2026 22:03 G-ameBoy#2
Wtf? No VirusTotal scan, no source, repo link is 404, and the npm package ships obfuscated V8 bytecode + native binaries + a Windows exe.
07/30/2026 13:14 Slin-#3
Quote:
Originally Posted by G-ameBoy View Post
Wtf? No VirusTotal scan, no source, repo link is 404, and the npm package ships obfuscated V8 bytecode + native binaries + a Windows exe.

You’re right about the missing VirusTotal scan and broken repository link

The project is not open source, and the free edition is built from the same private codebase as the full version. The V8 bytecode is intentional. The native Rust module handles .NOS archives, while the Windows executable is the CLI launcher. Naturally, nobody is required to install or use it if they are uncomfortable with closed-source binaries.