Template talk:Infobox metaobj
Jump to navigation
Jump to search
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: --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. |
ToDo's
- (minor stuff to include in next major edit)
- 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.
- Category:Foods is set two times by hunger parameter (one can go, last)
- Category:Structures, InfoboxEquipmentStat, lift:
InfoboxEquipmentStat can't be used with bools (only checks for any data)
Move cat into Lift data-case check. - ...
- (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), ...
- ...