False Death Messages in gen chat #1015
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/petz
3. source/testserver
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/possible close
4. step/QA main
4. step/QA NOK
4. step/QA OK
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
kind/standalone
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#1015
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
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?
related issue to #998 I haven't seen reported yet. Sometimes we get a death message displayed in gen chat, only to have the person in question disagree a moment later, usually they're in a fight and have just taken damage, but aren't dead.
Maybe Minetest registers the incoming lethal damage and displays the death message without considering damage that didn't come through due to the armor...and MT doesn't consider whether the player is actually dead.
Currently I cannot tell on which level or at what depth of Minetest I should look for the cause of this.
False Death Messagesto False Death Messages in gen chatThere's two parts to this. The death message comes from
mt-respawn. The lack of death comes from the heal factor from3d_armor. The solution, as far as I understand it, is thatmt-respawnshould be usingminetest.register_on_player_hpchangeor even better,minetest.register_on_dieplayer, instead ofminetest.register_on_punchplayer. I think it uses the latter because it allows you to more easily get the name of the weapon that was used to kill a player during PvP.Simple solution: I gather what MT believes to be the cause of death in a table, but only send once at register_on_dieplayer
Fixed in mt-respawn 325939d3cb4a30865dc2f345ac711270eb2dd2d9