User talk:Blackice

From Guild Wars 2 Wiki
Jump to navigationJump to search

Armour nav[edit]

Thanks for tossing it onto the Harrier's Bounty Hunter's Gauntlets for us. That prompted me to start getting it onto other pages where it also belongs :D. G R E E N E R 04:47, 16 October 2017 (UTC)

Dialogue subpages[edit]

Hi there, I noticed that you created a [[Shadows Watcher/Dialogue|dialogue subpage]] for Shadows Watchers. Generally, subpages like this are only used for historical dialogue that isn't in the game any more. Current dialogue should be on the main article for each watcher NPC. Edit: I've realised that you were using it as a transclusion. While that's a clever solution for 4 NPCs with near-identical dialogue, it was causing errors on three of the watcher articles because they aren't all called "Mage". It's possible to fix this problem with some simple code, but that would still be more effort than just copy-pasting the dialogue into the articles, and would make it difficult for other, inexperienced editors to figure out how to add to or correct the dialogue. --Idris (talk) 14:01, 22 October 2017 (UTC)

Hey ho, thanks for notifying me. I got interrupted earlier today and couldn't quite finish the watcher articles, so some errors (i.e. the term "Mage" used on all four pages) remained. The errors on [[Shadows Watcher/Dialogue]] and [[Shadows Watcher/Quotes]] should be fixed now. I think it would be preferable to transclude the lengthy blocks of dialogue text, which is pretty much identical for all four NPCs. Keeping four pages in sync while fixing errors/typos/etc. seems annoying to me. Maybe these four should have been merged into a single page, maybe something like "Shadows Watcher". --Blackice (talk) 16:51, 22 October 2017 (UTC)
Using a transclusion does seem like a nice solution, but I think a lot of users will just get confused if they click on "edit" and see {{/Some_random_page/Dialogue}} instead of the actual dialogue -- many of them won't have the first clue where to go looking for the correct article to edit. I think this outweighs the inconvenience of having to edit four pages at once.
Merging the four NPCs into a single NPC is a good idea though, and one I considered. I'm on the fence about it because I'm not sure how we'd handle the four different names in the infobox, but making up a generic name might be fine. --Idris (talk) 18:09, 22 October 2017 (UTC)
They're different NPCs, so no they shouldn't be merged. Even if they share dialogue - there are many NPCs that share dialogue, but because they're different NPCs with different names and different locations, we have full separate pages for each. Transclusion seems like a needless addition as well, IMHO. Konig (talk) 18:10, 25 October 2017 (UTC)

Coordinates[edit]

Just a heads up, you don't need to use approximate coordinates from GW2Timer for map icons -- the wiki's got your back. Zoom in and click on a point of interest or other map icon to get its id and coordinates. :) --Idris (talk) 18:57, 23 October 2017 (UTC)

Hi and thanks for the info. I replaced my GW2Timer coordinates and I'll use this widget from now on. :) --Blackice (talk) 19:10, 23 October 2017 (UTC)

Images[edit]

Hello, you don't need to make a new screenshot for every creature - most of them shares model/colors, so check Guild Wars 2 Wiki:Projects/Shared Model Project, it will greatly helps you and also saves time! Sime (talk) 20:41, 26 October 2017 (UTC)

Hi Sime, thanks for linking the shared models. I kinda think taking screenshots of enemies is fun (maybe I played too much Pokemon Snap as a kid) and it's relatively quick compared to filling out loot tables. Don't worry though, I'll try to avoid unnecessary image/file bloat. :) --Blackice (talk) 08:48, 27 October 2017 (UTC)
Just want to say Pokemon Snap was one of my favorite games as a kid and I'm trying to find where my copy is currently haha. Also gonna leave you with a tip: when you do upload pictures, you don't need to include the build number, that's really only needed for patch notes. ;) - Doodleplex 18:23, 27 October 2017 (UTC)
If you have a Wii, Pokémon Snap is available through the online store. SarielV 20 x 20px 22:09, 24 November 2017 (UTC)

Screenshots[edit]

