/cwiki could benefit from more custom-tailored technical information

[JoakimThorsen]

trafficstars

Not sure what the best approach to implement this is, but the current implementation of /cwiki only provides a very surface-level "definition" of sorts. To explain with an example, if I look up the wiki page of a beacon, chances are I want the range of it, not "it is a block with a light beam that gives status effects"

Other examples (not saying all of these are good): Hunger values for different food items attack damage/mining speed for tools (with enchantments like smite?) Properties for different blocks (is it transparent? blast resistance? flammability? luminance? designated tool?) Heath and attack damage of mobs Spawning conditions of mobs Hitboxes Crafting recipies (and uses)

(Less feasible ones) Timings of redstone components? Villager trades, piglin bartering chances?

[barraIhsan]

And also maybe add Visit Wiki at the end It basically just https://minecraft.gamepedia.com/Special:Search?search=%s So you can visit the wiki if you want more detail

[Earthcomputer]

Adding a link to the wiki might be the best option here... the cwiki command is mostly an experiment that turned out to not be as useful as I'd hoped

[JoakimThorsen]

How about being able to view the "contents" list of a wiki page, and then being able to choose the one you would like to look at, where you would then be able to "scroll" through the text? E.g. using somehting like /cwiki <pagename> obtaining 2 to view the next paragraph/the next 100 words/the next whatever of the "obtaining" section of an item (could be enhanced by using clickable text in the chat too)

In this hypothetical you would also be able to select the "notaninfobox"-infobox too of course, perhaps even using special selectors like infobox.tool to specifically query the info you want.

I have not yet sussed out how tables and the like would look in this hypothetical btw, especially larger ones would be quite hard to display. The "Breaking" page for example has a 12-column and 295-row table which could become a bit messy.