User talk:Hunterofsalvation/Archive 2
Template:Infobox ability
hi i created Template:Infobox ability which is inspired by the keyword template, i hope you guys like that --Hanmac (talk) 09:00, 17 March 2015 (UTC)
- Nice! looks good, thx for contributing --Hunter (talk) 13:32, 18 March 2015 (UTC)
- maybe i will make a more common one which can be used for the keyword action too, that might only be a change in the include and in the keyword search. Question: can you somehow get/make images for the DragonClan symbols? i want to use them in Template:Tarkir mechanics but i didnt find them in useful quality --Hanmac (talk) 10:57, 20 March 2015 (UTC)
Hello
I realized I forgot to introduce myself to you guys. I'm the Wiki Manager assigned to MTG Salvation Wiki, so if there is anything you guys need help with (permissions, extensions, etc) feel free to let me know. --Sigilbaram (talk) 17:31, 6 April 2015 (UTC)
Functional Reprint
is Ringwarden Owl and Dragon-Style Twins similar enough to count as functional reprints? -- Hanmac (talk) 16:51, 9 June 2015 (UTC)
- Don't ask me, I'm not a good judge for that sort of thing :-) --Hunter (talk) 19:08, 9 June 2015 (UTC)
Worlds
Just noting that I removed the list of World Champions because I have one coming up w/flags (and different formatting), but I need to add the templates. That said, keeping the old one until then is definitely fine! SeneMTGSalvation (talk) 17:18, 30 August 2015 (UTC)
Rulings for new mechanics
What is your source for the rulings on Awaken and Converge? Thrawcheld (talk) 04:18, 10 September 2015 (UTC)
- I deduced them ftom Tabak's article. Maybe they should be a bit altered when the official rulings are known. --Hunter (talk) 05:32, 10 September 2015 (UTC)
- Could you make sure to add inline references in this case? I feel uncomfortable about unreferenced rulings - they could come from any random player who disagrees with a judge. I feel that "rulings" ought really to be restricted to official statements - other remarks about how they work are just remarks. I guess these qualify since Matt Tabak is Rules Manager, though. Thrawcheld (talk) 11:34, 10 September 2015 (UTC)
Protected edit request
I took another tilt at the Template:Navbox today and it looks like (for very good security reasons) there's no way to force the appropriate style information directly into the template/module without a staggering amount of work to mentally unroll Wikipedia's CSS. Could we try adding it directly to MediaWiki:Common.css? The relevant code is as follows, and could be pasted anywhere outside of the curly brackets in the top half of the file. If this edit does what I'm hoping, the blurb at the top of Test about "Block settings/Other planes" should become a properly finished navigation footer. --Corveroth (talk) 23:54, 10 November 2015 (UTC)
.navbox{border:1px solid #aaa;width:100%;margin:auto;clear:both;font-size:88%;text-align:center;padding:1px}.navbox-inner,.navbox-subgroup{width:100%}.navbox-group,.navbox-title,.navbox-abovebelow{padding:0.25em 1em;line-height:1.5em;text-align:center}th.navbox-group{white-space:nowrap;text-align:right}.navbox,.navbox-subgroup{background:#fdfdfd}.navbox-list{line-height:1.5em;border-color:#fdfdfd}.navbox th,.navbox-title{background:#ccccff}.navbox-abovebelow,th.navbox-group,.navbox-subgroup .navbox-title{background:#ddddff}.navbox-subgroup .navbox-group,.navbox-subgroup .navbox-abovebelow{background:#e6e6ff}.navbox-even{background:#f7f7f7}.navbox-odd{background:transparent}table.navbox{margin-top:1em}table.navbox table.navbox{margin-top:0}table.navbox + table.navbox{margin-top:-1px}.navbox .hlist td dl,.navbox .hlist td ol,.navbox .hlist td ul,.navbox td.hlist dl,.navbox td.hlist ol,.navbox td.hlist ul{padding:0.125em 0}.navbar{display:inline;font-size:88%;font-weight:normal}.navbar ul{display:inline;white-space:nowrap}.mw-body-content .navbar ul{line-height:inherit}.navbar li{word-spacing:-0.125em}.navbar.mini li span{font-variant:small-caps}.infobox .navbar{font-size:100%}.navbox .navbar{display:block;font-size:100%}.navbox-title .navbar{float:left;text-align:left;margin-right:0.5em;width:6em}.collapseButton{float:right;font-weight:normal;margin-left:0.5em;text-align:right;width:auto}.navbox .collapseButton{width:6em}.mw-collapsible-toggle{font-weight:normal;text-align:right}.navbox .mw-collapsible-toggle{width:6em}
- I'm not sure what you are asking? Which page should I edit for you? And why is this a protected edit? --Hunter (talk) 04:41, 11 November 2015 (UTC)
- Template:Navbox is a useful template for consistent navboxes, borrowed straight from Wikipedia. MediaWiki:Common.css is one of the major stylesheets governing the appearance of this website, and because it's so important and universal, it's protected. Our copy of the navbox template is broken, largely because Wikipedia has style rules that our Common.css is lacking. The above line of code, copied in its entirety, should contain the style rules necessary to make the navbox template mostly functional (and it's highly specific, so it won't touch anything outside of that template: note all of the references to ".navbox" and ".navbar"). So, I'm asking that you add that line of code to Common.css. As long as it's pasted outside of existing curly brackets, nothing else will be effected. --Corveroth (talk) 06:19, 11 November 2015 (UTC)
- Done. Did I do that right? I'm a total layman with this stuff --Hunter (talk) 06:32, 11 November 2015 (UTC)
- At a glance, that looks like it worked! I'll assemble some more rigorous tests and see if we need anything else. On the very unlikely off-chance you notice a problem elsewhere, feel free to revert at will (just please let me know what broke!). And of course, thank you. =) --Corveroth (talk) 06:34, 11 November 2015 (UTC)
- One more chunk! This should govern the appearance of individual rows within the navboxes. Again, this is explicitly targeted to narrow uses, so unless someone else starts playing with Scribunto/Lua, this shouldn't affect anything else on the wiki at large. This can be pasted right below the last. --Corveroth (talk) 07:18, 11 November 2015 (UTC)
- At a glance, that looks like it worked! I'll assemble some more rigorous tests and see if we need anything else. On the very unlikely off-chance you notice a problem elsewhere, feel free to revert at will (just please let me know what broke!). And of course, thank you. =) --Corveroth (talk) 06:34, 11 November 2015 (UTC)
- Done. Did I do that right? I'm a total layman with this stuff --Hunter (talk) 06:32, 11 November 2015 (UTC)
- Template:Navbox is a useful template for consistent navboxes, borrowed straight from Wikipedia. MediaWiki:Common.css is one of the major stylesheets governing the appearance of this website, and because it's so important and universal, it's protected. Our copy of the navbox template is broken, largely because Wikipedia has style rules that our Common.css is lacking. The above line of code, copied in its entirety, should contain the style rules necessary to make the navbox template mostly functional (and it's highly specific, so it won't touch anything outside of that template: note all of the references to ".navbox" and ".navbar"). So, I'm asking that you add that line of code to Common.css. As long as it's pasted outside of existing curly brackets, nothing else will be effected. --Corveroth (talk) 06:19, 11 November 2015 (UTC)
.hlist dl,.hlist ol,.hlist ul{margin:0;padding:0} .hlist dd,.hlist dt,.hlist li{margin:0;display:inline} .hlist.inline,.hlist.inline dl,.hlist.inline ol,.hlist.inline ul,.hlist dl dl,.hlist dl ol,.hlist dl ul,.hlist ol dl,.hlist ol ol,.hlist ol ul,.hlist ul dl,.hlist ul ol,.hlist ul ul{display:inline} .hlist dt:after{content:":"}.hlist dd:after,.hlist li:after{content:" · ";font-weight:bold}.hlist dd:last-child:after,.hlist dt:last-child:after,.hlist li:last-child:after{content:none} .hlist dd.hlist-last-child:after,.hlist dt.hlist-last-child:after,.hlist li.hlist-last-child:after{content:none} .hlist dd dd:first-child:before,.hlist dd dt:first-child:before,.hlist dd li:first-child:before,.hlist dt dd:first-child:before,.hlist dt dt:first-child:before,.hlist dt li:first-child:before,.hlist li dd:first-child:before,.hlist li dt:first-child:before,.hlist li li:first-child:before{content:" (";font-weight:normal}.hlist dd dd:last-child:after,.hlist dd dt:last-child:after,.hlist dd li:last-child:after,.hlist dt dd:last-child:after,.hlist dt dt:last-child:after,.hlist dt li:last-child:after,.hlist li dd:last-child:after,.hlist li dt:last-child:after,.hlist li li:last-child:after{content:") ";font-weight:normal} .hlist dd dd.hlist-last-child:after,.hlist dd dt.hlist-last-child:after,.hlist dd li.hlist-last-child:after,.hlist dt dd.hlist-last-child:after,.hlist dt dt.hlist-last-child:after,.hlist dt li.hlist-last-child:after,.hlist li dd.hlist-last-child:after,.hlist li dt.hlist-last-child:after,.hlist li li.hlist-last-child:after{content:") ";font-weight:normal} .hlist ol{counter-reset:listitem}.hlist ol > li{counter-increment:listitem}.hlist ol > li:before{content:" " counter(listitem) " ";white-space:nowrap}.hlist dd ol > li:first-child:before,.hlist dt ol > li:first-child:before,.hlist li ol > li:first-child:before{content:" (" counter(listitem) " "} .plainlist ol,.plainlist ul{line-height:inherit;list-style:none none;margin:0}.plainlist ol li,.plainlist ul li{margin-bottom:0} .navbox{ border:1px solid #aaa;width:100%;margin:auto;clear:both;font-size:88%;text-align:center;padding:1px}.navbox-inner,.navbox-subgroup{width:100%}.navbox-group,.navbox-title,.navbox-abovebelow{padding:0.25em 1em; line-height:1.5em;text-align:center}th.navbox-group{ white-space:nowrap; text-align:right}.navbox,.navbox-subgroup{background:#fdfdfd; }.navbox-list{line-height:1.5em;border-color:#fdfdfd; }.navbox th,.navbox-title{background:#ccccff; }.navbox-abovebelow,th.navbox-group,.navbox-subgroup .navbox-title{background:#ddddff; }.navbox-subgroup .navbox-group,.navbox-subgroup .navbox-abovebelow{background:#e6e6ff; }.navbox-even{background:#f7f7f7; }.navbox-odd{background:transparent; }table.navbox{margin-top:1em; }table.navbox table.navbox{margin-top:0; }table.navbox + table.navbox{margin-top:-1px; }.navbox .hlist td dl,.navbox .hlist td ol,.navbox .hlist td ul,.navbox td.hlist dl,.navbox td.hlist ol,.navbox td.hlist ul{padding:0.125em 0; }
- While you're editing style sheets, could you please check out the talk page? There's a couple of other requested edits pending. Thrawcheld (talk) 13:35, 11 November 2015 (UTC)
- OK? --Hunter (talk) 18:26, 11 November 2015 (UTC)
- PERFECT! I'll let Thrawcheld check their intended applications, but that looks to be everything I needed. Compare Template:Planes_of_the_Multiverse/Sandbox to Template:Planes_of_the_Multiverse (especially their source wikitext) to see what we've accomplished. Now we have a generalized way to make those footers without needing to carefully craft tables, or worry about inner templates, or specify style options. Thank you, Hunter! --Corveroth (talk) 18:30, 11 November 2015 (UTC)
- OK? --Hunter (talk) 18:26, 11 November 2015 (UTC)
CSS class for column-count for lists
I don't know if you are the right person for that, but while searching for better ways to style this, Token/Full List, the place where the card list is split in three columns, i did come to the css style column-count, the problem is that i cant use it there because it does need to applied to the ul element which is auto-generated by the list. so my request: add the following block to the CSS of the side and i can use classes to make that dynamic.
.ul-column-count-3 > ul { -webkit-column-count: 3; /* Chrome, Safari, Opera */ -moz-column-count: 3; /* Firefox */ column-count: 3; }
so i can add "ul-column-count-3" as class to the td and it does style the ul element with the card list.
- It's all gibberish to me, but if you think it improves the wiki.... Done. --Hunter (talk) 16:06, 18 December 2015 (UTC)
Hm we might also add a count-2 variant too.
apropos what do you think of the idea to move part of the table into lists so the changes doesn't need to be done for all lists like {{Elemental Tokens}}? --Hanmac (talk) 09:40, 18 December 2015 (UTC)
- That might be a good idea, because now the main token list is not as up to date as the creature type pages. As it stand it is always double work and may differ. --Hunter (talk) 16:06, 18 December 2015 (UTC)
Another CSS rule might help to prevent the name splitting on column break:
.ul-column-count-3 > ul > li { page-break-inside: avoid; }
i don't know how it would be done in other browsers. --Hanmac (talk) 12:57, 15 March 2016 (UTC)
- To make it work in more browsers, please also add Talk:Token/Full List#Column break|this code. Thanks. —Fenhl 17:43, 21 June 2016 (UTC)
Mana symbol templates
Could you unprotect the templates Template:W, Template:U, Template:B, ..., please? I would like to change the images to another better ones (those that are in the Template:Main Header). --Tuamir (talk) 12:26, 23 December 2015 (UTC)
- Done, be carefull though. --Hunter (talk) 16:29, 23 December 2015 (UTC)
- Please, could you also unprotect the Template:Manawubrg and the numerical mana symbol templates? --Tuamir (talk) 02:02, 24 December 2015 (UTC)
- Sorry, but I also need the snow, tap, untap, x, y, z templates become unprotected. --Tuamir (talk) 15:07, 24 December 2015 (UTC)
- On that note, the following mana templates are still under protection, but should be defunct by redirecting to their shorter version: Manabu, Manabw, Managb, Managr, Manarb, Manaru, Manaug, Manauw, Manawg, Manawr. - Yandere Sliver 00:58, 25 December 2015 (UTC)
- I don't know currently all mana symbols have the same look and feel. If you update the main 5, I would like to see the generic( X, 1, 2, 3), the hybrids and phyrexian updated as well. -- Yandere Sliver (talk) 12:38, 23 December 2015 (UTC)
Regular expressions
Do we have any form of regular expression use in this wiki? - Yandere Sliver 16:08, 23 December 2015 (UTC)
- What do you mean? :-) --Hunter (talk) 16:34, 23 December 2015 (UTC)
- We have the MTG Salvation Wiki:Manual of Style|Manual of Style if that's what you mean, but it hasn't been updated for a long while. --Hunter (talk) 16:34, 23 December 2015 (UTC)
- Something like this: RegexParserFunctions - Yandere Sliver 16:58, 23 December 2015 (UTC)
- Oh, that's not my cup of tea. Some of the current users have more expertise with things like that. --Hunter (talk) 18:45, 23 December 2015 (UTC)
- We do have access to Lua via the Scribunto extension, so we could certainly implement something similar. Would you like me to build such a module? What's your plan for it? --Corveroth (talk) 18:54, 23 December 2015 (UTC)
- My idea was to display strings like {W} from the comprehensive rules with . You can do this for every single sting, or you write a regular expression for this. But perhaps the pure form is prefered? - Yandere Sliver 21:20, 23 December 2015 (UTC)
- I considered doing so when I implemented the module that now underlies the CR template. As you're aware, it's a trivial technical task. I opted not to for the sake of pure quotation of the source material, in order to reinforce that those text representations are fully canonical. I have some ideas I'll mull over - in the meantime, feel free to offer feedback over at Module_talk:CR. --Corveroth (talk) 23:27, 23 December 2015 (UTC)
- My idea was to display strings like {W} from the comprehensive rules with . You can do this for every single sting, or you write a regular expression for this. But perhaps the pure form is prefered? - Yandere Sliver 21:20, 23 December 2015 (UTC)
- We do have access to Lua via the Scribunto extension, so we could certainly implement something similar. Would you like me to build such a module? What's your plan for it? --Corveroth (talk) 18:54, 23 December 2015 (UTC)
- Oh, that's not my cup of tea. Some of the current users have more expertise with things like that. --Hunter (talk) 18:45, 23 December 2015 (UTC)
- Something like this: RegexParserFunctions - Yandere Sliver 16:58, 23 December 2015 (UTC)
- We have the MTG Salvation Wiki:Manual of Style|Manual of Style if that's what you mean, but it hasn't been updated for a long while. --Hunter (talk) 16:34, 23 December 2015 (UTC)
Blurb
Just curious, where did you get the story blurb from for Shadows Over Innistrad? —The preceding unsigned comment was added by 23.28.100.245 (talk • contribs).
MTGSCards bug
Could you please contact the Hydra Platform Team about this? —Fenhl 14:38, 18 March 2016 (UTC)
- Sorry, I don't know what the Hydra Platform Team is?! Not my area of expertise --Hunter (talk) 15:52, 18 March 2016 (UTC)
- I will post it in the wiki admin chat. Some of use should know what to do... (Not me :P) - Yandere Sliver 16:02, 18 March 2016 (UTC)
- Thanks. I don't know who the Hydra Platform Team is either (I'm assuming they're Curse staff), but Special:Version says they maintain the MTGSCards extension which provides the
<c>
syntax. —Fenhl 16:37, 18 March 2016 (UTC)
- Thanks. I don't know who the Hydra Platform Team is either (I'm assuming they're Curse staff), but Special:Version says they maintain the MTGSCards extension which provides the
New bot users
It seems each day there are a bunch of new users created by some bot. How can this be stopped? --Tuamir (talk) 16:56, 10 April 2016 (UTC)
- I wish I knew :-) They don't seem to edit, though --Hunter (talk) 19:26, 10 April 2016 (UTC)
- I don't know how this works. Is the bot a code situated in some page in the wiki? Or is the bot something exterior of the wiki? If is the later, it could mean that the conditions to registry a new user are weak and easy to be automatized from another place.--Tuamir (talk) 21:41, 16 April 2016 (UTC)
- We've been chatting about this on the forums. The registration is a few levels above our head (Gamepedia, or perhaps Mediawiki), but for now, we're safe for the reasons discussed in that thread. So long as that holds, there's no impact beyond a bit of noise in the recent changelog, which is perfectly tolerable. --Corveroth (talk) 22:38, 16 April 2016 (UTC)
- I don't know how this works. Is the bot a code situated in some page in the wiki? Or is the bot something exterior of the wiki? If is the later, it could mean that the conditions to registry a new user are weak and easy to be automatized from another place.--Tuamir (talk) 21:41, 16 April 2016 (UTC)
Hanweir
now that Hanweir becomes a legendary creature, would it make sense for it to finally have its own page where the info about it is collected (with slightly removing it from other pages)? and if it gets a own page, where should be put it in {{Innistrad}}? is it still a Location and should be a sub-entry in Nearheath, or should it be listed in Characters or both? --Hanmac (talk) 18:24, 25 June 2016 (UTC)
- If you think you can expand on the available info, go ahead. For categories sake it would be both a character and a location, I think. For the template, I would choose "other" :-) --Hunter (talk) 03:04, 26 June 2016 (UTC)
- Well I think it could become its own page. It is not a location anymore... It is a character. More or less... I think Nearheath should definitely mention Hanweir. But seriously, we have enough pages with less information. - Yandere Sliver 19:23, 25 June 2016 (UTC)