Option for Spawneggs changing Spawner Type
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
Research direction
Start by tracing the blacklist-txt handling for the on-use=deny attribute and the monster-spawner interaction path. Determine how changing a spawner type with spawn-eggs is distinguished from mining it, then implement and document one supported configuration, blacklist, or region-flag option. Done means egg-based type changes can be denied while pickaxe destruction remains allowed.
Written by the indexing model from the issue text.
Description
The Problem
Hey :)
I already asked 1-2 days ago in discord but I will repeat it here so that it won't get flooded away etc:
Is there the possibility that you can implement the option (either in the general config or in the blacklist-txt for per-world options) to change the behavior on monster-spawners?
So that users can NOT change the spawner types with spawn-eggs but still destroy them with a pickaxe?
Currently I only can set up in the blacklist the attribute "on-use=deny" but this prevents also the mining of the spawners.
A Solution
- general config option like "change-spawner-type-with-eggs: true /false "
- or new option for the blacklist-txt for per-world settings
Alternatives
If that isn't as easy maybe an own region-flag?`something like "spawner-changetype" (allow/deny)
Anything Else?
Hope it is possible in any way, but this current way is a bit blocking 😅
Thanks in advance 🫂
- Dominant language
- Java
- Stars
- 938
- Forks
- 674
- Avg merge
- 22h 57m
- Merged PRs (30d)
- 1
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from EngineHub/WorldGuard
-
NullPointerException when setting flag to "none" in RegionCommands.setFlagPossibly taken @HP-network claimed this 18 days ago. Openstatus:pending type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
EngineHub/WorldGuard#2305 ·
-
Folia: Cause.Builder reads Creature#getTarget() from a non-owning region during vehicle damagePossibly taken @baichuan335 claimed this 12 days ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 72/100
EngineHub/WorldGuard#2311 · 1 comment ·
-
status:pending type:bug
Difficulty 4/5 3-5 days Newbie friendliness 48/100
EngineHub/WorldGuard#2302 · 4 comments ·
-
status:pending type:feature-request
Difficulty 4/5 3-5 days Newbie friendliness 45/100
EngineHub/WorldGuard#2301 · 5 comments ·
-
status:pending type:feature-request
Difficulty 5/5 Over a week Newbie friendliness 25/100
EngineHub/WorldGuard#2288 · 1 comment ·
All issues in EngineHub/WorldGuard
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
Make branch and label autocomplete matching locale-independentPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
jenkinsci/gitlab-plugin#1950 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
commons-app/apps-android-commons#6984 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
It's not necessary to copy the memory block in the readWrite() of org.h2.store.fs.mem.FileMemDataOpen
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
h2database/h2database#4435 ·
Maintainers usually reply within 1 day