User talk:Armithaig/Workshop Tags

Why singular

imo "starting pet" can be shortened to "pet" and "pronoun set" can be abbreviated to "pronouns". also, is there a specific reason for preferring singular forms? – helado de brownie (talk) 05:20, 22 July 2020 (UTC)

☕👍 And's a couple minor ones, which words to pluralise's kinda inconsistent and you start having to ask for every tag: Should Library be pluralised or not? Tileset? Music? Resource?
The somewhat hazy rules of which things're just gonna have an 'S' slapped on the end confunoyed me when they've all got beautiful untainted singular forms.

Second'd thought about it in the context of description, usually the singular's used no matter the quantity contained: "this is an item mod", "this is a mutation mod".
Third's just less characters, with all the tags somethin' like CoQ expanded's likely to have you could shove another tag in there if you cut out all the Sssssnakes.

'Course for things that only exists in multiples like pronouns'll capitulate, shorter too. Just "asset" sounds kinda weird too, hmm.
Should probably "thunderdome" 'bout it in the channel if you disagree, don't wanna railroad us down my own tracks. Armithaig (talk) 19:59, 22 July 2020 (UTC)

Stable/Beta tags

i wanna say the main problem i can think of with stable/beta tags is they would very quickly become out of date. the devs are anticipating using beta multiple times in the upcoming months to try out new additions, and any mod labeled beta during one of those times will ultimately become stable (and possibly out of date). what isn't a moving target is the specific version they target. there might come to be many of those but i think ultimately they'd make better tags than stable or beta. – helado de brownie (talk) 01:47, 23 July 2020 (UTC)

Hmm agree's an issue 👍, for other games'd consider specific versions to be ideal but the main gristle point for me's whether any of the devs can add tags or just Brian, or if's possible to cordon it off to some community officer. They're already pushing versions by hand to 4+ different platforms n' it ain't all that uncommon for 'em to miss one (certainly wanna 12G my own ball-bearing brain when pistoning out mods to just 3 places), so'm not exactly comfortable placing that cherry on top of the layercake.

Ideally you'd break up the tags by mod compatibility but's very different from save compatibility, a patch point release only "guarantees" your save will still deserialise properly in the new version, not that no functions've changed that a mod might use (e.g. many mods broke 200.71->200.72). So you'd really have to make a tag for every version. Did find some workshops with a dropdown that'd be ideal for shoving 'em in.

As they are now at least if some bumblebutt comes into my comment section again, trumpets a 25cm hole in me for not updating my mod for beta, can point to the tiny sign: more for authors to advertise what branch they support than for users to filter outdated mods. Will ask Brian in the email all the same whether anyone'd be willing, it didn't sound like steam was that flexible (restricted + free-text tag added to dropdown) but a [XXX.XX] version field in the workshop uploader to automatically create the tag'd relieve 'em of the updating burden. Otherwise specific versions're likely better shoved into some user free-text like the title or description, but's pretty telling that with how quickly versions come and go: not many people bother with that heheh. Armithaig (talk) 03:54, 23 July 2020 (UTC)