Game Ideas

I think it would be nice to be able to call asynchronous events. For example, a client wants to request information from the server, and act on that data immediately. Something like this. Events.CallRemoteAsync('getLeaderboard', function (data) Console.Log(NanosTable.Dump(data) end end Which on the server would look like: Events.RegisterRemoteAsync('getLeaderboard', player, function () -- Do some logic to get the leaderboard data return data end end This would eliminate the need for every client file to subscribe to a remote event and THEN process the data, and would instead just require them to call the remote event async (while inside of a function for example), and get the response back and process it immediately.

From TomDotBat issue: https://github.com/nanos-world/issues/issues/446 Some developers and server owners have a lot going on in their game which results in major slowdowns. This can be worked around by allowing developers to balance the load on several threads. Expose methods to the scripting environment that allow developers to use multiple threads. This could be achieved with an existing Lua threading library such as: Lanes or Effil. Several adjustments will need to be made to ensure threads are destroyed when a player leaves a game, it also shouldn't be possible to spawn an extreme amount of threads and potentially cause harm to a player's computer. Looking back at how servers on garry's mod perform, they all suffered when too much was going on. Obviously the simple solution is to remove content, but you're losing gameplay features in that case.

It would be nice to have an option in the server config to prevent using CEF dev tools

Having a way to add new meshes to a Melee entity (not attached to the melee, but to the character) would be convenient. This would allow to have one melee in each hand, akimbo style, and more cool stuff! About the API design I'm not sure what could be the best: Having a new method that you'd call on a Melee instance Making a Character being able to carry multiple Melee (sounds a bit messy regarding how Pickables are handled)

A function that return every light spawned by the map To turn off / on some light

In my opinion It is preferable for readability to separate the widgets to a dedicated category

I think it would be useful if there was a way you could pass simple data (like strings and etc) between servers when using player:connect() to redirect a user to another server. As an example, something like my_player:Connect(server,?password,param1,param2) Then on the other server Server:Subscribe("PlayerConnecting", function(IP,...,...,param2, param2) A use case for this could be a multi-server setup where you want the same character ID to be referenced across multiple servers. Instead of making the user select their character all over again on reconnect, the characters ID could be passed through and then they would be able to lookup that character and load it for the player automatically.

A new (optionnal) parameter that would allow to add an offset to the location where the force will be applied on the entity. API design: my_actor:AddImpulse(force[, velocity_change, offset_location]) offset_location default value: Vector(0,0,0)

Console variables can be perfectly emulated with a console command that changes the value of a global variable read by various functions. However, a command variable: adds the convenience of other modders knowing exactly how to get its value (going for the cvar name and not for some random Lua variable in the code); lessens the chance of name conflicts in the global Lua environment (since all these indentifications are abstracted by the API) (Modders tend to be much more careful with cvar names than with internal variables btw); and ensures that configurable values are exposed for all addons (which I'm sure will be a problem for nanos due to the way addons work - requiring Package.Export). Preview: AddConVar( "hi", "1") -- Accepts strings and numbers local cachedCvar = GetConVar("hi") print(cachedCvar:GetString()) An old implementation I made: https://github.com/Xalalau/liblau/blob/master/Shared/libs/sub/CVar.lua

Be able to create our own buttons like this in the discord status system