AliasAlreadyTaken reports: No log message when a player d ... #2995
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#2995
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?
AliasAlreadyTaken reports a bug:
Player position:
Player look:
Player information:
Player meta:
Log identifier
Profiler save:
Status:
Teleport command:
Compass command:
this should be logged:
750761c11f/node.lua (L88-L92)
i'll do some testing locally.
well, that code isn't doing what it's supposed to do. now to fix it...
fixed in
7eef936a0f
, and added more detail to log messages in general.also fixed a crash that i'm unsure how we've avoided.
@AliasAlreadyTaken i can't verify this, please check and close this at your convenience :)
For some reason it's not, I can see neither the dig action nor the inventory action in the log.
probably the bones mod needs updated
We're on 750761c11f77bd72618b0e12fdb85ca2518ab94c : don't crash
This commit is from Date: Sun Jul 17 08:26:05 2022 -0700
https://gitea.your-land.de/your-land/bones.git
Since it was fixed way after that date, I assume the source is wrong, the branch is wrong or - most likely - the fix didn't get pushed :D
ah, i can resync w/ the "upstream"
rebased https://gitea.your-land.de/your-land/bones/src/branch/yl_stable
this is live