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

Add a easier way to access locomotion modules in protoflux #3160

Open
3x1t-5tyl3 opened this issue Nov 4, 2024 · 1 comment
Open

Add a easier way to access locomotion modules in protoflux #3160

3x1t-5tyl3 opened this issue Nov 4, 2024 · 1 comment
Labels
New Feature A new addition, whose complexity hasn't been evaluated yet protoflux

Comments

@3x1t-5tyl3
Copy link

Is your feature request related to a problem? Please describe.

Currently some locomotion modules cannot be renamed or given an easy "way to find them" as the locale format driver messes with it.

While the locomotion modules the world gives are available, that'd mean I'd have to always interject my own modules if I wanna use them; Making it a mess to deal with for me and world creators.

Describe the solution you'd like

A way of directly accessing current locomotion modules
Ergo "Amount of locomotion modules"
and query their corrosponding type; name or other important factors to determine the right module.

It doesn't really matter what or how. But getting access to the currently installed module at "whatever index" would help us be able to loop over them and decide which one to deal with with or not.

Describe alternatives you've considered

Not sure?
This could be something for collections. But I feel like "Get Locomotion Module at Index" is easy enough for us to mess with and get the desired output we want.

Sadly I can't come up with any alternatives other than "wait for collections" or locomotion modules rework.

Additional Context

#3156 #2600 #3158

Requesters

3x1t_5tyl3

@shiftyscales
Copy link
Collaborator

At a quick read this sounds like something that may be implicitly resolved by #57. But as you highlight would likely also have some dependency on #572.

@shiftyscales shiftyscales removed their assignment Nov 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
New Feature A new addition, whose complexity hasn't been evaluated yet protoflux
Projects
None yet
Development

No branches or pull requests

2 participants