Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

utility scripts? #81

Open
Shadowblitz16 opened this issue Aug 9, 2020 · 2 comments
Open

utility scripts? #81

Shadowblitz16 opened this issue Aug 9, 2020 · 2 comments

Comments

@Shadowblitz16
Copy link

Shadowblitz16 commented Aug 9, 2020

can we have utility scripts for the following?

  • 2d drawing
  • 3d drawing
  • 2d physics movement and collision
  • 3d physics movement and collision
  • pathfinding
  • generation
  • input and input binding
  • gui

the idea of this suggestion is that we can use a ecs workflow and implement our own nodes

@willnationsdev
Copy link
Member

I would probably just wait for Andrea Catania to finish his fully-fledged ECS module and then use those scripts for this.

Also, for all rendering, collision, and (in 4.0) navigation, you can already use Servers for standalone operations.

generation is too custom, so people will need their own functions for those.

what kinds of utility methods are you thinking of for input and input binding / gui? Those seem like they could be useful.

@Shadowblitz16
Copy link
Author

Shadowblitz16 commented Dec 21, 2020

input would be like the default one but would support raw controller input and binding action like mouse movement

gui would be something like a intermediate gui implementing of godot's ui

also the rendering and collision isn't really clean on how to use I was thinking something simple like..
draw_shape(pen or brush or both, args)
collide_and_move(shape, args) <- works outside of physics nodes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants