lost&found chests #3355

New Issue

yourland-report · 2022-12-29T01:53:06Z

yourland-report commented

2022-12-29 01:53:06 +00:00

we need a more coherent mechanic for returning lost items to players. these will be called "lost&found chests".

my vision:

a place like the basement of the town hall in haven, where chests containing items belonging to various players can be placed.
staff should be able to put and take things from the l&f chest, and configure them.
bailiffs should be able to put stuff into a chest and mark the owner, but not take stuff out. bailiffs should not be able to make themselves the owner of a lost&found chest.
"owners" should be able to take their stuff.
no-one else should be able to interact w/ them.
when a chest is emptied, it should automatically clear the owner and indicate it's ready for re-use, probably by changing color.
when a chest is assigned to a player, it should automatically email them w/ the coordinates
chests should display the owner's name on the front as a sign
they should have configurable inventory size, up to a point. allowing them to contiain 90+ stacks shouldn't be an issue.
there needs to be a separate mechanic for "normal" players who want to return stuff; they shouldn't be able to fill random lost&found chests w/ garbage or rude notes. there should be some additional "mail items to a player" node, which requires bailiffs/staff to moderate.

we need a more coherent mechanic for returning lost items to players. these will be called "lost&found chests". my vision: * a place like the basement of the town hall in haven, where chests containing items belonging to various players can be placed. * staff should be able to put and take things from the l&f chest, and configure them. * bailiffs should be able to put stuff into a chest and mark the owner, but not take stuff out. bailiffs should not be able to make themselves the owner of a lost&found chest. * "owners" should be able to take their stuff. * no-one else should be able to interact w/ them. * when a chest is emptied, it should automatically clear the owner and indicate it's ready for re-use, probably by changing color. * when a chest is assigned to a player, it should automatically email them w/ the coordinates * chests should display the owner's name on the front as a sign * they should have configurable inventory size, up to a point. allowing them to contiain 90+ stacks shouldn't be an issue. * there needs to be a separate mechanic for "normal" players who want to return stuff; they shouldn't be able to fill random lost&found chests w/ garbage or rude notes. there should be some additional "mail items to a player" node, which requires bailiffs/staff to moderate.

AliasAlreadyTaken was assigned by yourland-report

2022-12-29 01:53:06 +00:00

AliasAlreadyTaken added the

1. kind/enhancement

label 2022-12-29 03:24:19 +00:00

AliasAlreadyTaken commented

2022-12-29 03:25:32 +00:00

We also need a way to create those itemlists from external sources, like the log, so that it's easy to recreate lost books, bones or similar

flux commented

2022-12-30 04:07:40 +00:00

We also need a way to create those itemlists from external sources, like the log, so that it's easy to recreate lost books, bones or similar

i could do a thing where it could read in an itemstring or dumped inventory list. is that what you mean? i don't think it's a great idea to get it to actually try to parse the debug.txt log file.

> We also need a way to create those itemlists from external sources, like the log, so that it's easy to recreate lost books, bones or similar i could do a thing where it could read in an itemstring or dumped inventory list. is that what you mean? i don't think it's a great idea to get it to actually try to parse the debug.txt log file.

flux changed title from ~~rheo reports: we need a more coherent mechan ...~~ to lost&found chests

2022-12-30 04:11:55 +00:00

AliasAlreadyTaken commented

2022-12-30 04:17:56 +00:00

If we don't want to parse debug.txt, then we hould log item-related transfers in a readable format.

Imagine bones. Someone lost for whatever reason their bones. Then we need a way to read what we currently write in a certainly structured way into the log by some way to hand out those items. So far I put the log into Libreoffices's Calc to have it in columns, replace a bit, cut a bit, so that I have a "/giveme itemstring number" format.

If we don't want to parse debug.txt, then we hould log item-related transfers in a readable format. Imagine bones. Someone lost for whatever reason their bones. Then we need a way to read what we currently write in a certainly structured way into the log by some way to hand out those items. So far I put the log into Libreoffices's Calc to have it in columns, replace a bit, cut a bit, so that I have a "/giveme itemstring number" format.

daydream commented

2022-12-30 11:38:42 +00:00

could it use mailbox code that staff can set to player name but once they empty it - it reverts to available.

flux commented

2022-12-30 21:24:07 +00:00

If we don't want to parse debug.txt, then we hould log item-related transfers in a readable format.

Imagine bones. Someone lost for whatever reason their bones. Then we need a way to read what we currently write in a certainly structured way into the log by some way to hand out those items. So far I put the log into Libreoffices's Calc to have it in columns, replace a bit, cut a bit, so that I have a "/giveme itemstring number" format.

i guess i could make something that pulls itemstrings out of log messages like "%s added %s to bones @ %s", but i'd still prefer that someone copy/paste the log lines into a formspec than write a mod that tries to deal w/ the log file directly. and it'd be easier if it just had to handle copy/pasted itemstrings. possibly i'll do the itemstrings first and add the other features later.

> If we don't want to parse debug.txt, then we hould log item-related transfers in a readable format. > > Imagine bones. Someone lost for whatever reason their bones. Then we need a way to read what we currently write in a certainly structured way into the log by some way to hand out those items. So far I put the log into Libreoffices's Calc to have it in columns, replace a bit, cut a bit, so that I have a "/giveme itemstring number" format. i guess i could make something that pulls itemstrings out of log messages like `"%s added %s to bones @ %s"`, but i'd still prefer that someone copy/paste the log lines into a formspec than write a mod that tries to deal w/ the log file directly. and it'd be easier if it just had to handle copy/pasted itemstrings. possibly i'll do the itemstrings first and add the other features later.

👍 1

flux added this to the flux's TODO list project 2022-12-30 21:24:13 +00:00

flux added the

4. step/at work

label 2022-12-30 21:24:23 +00:00

flux self-assigned this 2022-12-30 21:24:32 +00:00

AliasAlreadyTaken commented

2022-12-31 06:15:19 +00:00

Either that or we could alter the log messages into a better readable format.

IMO all item actions need to be logged anyway, in some unified, readable and parsable format.

item to and from chest, item to and from ground, item break, item destroym ...

Either that or we could alter the log messages into a better readable format. IMO all item actions need to be logged anyway, in some unified, readable and parsable format. item to and from chest, item to and from ground, item break, item destroym ...

flux removed the

4. step/at work

label 2023-02-12 00:13:00 +00:00

flux commented

2023-02-12 00:13:57 +00:00

putting this on pause because trying to code non-trivial formspecs makes me reconsider life choices.

😆 3

Sign in to join this conversation.