User talk:Musha

From Guild Wars 2 Wiki
Jump to: navigation, search

Avada Kadavra on Red link![edit]

Hai, welcome to the wiki :) --User:Nautaut /(t) 16:31, 13 May 2010 (UTC)

Did you just,... Use a Harry Potter-spell? 0_0. --Naoroji My Contributions 16:37, 13 May 2010 (UTC)
COPYRIGHT joking.--Neil2250 , The DeleterUser Neil2250 sig icon5.png 16:40, 13 May 2010 (UTC)
No actually, I just generated two random words using mostly 'a' and 'z'. --User:Nautaut /(t) 16:46, 13 May 2010 (UTC)
Agressive Zebra.--Neil2250, The Deleter User Neil2250 sig icon5.png 16:58, 13 May 2010 (UTC)


The event infobox automatically categorizes events by zone, in case you didn't know. It's purely redundant to add it to the bottom. Manifold User Manifold Neptune.jpg 23:33, 14 December 2012 (UTC)

I did not know that, but I think it's fantastic that it does that! Thank you for letting me know. :) --MushaUser Musha Sigc.png 09:29, 15 December 2012 (UTC)


why'd you put multiple parameters? Events only have one start npc--Relyk ~ talk > 03:35, 14 February 2013 (UTC)

Almost all of them do, but allow me to direct your attention to Assault Foulbear Kraal by killing its leaders before the ogres can rally. This may be the only event with multiple start npcs, but still, because it has more than 1 start npc, I needed to change the infobox to fit them both in. --MushaUser Musha Sigc.png 03:38, 14 February 2013 (UTC)
I wish had #arraymaps already, would've handled it easily.--Relyk ~ talk > 04:58, 14 February 2013 (UTC)
And I'm totally going to nickpick, do dynamic event instead of Dynamic event.--Relyk ~ talk > 05:04, 14 February 2013 (UTC)
Isn't convention, when inserting links, to use the literal title of the page you're linking to? --MushaUser Musha Sigc.png 05:07, 14 February 2013 (UTC)
In prose, you keep it lowercase since it's not a proper noun. The titles for NPCs, equipment, skills, traits, and events use the literal link because they are proper nouns or to avoid confusion. It's really the equivalent of [[Dynamic event|dynamic event]]. You can get into muddy water with articles like items though.--Relyk ~ talk > 05:23, 14 February 2013 (UTC)
MediaWiki is case-insensitive on the first character of article names. dynamic event and Dynamic event are 100% equivalent. This was done intentionally to do as Relyk says - use article names in prose without having to introduce Random capital Letters. —Dr Ishmael User Dr ishmael Diablo the chicken.png 05:45, 14 February 2013 (UTC)
Works for me. --MushaUser Musha Sigc.png 06:37, 14 February 2013 (UTC)

Stop the bandit thief from stealing the pumphouse blueprints[edit]

Did the event run properly/normally or was if weird? When I played it the thieves kept spawning but cold not be killed. Claret 02:39, 29 March 2013 (UTC)

It was weird. It's definitely bugged. I was able to complete the event, but the thief respawned immediately back at his starting spot, but the event did not restart. I killed him several times and each time he respawned back at his spot, so I just let him do his thing and I reported the bug. --MushaUser Musha Sigc.png 03:45, 29 March 2013 (UTC)

"Discovered" not historical[edit]

Hi, you removed the historical tag from a couple of event s in Plains of Ashford with the comment "events discovered by API are not historical". They may not be in one sense but in another they may well be. It's not uncommon in programming to leave "old stuff" in rather than remove it. Kill the Flame Legion Ritualists to stop their summoning of embers was replaced by Destroy the Flame Legion braziers in the event sequence leading to Defeat the Flame Legion Shaman. There is no Flame Legion camp anymore for Destroy the newly emerged Flame Legion camp and that event has not been seen since beta. If someone actually sees these events then, I guess, removing the historical tag might be justified. But, for practical purposes, these events are historical. It has been suggested to me that leaving the tag of historical until someone actually sees the event is the way to go. Certainly, Defeat the enraged troll king, Rescue sylvan pups from their troll captors, Drive the cave spiders away from Grenbrack Delves and Destroy the Risen blockades outside of Wardenhurst are similarly, for all practical purposes, historical. Again, if someone actually sees these events then by all means remove the tag.

ANet responses are, much like many other MMOs, proabaly "canned". It's probably too much trouble to find out if these events are "current". If I were programming, rather than rewrite a section to remove an event, I may well make an event unstartable by making a start condition impossible. Thus, I would have left it there in case that I wanted it later.

