Talk:Mount

DPL Mount images
Tied to edit in the missing images, but not sure where the images are being pulled from - hit a dead end at Template:Mounts by update. Just now uploaded .png's for all 4 basic and filled in the individual horse articles (the Chestnut front-view is not great, is better imo), &rArr; C-Hound (Contribs • Message • Email ) 10:49, December 5, 2019 (EST)
 * The images are pulled from the respective Item: page for the mount. Looks like all the popups are there except for the fast horses now, so it may have been a caching issue?  DPL only updates once a day unless you purge the dplcache with the link at the bottom of the table.  &#x1f45f;&thinsp;ShoeMaker (Contribs&thinsp;•&thinsp;Message&thinsp;•&thinsp;Email )&thinsp;&#x1f45f; 10:21, December 6, 2019 (EST)

Changes to T:Mount and related DPL
My primary motivation is to display useful columns in the mount list on Mount page. IMO, we can (at least for now) hide minimum level and binding. Those are the same for all currently available horses. (If this information is needed on Mount page, we can add a sentence above or below the table that all mounts are ML1 and BtC.) Instead, need to add a new column, something like Source (with values like Daily Dice, Quaal of Vesve, kotb bonus items, ...). Unfortunately, the T:Mount currently does not include such a parameter, so in my expert opinion, it should be added. There are several options for how this parameter should be implemented, for example: Whaddya think? &rArr; Cru121 (Contribs • Message • Email ) 06:54, December 11, 2019 (EST)
 * Do we want to categorize horses based on the source? If yes, we should probably make it two parameters, e.g. |source=Daily Dice; |source_comment = Gold Roll 96+
 * Should we worry about multiple sources? If yes, this obviously introduces additional headaches.
 * When I created the all the pages for this, I was trying to think ahead as much as possible and thinking that there would be a need for ML at some point. I have no issues with hiding the column (or flat out removing it) for now.  I also have no problem adding some kind of location type parameter for where it's acquired and a cost type parameter that shows what the cost is to get it (96-99 Gold Roll would be a valid cost, IMHO).  I can set it up using the same logic that's in the Monster template for habitat/h_note so that multiple locations can happen.  I don't see a need for categorization by drop location at this time, but it wouldn't be hard to add later with the parameters already in use.  &#x1f45f;&thinsp;ShoeMaker (Contribs&thinsp;•&thinsp;Message&thinsp;•&thinsp;Email )&thinsp;&#x1f45f; 12:00, December 11, 2019 (EST)
 * Update: I've updated the template to accept those parameters and set up an example testcase to check out. &#x1f45f;&thinsp;ShoeMaker (Contribs&thinsp;•&thinsp;Message&thinsp;•&thinsp;Email )&thinsp;&#x1f45f; 12:49, December 11, 2019 (EST)
 * I've updated all existing mount pages with new parameters. That works nicely. However, categorization is messed up, DPL finds no results. -- &rArr; Cru121 (Contribs • Message • Email ) 10:39, December 12, 2019 (EST)
 * What categorization? "I don't see a need for categorization by drop location at this time, but it wouldn't be hard to add later with the parameters already in use."  &#x1f45f;&thinsp;ShoeMaker (Contribs&thinsp;•&thinsp;Message&thinsp;•&thinsp;Email )&thinsp;&#x1f45f; 17:54, December 12, 2019 (EST)
 * Oh, the by update categorization that was already there. Fixed. :)  &#x1f45f;&thinsp;ShoeMaker (Contribs&thinsp;•&thinsp;Message&thinsp;•&thinsp;Email )&thinsp;&#x1f45f; 18:04, December 12, 2019 (EST)