Game Ideas

Allow the possibility to download the server content via a CDN or anorther server than the one hosting the game. (or atleast the Assets).

I propose the addition of a feature that allows developers to execute JavaScript via a package, enabling seamless communication between the game server and external applications like Discord bots. Here are the key points of the idea: -- 1 > Execute JavaScript Through a Server-Side Package: Allow developers to set up a JavaScript server or integrate with Node.js to execute custom scripts directly. This would open up possibilities for creating powerful tools, automation, and integrations. 2 > Communication Between the Game Server and External Applications: Introduce a way to send and receive data between the game server and external applications, similar to how front-end web applications communicate with APIs. For example, developers could send data about players or the game state to a Discord bot. 3 > Discord Bot Integration: Provide tools or APIs that enable the creation of Discord bots directly linked to the game server. This would allow commands like /userinfo <id> to return detailed player information such as their name, role, money, job, or other server-specific data. This could be particularly useful for roleplay servers where managing detailed player data is key. -- This feature would greatly enhance the server-side development ecosystem, enabling advanced integrations and automations that bridge in-game interactions with external platforms.

GUI concept for dedicated server. Also settings has GUI. Add there packages, assets (store). In general, there will be 2 options, like a console and an interface.

Return false in LogEntry event to prevent the message from appearing. Also prevents from saving in the log file ? Nanos world has some errors and warnings that we don’t want. Would be nice to be able to hide the intended ones. This seems a bit dangerous so maybe you can keep saving the log in the log file but not showing it in console idk.

Support IPV6 only for client / Server

For assets and packages Use hashing table where the path is the key to know if you already checked a file. Would be nice to avoid conflicts when starting multiple servers and to make the validator safer.

For now when someone joins a server, he need to download and install every assets that the server has and that can lead to huge wait times (especially 🥔 internet). One of the solution is to download and install Assets in-game and only the map assets will be downloaded before joining. This idea can be the following : The user on the options will have 3 ways to download and install assets : 1: Classic: Download and install all assets before joining the server. The user wait on the loading screen 2: In-Game: Download and install some assets in-game, the user only waits on the loading screen for the most importants assets like map and some assets that has been defined on the config file as major. 3: Dynamic: Like the method 2 In-game but smarter. Instead of queuing each downlads in game, it will only queue downloads/installs of assets that are near the player. Since there will be huge maps, some kind of assets will likely be at the other side of the map and the user might not access this part soon or even at all during his playtime. For theses methods upper, all the assets will still be referenced on the server like before, only the way of loading it can change. It can also be great to add dynamically new assets to the server without restarting it but i think it will lead to some major work. That's why the 3 ways of downloading assets to the user listed above will likely have more good impact to the user experience than this.

Sending assets would be much faster if zipped & compressed. You will still be able to send unpacked assets but it would be much slower. For example, right now my map is 2.5GB unpacked but when it's packed, it's only 1.3GB.

For the Client/Server Console. If the exact same message is displayed just put a X2, X3, X4 depending on the number of times it was printed, to avoid flooding the console (Problem is that you need to change how stuff is logged in the log file, maybe wait for the next message to log the old one in the log file)

The use case is very edge, as in title split main executable into dll and launcher. All what Launcher.exe would do is to load NanosWorldServer.dll and run some "Start" export function. That way it become possible to embed server into anything what can run .dll, example use cases: someone can make a graphical wrapper around server to add graphical user interface - you can get exports from lua modules, if module start it may set lua callback to custom buttons Wrap server with c# and use c# as an main scripting language serverside - thats the main motivation for this refactor. Also, i assume it will not take a long time to do this