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

Disable mob spawner nerf for naturally generated spawners #2411

Closed
Xinayder opened this issue Aug 4, 2019 · 7 comments
Closed

Disable mob spawner nerf for naturally generated spawners #2411

Xinayder opened this issue Aug 4, 2019 · 7 comments
Labels
resolution: won't fix Issue will not be resolved or feature not added. type: feature Request for a new Feature.

Comments

@Xinayder
Copy link

Xinayder commented Aug 4, 2019

The current Spigot setting nerfSpawnerMobs and the related Paper setting to make these mobs jump, so as to not break mob farms, work for any kind of spawner.

It would be nice if there was a third setting that could disable this nerfed behavior for naturally generated spawners, which wouldn't get rid of the danger aspect of dungeons and mineshafts.

@zachbr
Copy link
Contributor

zachbr commented Aug 10, 2019

The server does not track which spawners are naturally generated vs placed by a plugin. This seems out of scope for the server-core.

@stale
Copy link

stale bot commented Dec 3, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@Machine-Maker
Copy link
Member

I was thinking of adding new API to spawners for setting their nerf'd status. If that happens, this can be a thing.

@stale
Copy link

stale bot commented Feb 4, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale
Copy link

stale bot commented Feb 11, 2021

This issue has been automatically closed because it has not had activity in a long time. If the issue still applies to the most recent supported version, please open a new issue referencing this original issue.

@stale stale bot closed this as completed Feb 11, 2021
@Machine-Maker Machine-Maker reopened this Nov 10, 2021
@stale stale bot removed the resolution: stale label Nov 10, 2021
@Machine-Maker Machine-Maker added resolution: stale status: accepted Disputed bug is accepted as valid or Feature accepted as desired to be added. type: feature Request for a new Feature. labels Nov 10, 2021
@stale stale bot removed the resolution: stale label Nov 10, 2021
@Igzak
Copy link

Igzak commented Feb 11, 2023

Any updates? Really good feature

@Owen1212055
Copy link
Member

In general, there is no great way to distinguish blocks placed by plugins vs natural generation. It is very much possible to use the API to mark custom-placed spawners with a special tag that can be used in joint with #4863 (comment)

@Owen1212055 Owen1212055 closed this as not planned Won't fix, can't repro, duplicate, stale Dec 27, 2023
@Owen1212055 Owen1212055 added resolution: won't fix Issue will not be resolved or feature not added. and removed status: accepted Disputed bug is accepted as valid or Feature accepted as desired to be added. labels Dec 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
resolution: won't fix Issue will not be resolved or feature not added. type: feature Request for a new Feature.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants