Forum:Lost Items (Re)Claim
I'd like to suggest a new databox related to reclaiming lost and/or destroyed items in game. Currently the item infobox includes info whether the item can be dropped or destroyed, and the destroy message in the latter case. While the destroy text usually inclues the necessary information, it is not always exhaustive (reclaim cost is often missing) and not necessarily accurate (there was a number of cases where this text was wrong over the years, at least temporarily). More detailed explanation is usually given in the prose of the article, however it's not standardised and not always easy to find at a glance. The databox would allow us to collect all data in a consistent, more visible format, while also allowing us to further use that data to generate categories or lists more easily.
For example, category Reclaimable from Diango needs to be added to every single page manually at the moment, similarly to the Diango/Reclaimables article, which requires manual upkeep and from what I can tell neither is particularly comprehensive or up to date, since they are likely usually forgotten. This is clearly not optimal way of doing this, especially since Diango is not the only entity related to reclaiming items we: also have May's Quest Caravan#Quest item storage or List of texts and tomes for books reclaimable from POH. Books already make use of their own databox noting if they can be found on bookcase, however some can also be reclaimed from the quest caravan or other sources, and would also benefit from the new databox.
Similarly to parameters used in Infobox Item for noting behaviour of items on death, the Databox would include the following info:
- reclaimable =
- yes (can add general "Reclaimable items" category)
- no (item is lost if destroyed, for example items that would need to be obtained again as a drop or a reward instead)
- temporarily (only during a specific quest or event and not reclaimable after the content is completed)
- restricted (potentially reclaimable multiple times, but only as long as player remains in certain area/minigame etc.)
- source = how do you reclaim the item: name of NPC or scenery that needs to be interacted with
- cost =
- free (can be reclaimed for free)
- fee (can be reclaimed for X coins, often case for items with combat stats)
- notes = details on the restriction (i.e. "Only during X quest/Y event")
- discontinued = potential optional parameter noting that the item can be reclaimed by those who already owned it, but cannot be obtained anymore if not. If reclaimable = no & discontinued = yes, could include category "Items destroyed if lost". We have similar category for items lost on death but this would also include other cases like manually destroying the item.
Parameters would automatically add relevant categories like "Items reclaimable for free/for a fee". For sources that can return multiple items we could have "Items reclaimable from holiday/quest item storage". While Diango's name is currently used, his storage can be accessed from a few other NPCs and directly from the bank, so this could be potentially renamed (although arguably Diango is commonly recognisable for this functionality). Having the information in the databox would also allow to generate specific lists much easier, for example we could create a table of reclaimable combat equipment in specific slot sortable by cost to reclaim etc.
A rough mockup, the actual parameters, names of cells and general layout are up for suggestions. (Click [show] to expand)
|Yes||Ivan Storm||100,000||After The Lord of Vampyrium|
|Yes||Quest item storage||Free|
|Yes||Quest item storage, Bookcase||Free||After Twilight of the Gods|
|Teporarily||Luna||Free||During 2021 Hallowe'en event|
|Restricted||Teelee||Free||During Wisps of the Grove|
One other potential consideration are edge cases of items that are reclaimable unless lost in the Wilderness, i.e. Lucky Saradomin godsword. However I'm not sure how those items behave after the Wilerness rework and if this info is not better suited for the kept on death section in the infobox (which as a side note probably requires revieving with regards to the same rework).
I feel the databox would be useful to both players (more comprehensive, visible and consitently presented information) and for the editors (we can do more with the data & maintain it easier). One major concern is the sheer number of relevant items. We could potentially generate a list of all items with destroy text in the infobox and no reclaim databox and then just gradually go through them, using the destroy text and/or in-game verification. It will take a substantial amount of time & work, however we already have a number of massive ongoing projects like update history, graphical updates, so personally I wouldn't consider it a reason not to do it. As mentioned, the proposed parameters and databox layout are just a mockup to give the idea and showcase different examples so any feedback on those or alternate suggestions are welcome.
Also an honest disclaimer, I'm absolutely clueless about modules/Lua, so while I'd love to implement the databox on the pages, I probably wouldn't be able to actually make said databox. Mariobaryla (talk) 22:11, 18 August 2022 (UTC)
- Support - However I'd like to suggest some changes:
- The databox should run verticly rather than horizontally.
- Type doesn't make sense as a header; Type: Yes/No is strange to read.
- Change the Notes header to Requirments?
- I'd also like to ask if you've thought about where on the page this would sit in relation to other sections?
07:37, 19 August 2022 (UTC)
- I've revised the naming and style a bit to be more in line with other databoxes.
- Not sure about the exact placement since I started with horizontal one which could easily fit anywhere. The main databox of the article with combat stats or other core item info should likely take precedence, beyond that not sure. It also depends whether we want to keep the info in the prose, as it currently is, or fully replace it with databox. Mariobaryla (talk) 12:42, 19 August 2022 (UTC)
Comment - I do like the idea of having the reclaim information made clearer but wonder if this is something that should be kept within the item infobox? Reclaim information is pretty significant and on longer pages which already have a lot of sections with databoxes e.g. rune platebody I think that moving reclaim information to a databox might make it harder to find/pushed down the page. 13:43, 31 August 2022 (UTC)
Support/Per-Isobel - Overall, I like the idea, but I think it should be part of the infobox, not separate in the prose or as its own box. The properties could all be optional, and only display if the are not blank. (ie, fee/cost would not even show up unless item is reclaimable, etc). Perhaps something along the lines of this mockup? (Click show to see).
14:18, 12 September 2022 (UTC)
- Support - and agree with Isobel and Myles that the item infobox seems like the best place. Weletta (talk) 15:03, 13 September 2022 (UTC)
Support vertical - I think expanding on this would be a good idea. Perhaps we could keep what's in the infobox and add the databox to the page. This way the information would not get lost on longer pages.19:04, 27 September 2022 (UTC)
Soft support vertical separate databox - request for clarification on placement and more clarifications - I think making sure the information is not lost on longer pages is a valid concern, and keeping it separate aids from a reader perspective. I'm curious if there could be assigned smw (or Bucket?) properties to allow the "source" of a reclaim to be autogenerated on the corresponding page. Additionally, I'd like to see some thoughts on where this should be from a page style guide perspective when it's rolled out. Overall, I support this concept and think it should be pursued, but would like to see more if it fleshed out/prototyped beyond Blackhawk's suggested formatting prior to it being implemented.12:02, 4 October 2022 (UTC)