I would be interested in your response. Thanks. --Claret (talk) 15:32, 16 June 2013 (UTC)

Sounds reasonable to me, I was simply under the impression that being discovered by the API meant that it was, in fact, still in game, but bugged. I created a forum post on the support page to confirm this with anet. I'm still awaiting a response from them. If it is SOP to leave them tagged as historical until they are actually seen, so be it. Thanks for letting me know. --MushaUser Musha Sigc.png 06:45, 17 June 2013 (UTC)
Reading a two-week old forum post (don't ask me to find it again). the developers don't seem aware or able to admit the large number of permanently bugged events there are. It is not unusual for MMO developers to ignore "old stuff" that's bugged while they press on with "cool" new stuff. My feeling, and that of a few others, seems to be to leave them tagged as historical until they are seen. Thanks for your comment anyway. Personally I get excited if I discover one that is still running  :) --Claret (talk) 10:09, 17 June 2013 (UTC)

event edits[edit]

Events that are part of meta events are not meta events themselves. You've also been removing time limits and replacing them with "x:xx". The total time available is valuable information, x:xx just represents an amount of time that hasn't been recorded yet. Manifold User Manifold Neptune.jpg 06:31, 28 June 2013 (UTC)

Good to know. You see something a certain way so many times, you think it's the standard. --MushaUser Musha Sigc.png 06:49, 28 June 2013 (UTC)


You were editing Stop the giant risen from reaching Caer Verdant when you created Stop the giant Risen from reaching Caer Verdant. The content is identical, so... eh? —Dr Ishmael User Dr ishmael Diablo the chicken.png 23:51, 28 June 2013 (UTC)

Well, I wouldn't say identical. They are 2 separate events of the same name and content, but check out the 'r' in Risen on both event titles. Since failure of the preceding event leads to both events, and they have, however slightly, different titles, I felt it warranted 2 separate event pages, if just to show that 2 events are triggered by previous event failure: 1 goes 1 direction, and the other, a different direction. --MushaUser Musha Sigc.png 23:58, 28 June 2013 (UTC)
Actually risen and Risen are both valid names from API list - dunno if that's relevant. --Claret (talk) 23:56, 28 June 2013 (UTC)--Claret (talk) 23:55, 28 June 2013 (UTC)
{"id":"129403D3-6418-4EA1-BF37-C4CC94DA0EEE","name":"Stop the giant risen from reaching Caer Verdant."},
{"id":"66B4D334-60A7-407E-95F9-C2B50F7186B2","name":"Stop the giant Risen from reaching Caer Verdant."}, weird, eh? --Claret (talk) 23:58, 28 June 2013 (UTC)
Yes, it's probably a way ANet use to get round two simultaneous events, they do run together. Well spotted Musha. I would suggest expanding your notes to cover this in more detail. eg There may be two of these events simultaneously depending on how many generators survived in the previous event. The other will be called the almost identical name [[whatever]] --Claret (talk) 00:04, 29 June 2013 (UTC)
Are these events contingent upon how many generators survived? I didn't know that. I'd like to verify before I make that note, but I'll add such notes should they be applicable. Thank you. --MushaUser Musha Sigc.png 00:13, 29 June 2013 (UTC)
They are, I can confirm that. I have made the note's changes, you may want to review them. As a matter of interest, the French, German and Spanish names are identical, no case change. Weirder and weirder. --Claret (talk) 00:17, 29 June 2013 (UTC)
Ah, I see. The same thing happens during the Jungle Wurm meta event, two different events named Destroy the blighted growth occur simultaneously.
{"id":"CF6F0BB2-BD6C-4210-9216-F0A9810AA2BD","name":"Destroy the blighted growth."},
{"id":"456DD563-9FDA-4411-B8C7-4525F0AC4A6F","name":"Destroy the blighted growth."},
I don't think we necessarily have to have two separate articles if the events are essentially identical save for location. In this case, the names are slightly different (risen/Risen), but I still don't think that's really enough of a difference to have to duplicate the content. (And yes, the content is identical because the intro line reads "risen" on both. :P ) —Dr Ishmael User Dr ishmael Diablo the chicken.png 00:45, 29 June 2013 (UTC)
OTOH there are two ANet ids. And, predicatably, as people find what they see as an error, the almost certainty of re-editing arises. At the very least, a redirect is needed. --Claret (talk) 00:50, 29 June 2013 (UTC)
The difference in the title, though, however trivial, seems to me that they should be kept on different pages. Add to that that the 2 events move and go opposite directions and that when the events have moved far enough, the other event becomes no longer visible as it is no longer in the vicinity. A passerby coming across one event won't even know about the other event. With the Jungle Wurm, there's an over-arcing meta event that causes both instances of the event to appear while in the vicinity. These 2 Risen events are completely isolated from one another. This causes me to think that each Risen event should get its own respective event page. --MushaUser Musha Sigc.png 00:57, 29 June 2013 (UTC)

Textual Description[edit]

You seem to be reducing many of the text descriptions to a repetition of the information in the infobox. The extra material adds flavor to the textual part. You might just as well remove all the text as it's superfluous if one reads the infobox. Just my 2¢. :) --Claret (talk) 03:02, 29 June 2013 (UTC)

Hm. To which pages do you refer please? I've only been removing text that is superfluous (as it can be found in the infobox) other than the backbone text dictated by [1], such as text that mentions follow up events or start npcs. I'm not aware of any lore or flavor text that I've removed. If I have, please point me to it. --MushaUser Musha Sigc.png 03:03, 29 June 2013 (UTC)
Defend Annwen's wardens from the hylek raid is the nearest the top of the list, what's wrong with including near the Hamlet of Annwen Waypoint? It's helpful, it mentions the hamlet and it's not just another version of the infobox. Same in the Liberate version. Guard the mossheart carrying Widd's research - why remove the "Researcher Widd needs help defending the caravan carrying his research on skritt to Chief Dekkti"? There are many other examples. You say that you have been removing text that is superflous. Well, Stop the giant Risen from reaching Caer Verdant the location is in both parts, the event type is in both parts, the level is in both parts. The guidelines are guidelines with a minimum amount of data. Incidentally, since they repeat the text in the infobox, they themselves are illogical but that's another matter. They are not prescriptive. This is a comment. Take it or leave it. Your choice. --Claret (talk) 03:21, 29 June 2013 (UTC)

I am really not getting at you[edit]

But, you do know that the actual order of parameters in event infoboxes does not really matter. It could well be that you do, if so, fine. --Claret (talk) 19:40, 2 July 2013 (UTC)

Oh yes, I do know; but thank you! It just helps me as I go through the event pages, making sure everything that needs to be there is there, if I see it in a consistent order. :) --MushaUser Musha Sigc.png 19:43, 2 July 2013 (UTC)
I applaud your consistency. :) —Dr Ishmael User Dr ishmael Diablo the chicken.png 19:51, 2 July 2013 (UTC)
Oh, no problem. There's a fine line between consistency and OCD, trust me, I know, I cross it regularly.  :) --Claret (talk) 19:54, 2 July 2013 (UTC)
Lol. And I'm far across that line... You should see the way I play the game... XD --MushaUser Musha Sigc.png 19:58, 2 July 2013 (UTC)
Probably not too differently than me, if truth be known. I have restricted myself to crude editing of events as I am confident you will be along, although I don't always agree with your interpretations (it's a wiki, ofc). I am on Scouts and Hearts NPCs' dialogues right now, and with Yoe Dude hitting the POIs… 4am local is good because you can see events fail and explore the chain that often follows. --Claret (talk) 20:03, 2 July 2013 (UTC)
Yeah, it sounds like you play like I do. I play each event twice: once to succeeed, once to fail, to see what other events might be triggered by either. --MushaUser Musha Sigc.png 20:08, 2 July 2013 (UTC)
Pretty much the same. --Claret (talk) 20:10, 2 July 2013 (UTC)

