Game Ideas

Add a way to prevent a character simple from being ragdolled on death

If possible, moving the LookAt function to the BasePawn would allow it to be used on a CharacterSimple

This would avoid creating anim BP functions just to change one property

add API control to hide any character or entity for a certain player ,network blocking, disabling collisions and all logic automatically. My main motivation to get this feature is : Recreate my ESP based anticheat ( VigilantEYE ) that I created on garrys mod But there are other use cases : Bandwidth/Rendering cut: don’t send/render junk entities a client doesn’t need. Stealth/cloak mechanics: server-enforced invisibility. Scripted events: hide entities during cutscenes or triggers.

On the server we can play an animation with https://docs.nanos-world.com/docs/scripting-reference/classes/character-simple#function-playanimation However, there is no event telling us when this animation has ended. This would be great to have an event telling us when the animation has finished.

Exposing GetEntityMatrix and SetEntityMatrix would give developers much more control over entities. Instead of being limited to location, rotation, or scale separately, we could read and override the full transformation matrix.

Add a way to attach client-side entities to the player's camera, keeping them fixed in screen space for things like HUD elements

For example, passing nanos-world::SM_Cube to :CallBlueprintEvent would convert it into an object soft reference

That would be great to have a new event for detecting when collision occurs between Actors. As discussed something like this: myEntity:Subscribe("Collision", function(ortherEntity, ...) end) You mentioned it might be problematic if its enabled by default on everything so we suggested the event should be opt-int with something like entity:EnableCollisionEvent()

I'm suggesting 2 ways of doing it: Adding a new method :SetFogColor to set the color of the fog by passing a Color type value as 1st parameter. Edit :SetFog method to add a second parameter to set the color of the fog (still Color type) but optional. In my opinion, first one is better because you actually know what the method is doing, and it match with another method named SetVolumetricCloudColor.