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

console bug on spawner explode #1010

Open
homerek111 opened this issue Jan 20, 2025 · 8 comments
Open

console bug on spawner explode #1010

homerek111 opened this issue Jan 20, 2025 · 8 comments
Assignees
Labels
✔️ Confirmed Confirmed bugs that can be replicated 🔧 Potential fix A potential fix was already submitted

Comments

@homerek111
Copy link

homerek111 commented Jan 20, 2025

Minecraft's Version

This server is running Paper version 1.21.1-100-master@20ec622 (2024-09-26T23:53:46Z) (Implementing API version 1.21.1-R0.1-SNAPSHOT)

Plugin's Version

2024.4-b116

Describe the bug

in-game i dont see anything not working - but in console there is an error:

log: https://pastebin.com/2eFE2910

as i tested error does not happen if there is more than 1 spawner stacked (so it happens only when there is 1 spawner in a stack only)

I use silkspawners also 8.2.0

Also idk if it is a bug or not but when there are 2 or more spawners stacked when creeper/tnt explodes one of the dropped spawners is always dropped on the ground (not to the inventory. In both configs i have drop to inventory enabled

To Reproduce

explode with tnt/creeper

Additional Information

No response

@homerek111 homerek111 added the Pending Pending reports to be investigated label Jan 20, 2025
@OmerBenGera
Copy link
Member

Please send me a link to the SilkSpawners you use.

@OmerBenGera OmerBenGera added 📝 Missing information Required information is missing and removed Pending Pending reports to be investigated labels Jan 25, 2025
@homerek111
Copy link
Author

Please send me a link to the SilkSpawners you use.

https://dev.bukkit.org/projects/silkspawners

@OmerBenGera OmerBenGera added ❌ Unconfirmed Bugs that were reported but yet to be replicatable and removed 📝 Missing information Required information is missing labels Jan 30, 2025
@OmerBenGera
Copy link
Member

OmerBenGera commented Jan 30, 2025

I can't replicate it myself, however I added debug messages.
Please install latest dev build and wait for an error to occur, then upload it to pastebin

@homerek111
Copy link
Author

homerek111 commented Jan 31, 2025

I can't replicate it myself, however I added debug messages. Please install latest dev build and wait for an error to occur, then upload it to pastebin

log: https://pastebin.com/UPYBg8MK

also i have noticed that you made it cancel the explosion blocks break in dev#121

  • when i use dev#116 tnt/creeper explosion breaks blocks normally
  • but when i use dev#121 tnt/creeper explosion does not break blocks/spawners (it only gives damage)

this cancel explosion happens only when in explosion range there is a spawner (if spawner is not near the explosion blocks break normally)

@OmerBenGera
Copy link
Member

Please upload your config file to pastebin and send a link to it here (WildStacker's config file)

@homerek111
Copy link
Author

Please upload your config file to pastebin and send a link to it here (WildStacker's config file)

https://pastebin.com/0fSHGFEz

@OmerBenGera OmerBenGera added ✔️ Confirmed Confirmed bugs that can be replicated and removed ❌ Unconfirmed Bugs that were reported but yet to be replicatable labels Feb 1, 2025
@OmerBenGera OmerBenGera added the 🔧 Potential fix A potential fix was already submitted label Feb 1, 2025
@OmerBenGera
Copy link
Member

Check out latest dev build, this should be fixed

@homerek111
Copy link
Author

Check out latest dev build, this should be fixed

@OmerBenGera i have just tested latest dev build and now it drops 1 extra spawner on the ground after explosion... (dupe glitch)

My silkspawners config: https://pastebin.com/9v9iQcaY
my wildstacker config: https://pastebin.com/hRkt0zYS

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
✔️ Confirmed Confirmed bugs that can be replicated 🔧 Potential fix A potential fix was already submitted
Projects
None yet
Development

No branches or pull requests

2 participants