Your missed events[edit]

I looked at your list in your sandbox. Would you like some feedback on it? --Claret (talk) 22:21, 3 July 2013 (UTC)

Please. By all means! --MushaUser Musha Sigc.png 22:22, 3 July 2013 (UTC)
All that is great info, thank you. But I would like to ask how you know about the status of those 2 Plains of Ashford events being removed/replaced from the game? --MushaUser Musha Sigc.png 23:37, 3 July 2013 (UTC)
With regard to the braziers one. I saw it in beta and I saw when they replaced it with the other one. As for the camp one, it's inspired guess work and deduction - so may be wrong. I know this is irksome but sometimes we have to just come to terms with the fact that unless ANet become a lot more forthcoming with the events information, we will have to best guess. Also, ANet don't admit their bugs - hopefully they quietly fix them. My suggestion is to keep checking them on the event server activity "thing" and see if you ever see them. If then, guest to catch them. You're doing a great job, don't get too side-tracked. --Claret (talk) 23:47, 3 July 2013 (UTC)

Player Call-Outs[edit]

Is there anywhere on this wiki that lists all of the player call-outs such as, "I can outrun a centaur!" or "I feel furious!"? --MushaUser Musha Sigc.png 09:29, 20 July 2013 (UTC)

Special:WhatLinksHere/Template:Character_quote ^^--Relyk ~ talk < 10:29, 20 July 2013 (UTC)
Well, that will work! Thanks, Relyk. --MushaUser Musha Sigc.png 20:35, 20 July 2013 (UTC)

