Template talk:Unit infobox

Permanent Duration
duration = Permanent is not working. Elite stay (talk) 14:44, 5 January 2016 (UTC)


 * It is. You have to leave it out. It defaults to permanent. Since this template is for summoned units, a duration must be given. If not given, it choses permanent automatically.  Bu3ny  (talk) 14:48, 5 January 2016 (UTC)


 * For the record, permanet duration is now achieved by a 0 duration. Molldust (talk) 09:47, 29 February 2016 (UTC)

Structure parameter
Regarding the structure parameter, I should explain how it is supposed to work. We're not quite there yet. Suggestions welcome.

There's the need of 5 states:
 * main (English main game)
 * main trans (Non-English main game, aka wrapper)
 * custom (English custom game)
 * custom trans (Non-English custom game)
 * hidden

main vs. custom:

If you make a data pull with SMW, you need to able to distinguish whether the unit is from the main game or not. Or we introduce another optional  parameter that specifies the custom game. Would default to main then.

english vs. trans (aka wrapper):

It can't use the hidden value, because it needs to be sorted into categories and the title property needs to be taken into SMW. The remaining properties like stats need to be left out.

hidden:

Won't show up anywhere except on this specific page. No translations, just duplicates. Cannot be wrapped.

Molldust (talk) 09:47, 29 February 2016 (UTC)


 * What I concern about is how to make non-en's DISPLAYTITLE correctly in the camp page or hero page. For example, Undying/zh-hans should display his hero name -- "不朽尸王", but not. How to figure out that? --Elite stay (talk) 09:57, 29 February 2016 (UTC)


 * Haha, funny. Take a look at Special:Browse/Undying/zh-hans to see what went wrong. Unit infoboxes on non-unit pages have to be marked.


 * My suggestion for Template:Ability, Template:Item infobox, Template:Hero infobox and Template:Unit infobox would be to establish a homogeneous convention how wrappers are called and how the infoboxes are supposed to use SMW. Summoning User:Bu3ny and User:Lemoncream for opinions on the the parameter and value naming. Molldust (talk) 17:29, 29 February 2016 (UTC)

Categories
Dynamic categories would be nice, based on the type of unit. As of now, it throws them all into the creeps category, if it's a unit from the main game. How about make it categorise units into wards/buildings/summons/jungle creeps/ancient creeps/etc?  Bu3ny  (talk) 12:17, 9 March 2016 (UTC)


 * Yep, I'm runnig circles finding a proper implementation. The current one only works because "Ancient" is alphabetically before every other category. Here's a bit of insight why unit type categories should not be automatically assigned by the unit template. I already assigned the buildings manually into Category:Buildings:


 * 1) It's a huge mess because of the ancient flag and mediawiki has no proper implementation of 2 or 3 dimensional condition trees. w:mw:Extension:Loops and w:mw:Extension:LoopFunctions would enable me to do some proper programming for that kind of tasks, but they are not installed.


 * 2) Custom game modes may want their own category tree and unit types. It's not feasible to implement a non-extensible structure for a general template.


 * The other problem I have are mana/bounty/cooldown values that scale in any kind (level, aghs). If the property is set to Number, strings like 1/2/3/4 or   cannot be parsed and will be ignored. If they are set to string, they cannot be sorted into tables properly. I tend to switch to string and sacrifice the other features.


 * And finally the unit structure for the main game is more diverse than it seems. The Animal Courier is a summoned, item originated, ancient courier. Roshan is an innate, jungle originated, ancient creep. It would make sense to have the following categories:
 * Heroes + Creep-Heroes + Creeps + Wards + Couriers + Buildings
 * Ancient units (+ Non-ancient unit ?)
 * Lane presence + Jungle presence + Hero originated + Item originated
 * Summoned unit (+ Innate unit ?)


 * Molldust (talk) 13:14, 9 March 2016 (UTC)

Unit vs item infobox
Pages that are an item as well as a unit, will assign the title property twice to the page. This causes issues when wrapping the unit infobox. Affected pages I know of:
 * Animal Courier
 * Flying Courier
 * Observer Ward
 * Sentry Ward

My suggestion would be to move the unit infobox to a subpage e.g. Animal Courier (unit) and wrap it on the item page. Any opinions? Molldust (talk) 08:03, 10 March 2016 (UTC)


 * I guess there is no other choice.  Bu3ny  (talk) 13:31, 10 March 2016 (UTC)


 * One question, why are there no such issues with the ability boxes? There are multiple abilities per page but each ability box wrapper uses the correct values.  Bu3ny  (talk) 14:10, 10 March 2016 (UTC)


 * Abilities create subobjects on a page. If this is done with the courier, we'd have to call . Therefor it couldn't be wrapped by the unit infobox wrapper.
 * As a sidenote, that's why you can call wrapped abilities like that: . It would be quite awkward to implement this for the unit/hero/item infobox wrapper. Molldust (talk) 19:19, 10 March 2016 (UTC)