Replace nether monsters with maintained version? #6191
Labels
No Label
1. kind/balancing
1. kind/breaking
1. kind/bug
1. kind/construction
1. kind/documentation
1. kind/enhancement
1. kind/griefing
1. kind/invalid
1. kind/meme
1. kind/node limit
1. kind/other
1. kind/protocol
2. prio/controversial
2. prio/critical
2. prio/elevated
2. prio/good first issue
2. prio/interesting
2. prio/low
3. source/art
3. source/client
3. source/engine
3. source/ingame
3. source/integration
3. source/lag
3. source/license
3. source/mod upstream
3. source/unknown
3. source/website
4. step/approved
4. step/at work
4. step/blocked
4. step/discussion
4. step/help wanted
4. step/needs confirmation
4. step/partially fixed
4. step/question
4. step/ready to deploy
4. step/ready to QA test
4. step/want approval
5. result/cannot reproduce
5. result/duplicate
5. result/fixed
5. result/maybe
5. result/wontfix
ugh/petz
ugh/QA main
ugh/QA NOK
ugh/QA OK
No Milestone
No project
No Assignees
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#6191
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Evaluate https://github.com/GreenDirkfried/minetest-nether-monsters to replace the nether monster repo we're using: https://github.com/rael5/minetest-nether-monsters
hm. maintained, but i'm not sure it really fixes any issues we have. the biggest change is that dragon armor gets nerfed from 10 fire protection to 1 - players will be quite upset when their dragon boots no longer protect them from lava damage on their own.
With that, I'd say do not change or find a way to modify the values, as the change essentially makes dragon gear almost completely useless. Willing to bet a lot of players (myself included) would be very very upset with these changes.
How does dragon armour NOT protect from fire damage? That is the very purpose ... !?
This is a maintenance issue, not a balancing one. The hope is to not have unmaintained code. The values on the relevant parts must stay the same - we'll not take fire damage protection off the dragon armour via backdoor.
changing the fire protection value would be very very simple.
i do still want to create a totally new mob API and port all our mods to it, but i don't have a timeline for that. i wouldn't mind taking over responsibility for merging our changes with upstream or various forks. if i'm being honest, i'm more interested in reworking damage and player effects and not so much mobs. i'm resigned to acknowledging mobs are terrible, but i don't think i can really improve them too much.