Hey, I just happened to catch your upload of File:Brightwater Inlet.jpg. Absolutely beautiful shot of the area, thanks! G R E E N E R 18:28, 24 November 2017 (UTC)

Thanks! Nice to see that someone enjoys it. :) -- Blackice (talk) 18:42, 24 November 2017 (UTC)

Can I ask why you replaced my screenshot of Kanuz Cache? Was there something wrong with the one we've been using for two months? Greyling (talk) 22:52, 24 November 2017 (UTC)

The one I uploaded is a daytime screenshot with slightly improved brightness and contrast, and a notably lower file size. I should have put that info into the file change notes, so it would have appeared in the file history, but unfortunately I messed that up. If you're not happy with the new screenshot, feel free to revert it, or upload a new one with daytime lighting. :) -- Blackice (talk) 23:00, 24 November 2017 (UTC)

Spacing and Caps[edit]

It doesn't really matter if things are capitalized or lowercase in infoboxes normally, they're set up to accept both so I wouldn't bother changing it for the most part. Also I've noticed you have a habit of adding spaces after semi-colons on NPC pages and such; unless it's in a sentence like this one, semicolons really shouldn't have a space after them, it's unnecessary whitespace. - Doodleplex 20:32, 16 December 2017 (UTC)

If you are referring to the wrapped weapons skin pages, which I updated previously, several of these had the weapon type capitalized in the lead paragraph, like "... is an Axe skin.", which I found slightly weird. And I switched some stuff in the infobox to lower case in one go, because it's really just personal preference to use the lower case style for template params and arguments (unless using page names, etc.). Oh, and about the semicolons: I just habitually add a space for the definition lists, like for regular list items. Sort of like on the MediaWiki help page for lists. I can try to avoid that, but sometimes I just forget... —Blackice (talk) 21:08, 16 December 2017 (UTC)
if you're going to be all OCD about caps, https://wiki.guildwars2.com/index.php?title=Wrapped_Longbow&curid=227196&diff=1609783&oldid=1608342 wtf lower case weapon set names and weapon types. -Chieftain AlexUser Chieftain Alex sig.png 21:30, 16 December 2017 (UTC)
Sorry, I wasn't aware that these arguments are supposed to be upper case. Admittedly, the Template:Skin infobox documentation is pretty clear about this style. I guess I'll fix the affected skin pages. —Blackice (talk) 12:20, 17 December 2017 (UTC)

#titleparts[edit]

Hi - about #titleparts in templates; actually we use it on this wiki to encode names with apostrophes and other such url encoded characters. SMW often fucks up without it. -81.154.21.211 16:09, 20 December 2017 (UTC)

You're on your break, Alex, so let us break stuff while you're gone! >:( User Incarnazeus Signature.pngtalk 18:05, 20 December 2017 (UTC)
Thanks for correcting my mistake. :)
In case someone else is reading this and ends up confused: This is about to this diff. Turns out that #titleparts actually decodes character references produced by {{PAGENAME}}, for example:
  • '{{PAGENAME:'test'}}' → ''test''
  • '{{#titleparts: {{PAGENAME:'test'}} }}'test
There's also a warning box on mw:Help:Magic words#Page names about this issue, which explicitly recommends #titleparts. —Blackice (talk) 18:49, 20 December 2017 (UTC)

Exclamation points[edit]

A quick search turned up nearly 75 events using ‘em, and unless I missed something recently, I was told at some point that it’s okay for them to be left in. Just wanted to let you know. =) - Doodleplex 21:13, 12 March 2018 (UTC)

We use exclamation and question marks, but not full stops in event names (reasoning behind it is that both those marks are much more rare than full stops which are basically in every event). —Ventriloquist 21:29, 12 March 2018 (UTC)
I don’t remember any event having a question mark(which we couldn’t use until recently), but yeah that was it, thanks Vent! - Doodleplex 21:49, 12 March 2018 (UTC)
Yeah, I noticed the missing periods and interpreted this as punctuation being omitted altogether. Sorry.
Btw, question marks seem to be only used in the names of certain guild puzzle events, like "Can you puzzle out the mystery of Proxemics Lab?", as seen here. --Blackice (talk) 21:57, 12 March 2018 (UTC)

