debiankaios reports: my sword broke but no message ... #1510
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
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#1510
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?
debiankaios reports a bug:
Player position:
Player look:
Player information:
Player meta:
Log identifier
Profiler save:
Status:
Teleport command:
Compass command:
Aloha,
which type of sword was that?
Related: Please do not blindly rely on this message.
Greetings, Alias
i'm guessing it was a victim of debiankaios's terrible internet connection
y'know, it's technically possible to keep weapons from disappearing when they break, but instead replacing them w/ a non-functional varaint which could be repaired
This was due to using the sword to kill mobs. There's no easy, general way to fix this behavior because
mobs_redo
doesn't expose the necessary API hooks, and mobkit mobs don't cause any tool wear whatsoever.See comments in your-land/yl_commons#9
The solution is something we should address when mobs get an overhaul.
Maybe we could use
https://github.com/minetest/minetest/blob/master/doc/lua_api.txt#L7735
This seems to include however the tool is used, on dig on mobs, on anything. drawback, this will overwrite default wear and we'll have to deal with it on a custom basis.
If it works, we can add logging there.
Just tested to make sure -
after_use
is not called when attacking mobs, only when breaking nodes.so, it occurred to me today - why not just override the
on_punch
callback for all mobs_redo entities, check the tool wear before and after, and warn if the tool is damaged?i discovered you can do that, but that mobs_redo has a bug in which, after a normal hit, the tool is again worn down by the engine's on_punch logic. i've created an upstream issue for this: https://notabug.org/TenPlus1/mobs_redo/issues/134
however, the problem remains - there is no way to detect when the engine wears the tool down when punching a mob.
i've implemented a warning when a player punches a mob and the tool wears, which also takes into account the wear from the engine by simulating it
b381c284e7
i've created a new issue for the upstream mobs_redo report, which is somewhat tangential: #3916
QA
I get a message when the sword is close to breaking. That should be ok for now
this is live