Talk:Store hat list

Last cleared: 2018-10-30 20:30:38 (UTC)
( See the [History] option/tab for previous cleared talks or topics )
( Use the [Add topic] option/tab to start a new talk topic )

Maintaining separate Store-hat pages

Based on the availability of subobject-properties I'm kinda wondering if maintaining separate store-hat pages is still needed or generally useful.
Reasoning: With subobjects all store-hats data could be set/declared at the main store-hat page itself, and the separate store-hat pages don't seem to contain any real special info for any of the given store-hats.
The subobjects-block (ie: fields x records) might be a bit big, depending on what fields are maintained (general user/edit friendliness).
The alternative would be to still have separate store-hat pages. But only for setting related store-hat property-data, without actually displaying hat related text/info. (in this case I'm thinking about using sub-pages under the main store-hats page)
Whatever way, if any, will be taken. The current store-hat table data should probably be moved into there related store-hat pages. ... but for that I think a separate store-hats template is in order.
Anyway, just some potential things to ponder on for store-hats for the time being (while I try to re-focus on some other stuff I keep putting off (RoB and local/personal stuff))
--.MvGulik. 21:28, 30 October 2018 (EDT)

Store-hat pondering

• name: Main store-item id string.
• type: Hat/Other, subsc/no-subsc.
• page-object: linked/given by used page-name. (if saved as page)
• icon image: use name.
  • img-name-format: Currently just bare 'page-name' (+".png").
    • Potential keywords(folder style): "store-hat/item", "store hat", "storehat", "icon".
• in-game images: Currently added as page content. ... to be looked at.
  • Cases: Wearing, On-wall.
    • Potential keywords: "wearing"(implies "in-game"), "on-wall"/"on wall"/"on wall"(implies "in-game"), "N":Potential numbering in case of more than one.
    • User descriptions: DROP(maintainability), general store-text will do.
• Release date: ISO-date.
• Availability: DROP(maintainability)

• • • Release patch: Patch id/name.
  • Subscription related: yes/no.
    • Subscription info data/text: ... to be looked at potentially DROP(maintainability) or store in some 'history' section.
    • Price: (none subscription items) INT

• • Categories: to be looked at.
  • How to Acquire: ... Shared or move/redirect.

--.MvGulik. 18:51, 28 March 2020 (EDT)

Store Hat separate namespace

Is it possible to create a particular namespace for store hats, so that they would pile up there (like Legacy:pages successfully do) and do not appear in Random Page and default Search bar?
Most likely you've already thought about it. If so, why hasn't you done it already? (Not going to discuss the major importance of impact store hats have on gameplay.)

Additional namespace's possible, Sure. Just not by me. Nor do I see a general pressing need for it. One planned idea is to get rid of the separate hat pages, and dump it in one or two pages (although that leaves little room for additional hat preview images, to name a potential down side). The Store_hat_list/csv_data_dump page contains a cleaned-up store-hats data dump of potential maintainable store-hats data (which was a shitload of work). --.MvGulik. 02:32, 22 June 2021 (UTC)

Keeping pages separated is useful though: loading 100+ 200x300 preview images in 1 page would be a disaster. Store:Ridiculous_Hat_List and Party Like It's 1999 (talk) 08:28, 22 June 2021 (UTC)