Sokomine reports: now that the trash slot is gon ... #4155
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
5 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#4155
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?
Sokomine reports a bug:
Player position:
Player look:
Player information:
Player meta:
Log identifier
Profiler save:
Status:
Teleport command:
Compass command:
I have to review each and every book turned in to the library to make sure I don't have it already because there's no 'new' flag and even if there was - why should I have to delete all the books for the players just to roleplay returning a library book?
We could try 'new books only' and 'returned books' could be a camouflaged trash can... but if someone is turning in a book and does the wrong one - we'll never hear the end of it.
Maybe a red X on the book somewhere to 'go to book heaven' or something lol IDK but returning has issues. We'll have to think pretty far outside the box on this one.
Daydream has a very valid point. The idea was to have a special trash can disguised as a bookshelf so that players could "return" the books so that they'd automaticly get trashed.
Players putting new books in there and believing that's the right way to forward them to the library like daydream mentionned could be a big problem. My idea seems too risky then.
We'll bring back the old trashcan with the next server restart, until we have a replacement.
the accidental trash button removal seems to have gotten reset before i even noticed. i'd still like it if there was a dedicated trash "tab" in unified inventory, which had a limited undo functionality. cf. #2323
EDIT: this is the sort of thing i could write up in a day, perhaps i need to get my priorities straight.
This is a good issue for a new developer. In fact, TheTrueBeginner started on this one already.
Issue here: #4077
Repo here: https://gitea.your-land.de/your-land/yl_unified_trash
yl_unified_trash was implemented by yo_hi and delivered with 1.1.118
Giving books back would soon result in more copies than we can ever check. Closing this in favour of the new trashcan.
we can just use a tubelib trashcan and put a sign on it that says "book return"