Skip to content

Conversation

nivcoo
Copy link

@nivcoo nivcoo commented Jul 26, 2025

Hello,

I add and option and permission to bypass it to disable vanilla block break.

I handle interact events and runstack to prevent any issue with that feature. Like that if the option is enabled the player will not able to open menu and stack/unstack I don't test with plugin like WildTools to take spawner with it.

I was hard to find a way to determine if spawner is natural or not, be free to say if there is any better method than mine.

Thanks

@OmerBenGera
Copy link
Member

What about server restarts? You don't save this to DB.
I also think it should be in a different plugin and not built into WildStacker

@nivcoo
Copy link
Author

nivcoo commented Jul 26, 2025

You don’t save natural spawner into db so it will be ok after restart, and yes maybe an addon that detect if it’s ws spawner or not ? But which method in API say that spawner is natural or not ? There is no method into the API actually

@OmerBenGera
Copy link
Member

You don’t save natural spawner into db so it will be ok after restart, and yes maybe an addon that detect if it’s ws spawner or not ? But which method in API say that spawner is natural or not ? There is no method into the API actually

This means that after a server restart the state of whether a spawner is natural or not will be lost.
Regarding a custom plugin, you should track natural spawners by yourself, not using WildStacker's api.

@nivcoo
Copy link
Author

nivcoo commented Jul 27, 2025

No I mean that the state is not saved but you don’t save natural spawner into DB so after restart it will work too I already test that. I just explain to you why it works. And I don’t understand why you want a new plugin for that. Imagine you have to duplicate database to save which spawner is natural or not, hook the wildstacker api to cancel interaction with block because if I place spawner near another it will stack it so I have to cancel the event. It will better to manage everything related to spawner into the plugin that manage the spawner no ? It’s the same feature as silkdrop or something like that.

@OmerBenGera
Copy link
Member

No I mean that the state is not saved but you don’t save natural spawner into DB so after restart it will work too I already test that. I just explain to you why it works. And I don’t understand why you want a new plugin for that. Imagine you have to duplicate database to save which spawner is natural or not, hook the wildstacker api to cancel interaction with block because if I place spawner near another it will stack it so I have to cancel the event. It will better to manage everything related to spawner into the plugin that manage the spawner no ? It’s the same feature as silkdrop or something like that.

I will think about that

@OmerBenGera OmerBenGera reopened this Jul 28, 2025
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

Successfully merging this pull request may close these issues.

2 participants