Template talk:Infobox metaobj

User_talk:Rook - Currently best documentation source.

Old messages

There is no Hurt for now. Can some one delete this propereti from template? --Rootconsoler (talk) 15:23, 29 June 2016 (EDT) I'd rather leave it until dev says theyre not going to reimplement hurt. if you get confirmation i'll remove it --Ricky (talk) 00:28, 30 January 2017 (EST) Great timing with the jorb stream coming up 3 hours from now! :) Digzol (talk) 13:15, 1 February 2017 (EST) The hunger/energy info on food is a link to a number. Grapes for example, looks like this: Energy/Hunger: 125 How do we make that number not a link? --GauHelldragon (talk) 23:51, 8 October 2016 (EDT) I actually dug through the infobox page and found a fix for those linked numbers. shouldnt happen now. --Ricky (talk) 00:28, 30 January 2017 (EST)

ToDo's

(minor stuff to include in next major edit)

• Revision: 72045
  • Ditch "<empty>" input case for ccrafted. Blocks potential template-call display style where all/(well most) parameters are displayed without any data in templated call.(Done)
  • Category:Foods is set two times by hunger parameter (one can go, last)(Done)
  • Category:Structures, InfoboxEquipmentStat, lift:
    InfoboxEquipmentStat can't be used with bools (only checks for any data)
    Move cat into Lift data-case check.(Skipped. Lift also functions as a general structure flag (ie: extended bool. (True/False/None)). The general structure flag might not be to clear, due to it being used on seemingly none structures (to be checked))
• ...

(to be looked at)

• Other bools, like lift, template parameter-data normalization. lift evolved to using "Yes/No", while ccrafted evolved into using "yes")
• Ditch or keep single-value property collection. Technicality those are just single-data lists (ergo: category type data), while properties are multi-data (links) type data. There not hurting, but not really necessary either (if same data category is available/used). ... Exception seems to be, for quickly adding such a property into an #ask table to view/find misfit cases.
  • Current single-data properties: ccrafted(not actively used), ...
• Category:Structure: check used parameter combinations (lift, repwith, sthp, soak)
• ...

(temp notes/reminders)

• Category:Structure: when is something a structure. At least stuff that uses a build-sign-post. + repwith seems logical to.
  • Category:Structure is set on: lift, repwith, sthp, soak.

Gilding Attributes

I'd been working on adding links to a special search page for related gilding attributes; a discussion was just started on my talk page that maybe it isn't useful there (although I'm not in agreement, I'm fine to defer). However, the standard tends to be that folks wind up mixing Attribute impacts with Gilding Attribute classes; they don't really have anything to do with each other hence the point of the chances I've been making. That said, would be good to have a way to auto-matically cross link to other related gilding attributes, especially if possible more easily discovering which Gildings (property gildatt) match to which Equipment's Gilding Attributes (property Egildatt). The "special page" search link looks like this: `Special:SearchByProperty/:Egildatt/` -- it would be useful in my humble opinion to integrate that, or its companion `Special:SearchByProperty/:gildatt/` into the infobox template as decoration on the gilding attribute list entries. ProgrammerDan (talk) 16:39, 18 January 2019 (EST)