Skill infobox[edit]

ok firstly. I can help with the infobox, but what are you trying to do? (secondly, but less important since you've already done it - usually better to test out edits to mainspace templates in the userspace) -Chieftain AlexUser Chieftain Alex sig.png 07:31, 7 November 2013 (UTC)

Yeah.. It wasn't my intention to test though - I thought I had it. I've stopped trying for now seeing as how I was making lots of edits on it. What I'm trying to do is make the skill infobox be able to support multiple pets. For example, Lacerating Slash is available to both Juvenile Eagle and Juvenile Hawk, yet it is only able to list 1 of those at a time. If you can make this work, please do. I apologize for the multiple edits. --MushaUser Musha Sigc.png 07:36, 7 November 2013 (UTC)
No worries about the multiple edits - I think I've worked out how to do it. [2]. The arraymap notation is:
{{#arraymap: String to be split up, probably a parameter | what the string is going to be split up by, for example a comma | what you're calling the bit between commas | what you're doing do the bit between the commas | the separator that prints between your adjusted sections }}
{{#arraymap: {{{pet|Hawk, Eagle}}} | , | @@@ | [[Is for pet::Juvenile {{ucfirst:@@@}}|{{ucfirst:@@@}}]] | <br> }}
-Chieftain AlexUser Chieftain Alex sig.png 07:44, 7 November 2013 (UTC)
Yep! That'll do it. Thanks for coming to my rescue, Chief! --MushaUser Musha Sigc.png 07:48, 7 November 2013 (UTC)

A User's Response to my Feedback[edit]

Please do not send threatening messages over edits of clarity. That is not a clear direction and I clarified it. I was there at that Waypoint when the original was posted and it was NOT clear. The preceding unsigned comment was added by Zushada (talk).

I agree. It wasn't clear at all, and myself as well as all other Wiki users appreciate yours and all other efforts made to clarify. However, you definitely seemed more interested in having your specific word choice be the one displayed than in actual clarity, hence your continuing to revert all edits back to your own. The comment I made on your talk page was not "threatening" in the slightest. I definitely encourage you to continue contributing to the Wiki, but please remember that it's a community effort.
@Doodleplex, I loved your comment! You definitely are proof that not all millenials are bad! Haha! --MushaUser Musha Sigc.png 01:53, 10 May 2018 (UTC)

Onyx and Gold Lion weapon skins[edit]

Hey Musha, thanks for your work on the weapon skin sets. Just as an FYI, the Gold weapon skins are actual items in the game; they just don't get put into your inventory. It's likely being auto-consumed the moment that the Onyx skin is chosen. The Onyx weapon skins only unlock a single skin. As a guess, Anet may have done this so that when these are inevitably put into the Guaranteed Unlocks, the Onyx skin won't unlock the Gold skin. G R E E N E R 04:27, 9 August 2018 (UTC)

Well that makes much more sense, thanks for taking the time to tell me. But how do we know that it's an actual in-game item that's just being auto-consumed instead of simply unlocking the skin? --MushaUser Musha Sigc.png 04:30, 9 August 2018 (UTC)
There are a couple of clues to what's going on. First, when one consumable can unlock multiple skins, Anet has a means of listing them (e.g. the Gas Mask Skin). Normally Anet has auto-consumed skins as flagged to auto-consume, but didn't in this case. That leads me to believe they had at some point a few different plans for the items, and settled on this version looking to the future, and then did some hack to make the Gold Lion version get used. Second, Anet's always used an item of some kind to trigger the unlocking process; I'm not sure if this is a limitation of their code, but I can't think of a counter example. G R E E N E R 04:41, 9 August 2018 (UTC)
Well, you certainly have me convinced. Thank you for explaining. --MushaUser Musha Sigc.png 06:10, 9 August 2018 (UTC)

(Reset indent) Also, this edit is legitimate. The skins are not tied to the anniversary, but rather to gem store packs, so Greener's edit that they're a part of a set is valid. The ID was also correct, so this approach should probably be applied to all the Gold Lion/Onyx weapon pages, correcting it from 6th anniversary -> weapon set. —Ventriloquist 08:51, 9 August 2018 (UTC)