A command to get a book with latest death coordinates #4634
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#4634
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?
Should be a command for staff.
And possibly some way to get it for players themselves? NPC? Crafting recipe? Voodoo ritual?
Related
#3097
#1099
#2478
A book with latest death coordinatesto A command to get a book with latest death coordinatesLet's first have a cache with the last 10 death positions and a fucntion to put them into a book.
Where we execute that command, NPC, chatcommand, ..., ... is rather secondary.
I found something interesting:
Do not load death messages and team spawn points at serverstart
Why did you disable deaths?
Maybe we should re-enable it and add coordinates to that log?
UPD: I see why... It's a giant json file...
what is the actual goal here? getting the position of the player at death, or the position of bones? because bones don't necessarily end up where the player died. the priest knows about bones. i feel like this sort of tracking should be done in
yl_church
.I think the goal should be bones positions. Currently people can lose their bones because of multiple deaths + not being able to use compass. Positions of them ideally should be preserved between server restarts too.
Alias sometimes gives books of bones positions to people, but creates book manually. Book creation should be automatic, available to staff and possibly to regular players.
True, that could be done in the city service, most people already attach the "death note" to the priest and wish for them to hand out those books.