Game Ideas

This would significantly reduce performance overhead for rendering multiple instances of the same mesh Constructor: local eInstancedStaticMesh = InstancedStaticMesh(location, rotation, mesh, start_cull, end_cull) API: InstancedStaticMesh:SetMesh(sMeshAsset) InstancedStaticMesh:SetCullDistances(nStartCull, nEndCull) local iInstanceIndex = InstancedStaticMesh:AddInstance(tTransform, bWorldSpace?) InstancedStaticMesh:RemoveInstance(iInstanceIndex) local iInstanceCount = InstancedStaticMesh:GetInstanceCount() InstancedStaticMesh:UpdateInstanceTransform(iInstanceIndex, tTransform, bWorldSpace?) local tTransform = InstancedStaticMesh:GetInstanceTransform(iInstanceIndex) A useful addition could be a function that batches instance updates and sends the remote event only once, rather than on every single update

Currently, we can retrieve an entity's network ID, but there's no built-in way to find an entity using that ID It would be useful to have a function for this purpose, ideally it would make sense to have it as a Base Entity static function, but since that's a protected base class it's unclear what the best alternative would be from an API design perspective

API Design: ("OnLanded", function( tHitResult ) end) ("OnMovementModeChanged", function( iPrevMovementMode, iNewMovementMode ) end) ("OnJumped", function() end) ("OnStartCrouch", function() end) ("OnEndCrouch", function() end)

It would be great to listen to visibility changes on WebUI objects design: ```lua my_webui:Subscribe("VisibilityChange", function(self, iOld, iNew) end) ```

Add a launch option to directly join a server after starting the client ("+connect" for instance?)

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.

Client.OpenURL(url) Open an URL on the default browser of the Client

It would be nice to be able to control the cull distance of an individual entity, and prevent an actor from rendering when it's too far away from the camera API design: my_actor:SetCullDistance(min_dist?, max_dist?)

This would be really useful for game-modes with different chat channels (like admin-only etc.) API Design: Player:SetChatChannel(channel) local ret = Player:GetChatChannel() Player[/Chat]:Subscribe("ChannelChange") Chat.BroadcastMessage(message, channel?)