Template talk:Infobox item

Challenges

Unless I'm not finding them, there are no pages for challenges. I was about to create one, but to show a list of all the challenges and details, it would either have to be all manually put in, or a bunch of fields would have to be created. Specifically...

• new group/category/type?
• difficulty (easy, medium, hard, insane)
• r̶e̶p̶e̶a̶t̶a̶b̶l̶e̶ ̶(̶y̶e̶s̶/̶n̶o̶)̶ edit: looks like they're all repeatable, wouldn't need this until changes/additions would call for it
• time for bonus (time or none)
• requirements (kill certain animals, kill certain zombies, while drunk, with certain weapons, etc., or some other syntax simpler and shorter)
• reward (skill points awarded)
• bonus reward for time (skill points awarded)

If they're all just going to stay on one page, and not have separate pages for each different challenge, I'll just manually put them in. But before I do anything, and so it doesn't have to be redone, I'd like to hear what y'all think. Plus, I'm not sure if I would be overstepping by creating new fields, or even the correct protocol for doing so. I have all the info, but not sure what should be done with it.

Scur827 (talk) 16:09, 6 December 2016 (UTC)

When it comes to the editing of this Wiki, I like to think of the BOLD principle of Wikipedia. As the article says, "go for it." However, especially with templates, and more so with the Infobox_item template, take responsibility: "Be cautious about jumping in too quickly; discuss proposed actions with other users; but, in the end, be brave enough to do what needs to be done."

If you don't get much feedback here in the talk page, know you've done your part to seek consensus and assume silent consent. Having said that, I agree that an infobox is needed for challenges. An infobox will present useful and unique information per page, in a format and location already known to our readers and it will also enable DPL queries as you said. I don't think Infobox_Item is a good use for challenges because 1) it's already a very complicated template and 2) as its name implies; it should be used for items.

A while ago I started work on Claudes Treasure Map. That may or may not be useful to you. If it is, help yourself. The section titled "Finding The Chest" may be more appropriate as its own page that can then be linked from other treasure-hunting challenges...just a thought.

GrayBeard_Actual (talk) 23:01, 6 December 2016 (UTC)

I started work on a new infobox last night, then switched over to just using the existing item infobox today, without adding any new sections or fields or otherwise editing the template. I thought it would cover most everything, but after a while, I realized it really does need it's own template. There are actually two items for each challenge in the game data: the note the challenge is written on, and the challenge itself. It seems like it would be a bit confusing to have entries for both, and the note is an item that would use the item infobox, which wouldn't really show the details you'd expect to see. I'm going back to making the template.

While I'm here, is there a way to hide my user sandbox pages edits from the recent changes? I'm up and down a lot, and do a bit of saving, and it's cluttering up things a little.

--Scur827 (talk) 19:52, 7 December 2016 (UTC)

Do challenges include the treasure quests? or even the other quests that are available? Should they?

— Tilleen ^(talk) 00:08, 8 December 2016 (UTC)

They're split up into 3 things: quests, challenges, and treasure maps, but all are defined in the quest.xml, and only those things. Since the main one is more a tutorial I thought I'd call it that, or tutorial quest or something similar, to differentiate it from the overall heading of quest. The template is going to cover all three. But all three are separate things in the .xml, just have lots of common fields.

--Scur827 (talk) 00:21, 8 December 2016 (UTC)

Change Format in documentation

I'd like to propose to remove the following part from the documentation:

• Please add a small picture of an item you put into the infobox (e.g. ammunition) for the overall look.

Use this syntax:
 |ammo = [[File:CrossbowBolt.png|20px|link=Crossbow Bolt]][[Crossbow Bolt]]
 will look like: Crossbow Bolt

In my opinion this create a lot of extra code and work, without contributing anything to the user's experience. Furthermore, it is barely used at the moment, so if you want to make it standard practice (as suggested) we have to change a lot of pages for merely a small cosmetic change. I think the best way to go is to remove this from documentation and use simple links ( [[Crossbow Bolt]] ) in the infobox. Also, to keep things in line with each other, I would suggest to remove the small icon when you come across one.

What are your thoughts on this?

JonPardon (talk) 15:45, 3 February 2017 (UTC)

I generally agree, it does not add very much, and could be automated, so that the link provided provides the image via a dpl query. This of course may make it a bit expensive processing wise I suspect. I should still be removed.

On another topic, do the fields for weight and forge_weight mean anything any more? None of the values seem to match the weight value in the xml files. Is this just because the values are no longer used, or just one of them has been deprecated?

— Tilleen ^(talk) 21:37, 14 February 2017 (UTC)

Editors, note

that the the templates goes into a mess, when you dumbly follow the developer's naming and schemes, they have a class parenting and other things that make the changes easier, and they work there full time, use logic, base forms and correct terms to adapt to any possible changes in advance.

Ilias48rus (talk) 2019.05.10

Autocategorization

Looking at the code for autocategorizing...

Currently, autocategorizing does NOT work for the "categories" field, and the "type" field is ONLY autocategorizing if no "categories" field is defined. See the code listed underautocateorization in the footer section of source.

I would propose having all items Categorized in a 3 tier hierachy consisting of: 1) Item Group (already restricted to a set number of groups) 2) Categories (should also be restricted to a set number of categories, there is a lot of variability in items) 3) Type (should also be restricted to a set number of types, there is a lot of variability in items)

So for example, an Iron Pickaxe would have Item Group of Tools/Traps and Ammo/Weapons, Categories of Tool and Weapon, and Types of Manual and Melee

Pages with broken file links

Every item using the Infobox item template is being categorized as Category:Pages with broken file links Fixed 2 broken png files in Template Infobox Item which were causing the issue. This is resolved now.