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

Update entity movement configuration #398

Open
oh-noey opened this issue Apr 12, 2021 · 0 comments · May be fixed by #705
Open

Update entity movement configuration #398

oh-noey opened this issue Apr 12, 2021 · 0 comments · May be fixed by #705

Comments

@oh-noey
Copy link
Collaborator

oh-noey commented Apr 12, 2021

Is your feature request related to a problem? Please describe.
Server owners frequently are unaware that Movecraft supports non-player entity movement. Furthermore, restrictions of entity movement are currently limited to classifications of players and non players. Ideally, we would have a solution that covers both of these issues.
Describe the solution you'd like
onlyMovePlayers should be deprecated in favor of an moveEntities list, of which can be populated by entities by their entity type enum. It would also be preferable to have a system to provide less verbose configuration, and thus the class hierarchy may be taken into consideration. For example, it would be preferable to have a method for allowing only non-hostile entities, or all mobs of a specific type (i.e. spiders, zombies, skeletons). It may be necessary to generate a graphic for the sake of configuration for those unfamiliar with the Spigot API and its entity type hierarchy.

@oh-noey oh-noey added this to the Movecraft 8.0 milestone Apr 12, 2021
@oh-noey oh-noey removed the 8.x label May 30, 2021
@TylerS1066 TylerS1066 moved this to New in Issue Triage Mar 23, 2022
@TylerS1066 TylerS1066 moved this from New to Ready for Work in Issue Triage Mar 23, 2022
@Intybyte Intybyte linked a pull request Aug 26, 2024 that will close this issue
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Ready for Work
Development

Successfully merging a pull request may close this issue.

1 participant