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

No spawner perms, spawners duping when mined, change mob type with egg will only change the mob inside. #580

Closed
4 of 5 tasks
Rashdonkey opened this issue Oct 1, 2024 · 1 comment

Comments

@Rashdonkey
Copy link

What steps will reproduce the problem?

  1. Mining spawners will sometimes dupe them
  2. No perms even with the following permission nodes:
    -silkspawners.changetypewithegg.* (true)
    -silkspawners.place.* (true)
    -silkspawners.silkdrop.* (true)
    -silkspawners.info (true)
    -silkspawners.help (true)
    I am also using Luckperms for this.
  3. Changing mob type with an egg will only change the mob inside. the spawner holographic text remains the old mob. Picking the spawner back up also reverts it back to the old mob.

Log file of the issue/error

https://mclo.gs/K9rvult

/version output?

This server is running Paper version 1.21-130-master@b1b5d4c (2024-08-10T10:02:42Z) (Implementing API version 1.21-R0.1-SNAPSHOT)
You are running the latest version
Previous version: git-Paper-450 (MC: 1.20.4)

SilkSpawners version

SilkSpawners version 8.1.0

Please provide any additional information below.

I can provide configs and video proof if needed. I also have like 90 plugins so I can provide that too

  • I am aware that issues caused by /reload are ignored
  • If there is a (potential) plugin conflict, I've identified the conflicting plugin
  • I have added a valid /version output
  • I have added a valid SilkSpawners version
  • I have attached necessary information like a screenshot, my list of plugins, config or permissions file(s)
@timbru31
Copy link
Owner

👋 Hi there!

We're kicking off the new year with some housekeeping in our repository to keep things organized and up-to-date. As part of this process, we're closing some older issues that haven't seen activity in a while.

If you're receiving this message, it means we're closing this issue. However, we want to assure you that your input is still valuable to us! If you believe this issue is still relevant or if you're still experiencing the problem, please don't hesitate to open a new issue.

When opening a new issue, it would be super helpful if you could:

  • Provide any updated information about the problem
  • Confirm if it's still occurring with the latest version of our software
  • Include any additional details that might help us investigate

Thank you for your understanding and continued support of our project. We appreciate your contributions and look forward to addressing any ongoing concerns.

Happy gaming! 🎮

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

No branches or pull requests

2 participants