Unnamed skills as text errors[edit]

My understanding of text errors is that we use that term for any instance of text not being what it should be, and imo, missing skill/object/effect names fall under that definition. I might be wrong though, and it's certainly possible that some skills are deliberately unnamed, so I won't contest your removal of that autocategory from the skill infobox. :) (You might want to take a look at Unknown and see what you think about that counting as a text error though.) --Idris (talk) 15:01, 23 March 2018 (UTC)

The issue seems to be that Category:Text_errors is somewhat ambiguous. I interpreted it as being used for errors in quoted text, via {{sic}}. I think it would be best to use only Category:Unnamed_objects and Category:Unnamed_skills on the related pages, and maybe make both of these subcategories of Category:Text_errors. --Blackice (talk) 15:50, 23 March 2018 (UTC)
I'd been thinking that it was ambiguous too, and I considered the same solution as you suggested. I won't edit anything just yet, since I'm half-expecting someone to jump in and give me a bollocking for messing with the infoboxes, but I'm in favour of the change, if you feel like you want to go for it. :) --Idris (talk) 16:08, 23 March 2018 (UTC)

"The markup is more complex"[edit]

Nahh, it's fine. If anything, it looks simpler. You can get away with a bit more complexity on formatting guides anyway, since the only people who should be editing them are people who know what they're doing. --Idris (talk) 12:33, 28 March 2018 (UTC)

Guild cavalier weapons[edit]

I don't agree with this edit. I think they're worth documenting on a separate page.

Also I feel that wildcards in SMW queries should be avoided where possible. -Chieftain AlexUser Chieftain Alex sig.png 11:51, 5 August 2018 (UTC)

Hmm, previously, there were three pages: Cavalier weapon skins, Cavalier weapons, and Guild Cavalier weapons. Isn't that a bit much? Seems confusing to me. I added a weapon skin set table to this page, so we'll have links for all of the skin pages. And everything in one place.
Also, the weird gallery query with the wildcards is really only required for this one specific weapon set. --Blackice (talk) 12:09, 5 August 2018 (UTC)
Ah. I agree with the removal of the "_weapons" suffix. Perhaps the Guild Cavalier stuff should be on a separate page named "Guild Cavalier weapon skins".
Also, if you are on the wiki discord you may have noticed a bunch of noise about edits to default item parameter causing whitespace issues on Chrome and IE -- please be careful when making big edits to the most widely used template on the wiki - I recommend testing stuff in a sandbox first. -Chieftain AlexUser Chieftain Alex sig.png 15:22, 5 August 2018 (UTC)
So seems like you fixed the issue with the default item parameter template. Thanks!
I think the weird whitespace was caused by MediaWiki inserting non-breaking spaces into definition list when the markup is just in one line. For example ; term : description inserts a non-breaking space after term, but ; term: description doesn't for some reason… I did test the edits somewhat, but this one slipped past me… I vaguely remember using the sandbox approach once for [[Template:Skill infobox/testcases|for the skill infobox]], but the issue was that I lost interest extremely quickly… --Blackice (talk) 17:54, 5 August 2018 (UTC)
I think the issue in this case was that after/before every html comment you left a space, and you put the definition lists with miles of whitespace before and after.... -Chieftain AlexUser Chieftain Alex sig.png 18:02, 5 August 2018 (UTC)
Yeah, there were some spaces too much, I think. Here's a table:
Inserts non-breaking space "Correct"
; term <!--
--> : definition  
; term<!--
-->: definition  
Using these comments to split up long lines was probably a garbage idea in the first place. I thought it would make editing easier, but if you have to pay that much attention to whitespace there's really no point in it. --Blackice (talk) 18:38, 5 August 2018 (UTC)
(Reset indent) Just to say thank you very much for restoring the set parameters on the skin pages. Much appreciated. -Chieftain AlexUser Chieftain Alex sig.png 20:08, 5 August 2018 (UTC)