User talk:Abscisin

Spoiler template

Hey, the {{spoiler}} CSS has been cached long enough to work for about all users. I discreetly put it on the infoboxes we talked about and also here as an example of how it looks like in body text. What do you think? - epeli (talk) 04:53, 7 January 2017 (CST)

It's perfect! Thanks, this definitely takes care of the infobox problem.

The Nucleus example is a bit more interesting. In daylight, the black spoiler on black background was pretty much completely invisible for me. If you haven't told me what to look for, I probably wouldn't have realized there was anything there, and would have just dismissed that section as a placeholder. But I don't usually adjust the brightness of my screen during the day, so maybe this is not a problem for most people. And it's only when there are just a few words like in this case that it becomes much too easy to miss if one doesn't look hard enough, with longer texts this shouldn't be a problem at all. Maybe only partially hiding it would help, for example here by keeping "See" unspoilered and hiding only the quest. Just to give a small warning that there is something there.

In what cases should we use this, and when the old hidden section? - Abscisin (talk) 18:40, 9 January 2017 (CST)

Like you've pointed out, best practice would be to use the spoiler template for hiding infobox text and short inline spoilers such as this in the middle of sentence or paragraph. Using it that way should also take care of any contrast issues as there will be an obvious gap in the text.

The hidden section works better when you need to hide longer text such as a whole paragraph or multiple paragraphs. In hindsight, using spoiler on Nucleus wasn't a very good example (I thought of spoilering only part of the text, not sure why I made it that way), but at least it confirmed that there is a contrast issue! - epeli (talk) 07:36, 10 January 2017 (CST)

Patrollers?

If you were wondering WTF this patroller thing is, it just means we trust your edits and they are now automatically marked as patrolled and I won't have to check each and every one of them. (Finally got Styg to add a new usergroup, yay!) You can also patrol edits of normal users (in case we ever see some of those, lol) through recent changes. - epeli (talk) 07:43, 11 August 2017 (CDT)

Would this be a good time to reaffirm that all of my edits are made in good faith, even if down the line it turns out some were completely incorrect? - Abscisin (talk) 17:47, 24 August 2017 (CDT)

Damage templates

Just a heads up, I updated the damage type templates to accept an optional parameter for displaying damage numbers, so editors won't have to use/remember those clunky color codes and things stay consistent if the damage type coloring templates are changed.

Currently the output for {{cold|8-9}} looks like Cold: 8-9 so the number is preceded by the damage type name, at least for now. - epeli (talk) 11:28, 23 September 2017 (CDT)

Thanks, I've been counting on you to make this change. Those color codes were irritatingly blinding without an option to set the opacity. Having both the name and the damage written out in infoboxes makes them look a little cluttered, but it will suffice. Abscisin (talk) 14:28, 9 October 2017 (CDT)

{{damagetype}} is now a bit more flexible for general use. 8-9 Cold, 11-22 or anything goes. Character infobox is also a bit more spacious and health is now optional, so the bar won't appear on all those mentioned character articles. - epeli (talk) 09:05, 11 October 2017 (CDT)

Nice! I'll give it a spin. - Abscisin (talk) 16:23, 14 October 2017 (CDT)