-
-
Notifications
You must be signed in to change notification settings - Fork 18
Open
Labels
status: ☑️ acceptedThis issue or pull request is accepted as validThis issue or pull request is accepted as validtype: pack parityFeature to close functionality gap between this plugin and a datapack. Given higher priorityFeature to close functionality gap between this plugin and a datapack. Given higher prioritytype: 🎯 featureNew feature or requestNew feature or request
Description
Is your feature request related to a problem?
When having multiple graves, only the last and only the very last grave can be located via the locate command.
Describe the solution you'd like
I’d like to have one of the two possible solutions (maybe there are more/better ones, but these are the ones I’d implement):
- After collecting your last grave, the locate command points to the grave that is your new last grave (in relation to the time, when this was spawned).
- After collecting your last grave, the locate command points to the grave that is your nearest grave (in terms of radius).
Ideally I’d like to see both methods, maybe can toggle between modes. But I’d prefer the first method if I had to choose.
Describe alternatives you've considered
I considered switching back to the VanillaTweaks graves module, which would require a lot of manual work deleting the graves from the plugin beforehand.
Currently I’m working with tickets and manually searching the graves (with the /execute at armorstand method) but it is a major downgrade from VanillaTweaks in my opinion.
Other
N/A
Metadata
Metadata
Assignees
Labels
status: ☑️ acceptedThis issue or pull request is accepted as validThis issue or pull request is accepted as validtype: pack parityFeature to close functionality gap between this plugin and a datapack. Given higher priorityFeature to close functionality gap between this plugin and a datapack. Given higher prioritytype: 🎯 featureNew feature or requestNew feature or request