User talk:PanSola

Archives

 * Past mistakes are moved into the /MistakeArchive
 * Other closed issues are moved to /Archive, /Archive2, /Archive3, /Archive4, /Archive5, /Archive6

A bunch of proposed changes to the skill box template(s)
Sorry about dumping all this on you, but there aren't too many people to ask about this since most don't understand how the templates work. Here's a bunch of changes I want to make. I don't think there are reasons not to implement them, but I wanted to ask someone before making changes to "important" templates. If you have no objections, I'll make all these changes.

There's categorization code for campaign, skill type, etc. in the skill box templates besides the basic template:skill box. It's in many (if not all) of the others even though it'll never end up being used. I want to go through and cut the categorization stuff out of all but the basic template.

Along the same lines, I'll cut out the code that generates a message regarding the legacy use of skill templates since it should no longer be needed. This change and the last one aren't important, but it'll cut down on template use some, and that can't hurt but might help the server.

As for the usage of "profession=hide" in the QRs, I think it would be better to have parameters like hideprofession or hidewhatever. When I asked you a while ago on Template_talk:Skill_box about the parameter overriding, you said it was scrapped. Did you only mean for the stats? Hiding the profession icon and attribute for the QRs rely upon the profession being overridable. If it's switched to check for parameters like hideprofession the whole " " thing actually can be scrapped. In addition, SkillBoxIf can be scrapped in favor of just an if-then that checks for the existence of hideprofession (or whatever), cutting out some more template use.

Then there's Category talk:Echo (skill type)s where Galil and I discussed what to do about the echo type with the template. Originally, all the echo skills had their type set to "echo" which resulted in skills being categorized into "category:echos" but the type linking to echo, the skill article. Midnight08 came along and changed all the types to "echo (skill type)" to fix the type link, I guess, which resulted in "category:echo (skill type)s" but a proper type link.

Galil added a "cat" parameter to template:skill box with the intention of it handling the skill type category for echoes. So at the moment, the types are all "echo (skill type)" with cat set to "echos (skill type)." This sort of conflicts with how you have a hardcoded if to handle the skill type category for skills, since they both do the same thing in different ways. I don't really have an opinion about which way should be used, but they should both be done in the same way.

Depending on how the question of hardcoding an if into the template or providing a specific parameter instead goes, I'll do the same thing regarding the skill type link. Right now in the skill box and QRs, they all link to Echo (skill type), but I think Echo would be better. But, it's not possible to use a parameter to construct a link in a template such as " | ." I'll either add a parameter like typepipe so links are something like " | " or add a hardcoded if to achieve the same effect of making the "(skill type)" not display.

Lastly, to try to push to ParserFunctions again, I mentioned PF could be used to auto-fill the progression tables (since they're just linear). We could actually make skill descriptions fill in the values, too. In build articles we can use a "row"-like format that displays the actual values based on the build's attribute ranks. I'm going to post on Gravewit's talk page about it, so please chime in (if you agree).

Once more, sorry for so much text. --68.142.14.80 03:54, 24 August 2006 (CDT)


 * Thanks for caring. I agree with cutting out the categorization code for the non-basic skill box templates.  I agree with removing the legacy note.  The entire "hide" thing should just get nuked -- a new "skill box blah" should be used to display things differently (this is a change of design that I thought through later).  I suggest a "nocat" parameter for skill boxs to disable hard-code autocategorization, and manually categorize all skills of Echo type (manually specify  all of its categories, not just the skill type cat).  Finally, I support ParserFunctions too. - 05:51, 24 August 2006 (CDT)


 * Doing all the work in the specific skill box template seems like a good idea. Between that and removing the legacy note, there's no use for the "part" parameter, right?  Besides removing the useless categorization stuff, I'm going to think about it more before making any other category-related changes.  I was pondering letting skill data templates add additional categories, actually.  Something like extracat1=Touch skills, though that'd just make it a bunch of if extracatX exists then category:extracatX.  I think it'd be best to keep the categorization all in one place, whether the skill article or in the templates.  --68.142.14.80 06:16, 24 August 2006 (CDT)


 * Check out GuildWiki talk:Sandbox/Skill box for what I did with ParserFunctions and the basic skill box template. --Fyren 13:05, 25 August 2006 (CDT)

Skill quick reference layout
You have been taking part in the discussion earlier so I thought I might post to you among some others. I want this to be resolved pretty soon, so plese consider taking part in the discussion at GuildWiki_talk:Style_and_formatting/Skills. -- (talk) 20:01, 25 August 2006 (CDT)

Request for Review
As a well known/well learned mesmer user, I'd appreciate if you could review the Effective Mesmer Guide I've been writing up. Mesmer is one of the only profession without a guide, so I thought you might want to contribute. (bonus wiki-LAFT points) --Theeth (talk)   22:06, 27 August 2006 (CDT)

Massive Link-Changing
I've noticed that you have gone about changing most Tyria and Cantha tags into Prophecies and Factions tags, respectively. Is this a new standard on how to arrange chapter information, and if so, do you want help? ;) There are quite a lot of skills out there... --Ordin 22:28, 2 September 2006 (CDT)
 * It was never standardized. However, I believe in terms of acquisition (skills, items, quests), the Campaign name is more meaningful and relavent information than the in-game continent.  I've brought the issue up specifically regarding quest availbility here.  I will eventually finish changing them on my own, but if you want to help, all the better.  I'm just about to grab dinner anyways (-: - 22:32, 2 September 2006 (CDT)
 * Well, I might as well get something done while waiting for my show (anime -.-).--Ordin 22:51, 2 September 2006 (CDT)

Template:Switch and Template:Case
can you comment on the merge request on these pages. Template:Case is mine, a hold-over until parser functions are installed, and Template:Switch seems to be your creation, but i can't discern use. --Honorable Sarah 15:03, 5 September 2006 (CDT)


 * I thought I read that parser functions are now installed. Please retest and confirm/deny. &mdash;Tanaric 15:36, 5 September 2006 (CDT)
 * you are correct, they've been installed in the week i was gone, both of these should be deprecated then? --Honorable Sarah [[image:Honorable_Icon.gif]] 15:43, 5 September 2006 (CDT)

Warrior Prophesies Unique Items
Hi PanSola, thanks for all the contributions you make here. I hit the green prophesies items to look up a few old stats on greens and found them gone. I didn't go browsing to see when they got deleted and maybe you are working on moving them in still from the work I see you did with changing things to prophesies instead of Tyrian, but can you check to make sure you didn't lose the items in an update. If I find the old table of items here soon I'll edit them in.--ShmEk 19:04, 5 September 2006 (CDT)
 * The only thing I changed was from "Tyrian" to "Prophecies", and that's the only change I was planning to make, with respect to warrior prophecies unique items, if I actually did anything to it. Can you tell me the specific article you are referring to so I can actually look into it?  There's no way otherwise for me to guss.  I haven't touched the Warrior unique items quick reference (Prophecies) article since May. - 19:39, 5 September 2006 (CDT)

Japanese (Nightfall Event)
Hi mate, we need your Japanese skills to decypher this. What is this? People may phone Mike O'Brien and he will answer questions? -- 03:02, 6 September 2006 (CDT)
 * People email NCJapan 2 questiosns for Mike. 12 lucky winners will get invited to the question/answer session, and receive a Chimeric Prism at the end of the event (another indication that Japan is secretely part of Eurpoe?). - 04:22, 6 September 2006 (CDT)
 * Thanks for clearing that up. :) --[[Image:TurningL sml.gif|Tetris L]] 11:05, 6 September 2006 (CDT)

Taiwanese ("Globe Event")
I should start a section "PanSola's Translation Service Request". ;)

<- What's this? It says "Globe Event", but also something about "Jobs". I'm puzzled. -- 07:59, 11 September 2006 (CDT)


 * Job = Profession. This is a Chinese translation of the Scribe article on the PvP event. - 08:02, 11 September 2006 (CDT)


 * Cheers, once again. It was mostly the previously unreleased image of Elementalist and Necro armor that cought my attention. --[[Image:TurningL sml.gif|Tetris L]] 08:13, 11 September 2006 (CDT)

The Armor Pages Are a Mess!

 * It's hard to respond to some of the things you are pointing out, because I feel like we already address those things. For example, most armor have a Campaign associated to it, that is true, and we already handle it.  By pointing out things armor have in common but that aren't having issues, you are diluting and obsuring what some of the problems, making it harder for me to see your vision.  I've read the whole thing three times, I'll need to take a break and re-read it a few more times before I have the confidence to form a proper response. - 16:02, 6 September 2006 (CDT)


 * Blah, anyways, here's a few things I know I can support without digesting what you wrote above:
 * templating common components of armor galleries. I think depending on the armor art, additional custom shots should be able to go in the gallery for details.
 * common naming format for gallery pictures to help with the templating above
 * an open efford to give me more ectos and shards d-:
 * As for the rest, I need to figure out what you mean by what you wrote first. - 16:24, 6 September 2006 (CDT)


 * {| width="100%" style="background: transparent;"


 * style="background: #FFE5FE; border: 2px #FF36F7 solid; padding: 5px 15px 5px 15px;" valign=top|I realize that post was long and covered some of the things we already have done. It's just that not all the armor pages have them implemented yet. And as for the confusion of the Armor Art of Tyrian, Ascolon, and Krytan Armors being in the core, I think it's personal opinion of where they belong. They are core, but cannot be made in kryta from other creating a character or from a collector. Technically, Obsidian Armor isn't crafted in Tryria either >^_^<. Obsidian Armor looks so lonely by itself so I gave it some core friends. It looks nicer, although, yes. So far they can only be crafted in Cantha. I emphisise 'so far' because who knows what Nightfall will bring. In Elonia there may be armor crafters for those armors as well. That's only speculation on a common occuring theme though.

Prehaps I should be more succinct. My Main beef right now with the pages is that most of them still don't use templating, and need more of it. In adition, there is problems with data redundancy. I'm not sure if your familure with the term. It means that the item is in multiple locations, and in order to update the pages, you would have to go back and edit each by hand. If we instead store this data in 1 common file, in our case a template function, and link it to it to the pages recalling it, we can update all the occurances of that information. That is what I am really proposing. More templating is still needed. The templates also need to be set up to handle special cases as well, such as with the non bonus armor function types.

We can nitpick over the armor classifications later >^_^<. --Vulpes Foxnik 16:44, 6 September 2006 (CDT)
 * }
 * Enchanter's Obsidian armor can be crafted by people who only have Factions Campaign. It can be crafted by people who only have Prophecies Campaign, and thus it rightfully belongs in Core.  Again, as I have stated, I agree that Tyrian is intrinsically core.  But in the context of Enchanter's Armor, listing it under the core heading is misleading and provide no directly useful information.  People who only have Prophecies Campaign cannot obtain a set of Enchanter's Armor for their characters using Krytan art, and I believe that piece of information to be of sufficient importance that it should be conveyed in the Enchanter's Armor article.
 * I am fully aware of the concept of redundency. I am one of the biggest pushers for using modules to eliminate redundency on this wiki (with Karlos being the biggest opponent against modules, not to say he supports redundency, as he is against modules for other reasons).  However, where concern of misleading information is concerned, to me it trumps the concern over redundency.  We should not structure information to be misleading just to remove redundency.
 * Finally, I am still unclear WHAT is redundent. Part of the problem is you mentioned Campaign as being one of the common things across armor, but I don't see how, using Campaign as an example, is there any actual redundency that can be eliminated.  Campaign is a property that all armor has, but their value vary for each and every armor.  The only redundent thing that immediately comes to mind for me is which thumbnail image should be used for the armor art tables, and that will easily be taken care of using standardized naming scheme without bothering with a template or module to store all the data.  Thus I'm back to re-reading what you wrote to figure out the rest of your vision. - 17:01, 6 September 2006 (CDT)


 * {| width="100%" style="background: transparent;"

Redundancy by urgency: --Vulpes Foxnik 17:39, 6 September 2006 (CDT)
 * style="background: #FFE5FE; border: 2px #FF36F7 solid; padding: 5px 15px 5px 15px;" valign=top|I'm sorry about moving Tyrian to core. I have no intention on spreading misinformation. Both the Ranger and Warrior galleries list Ascolon, Tyrian, and Krytan as core. I've seen it in both. I'm sorry I touched the Mesmer section. I'm sorry if I am being aggravating to you. I'm new here, although I really would like to help out. I did not mean to 'talk down' to you. I'm just used to having to explain every little thing. My first post was ment to set up an overall view of the Armor issue at hand, not to Address a particular issue.
 * 1) The Armor Art Galleries at the bottom of the page.
 * 2) The Armor Art and Function Templates so they Report Ascended, Standard, and Obsidian.
 * 3) The Crafter Tables. (The tables themselves, not the data)
 * 4) The Class Armor pages. Closely related to #1 in the fact that they share(or at least should share imho) the Gallery previews for Armor Art as much as possible.  I may be obsessing over the redudancy of the data in the tables.
 * }
 * Don't worry about apologizing (-: I know you only have positive intentions for the wiki, and that's all that counts.  I'm not aggravated, just explaining my stance, and I am no more valuable than you are (just been around longer so I have a higher probablity to have considered more facet of things).  If you didn't touch anything, I wouldn't have thought about evolving the Mesmer armor/Factions art to be more compact and useful for Mesmer's Armor (the idea has popped up before, but I never gave it much thought until you came along).   Reading the rest of your latest post now (I'm typing this just after reading your first paragraph) - 17:48, 6 September 2006 (CDT)


 * 3. The crafter table already has kind of a header table that gets subst-ed at Template:armor crafting. It's developed after the release of Factions, so many prophecies armor articles haven't conform to that format yet.
 * 1. I believe a certain degree of redundency should be kept to make the information clear. Take a look at the newly evolved Virtuoso's Armor and Mesmer's Armor for example and let me know if you think the redundency there is ok or not.
 * 2. The only thing the armor box templates don't report currently is Standard. They report Ascended and Obsidian.  I prefer not to use IF's in templates when I can help it, and I'll ponder on what's the most elegant solution to get Standard in there.
 * 4. Due to the nature of the forced redundency for clarity in module design (see my response to 1), I think the class armor pages shouldn't be using the same modules (it'll have over-redundency). I think the redundancy problem will be trivially solved if we adapt a common-filename system for the images, which I have stated my support for. - 18:06, 6 September 2006 (CDT)
 * {| width="100%" style="background: transparent;"

I love what you did with the Galleries down there. They clear up any and all conceptual muddles in relation to acquisition. I can see what you are saying about how the Class pages should have their own section, mainly because those are to display the art styles, rather than where to get them. It is not overly redundant if it is only used in 1 location each time, which seems to be the case. Basic and Advanced is a much more succinct way of telling the armor cost than Standard and Ascended (which is relatively irrelevant in factions). As for the Armor Status Leveling, have you ever considered using a Switch? Wiki support them, but I'm not sure if they use namespace. It would also require alot of updating to the page. However, If it were completly in my control, I'd do away with the 2 tier system and classify a 3 tier system. Basic, Advanced, and Elite. Basic would be all the 'Standard' Armors. Advanced would be Luxon, Kurzick, Canthan 15k, and 15k Prophesies. Elite would be Kurzick 15k, Luxon 15k, and Obsidian. Ranking them on total resources needed to create them, rather than the cost solely in gold. I'm going to start working on fixing the Warrior section. Ranger is also a mess, but I think I should take a systematic aproach to updating the pages. --Vulpes Foxnik 19:58, 6 September 2006 (CDT)
 * style="background: #FFE5FE; border: 2px #FF36F7 solid; padding: 5px 15px 5px 15px;" valign=top|
 * }


 * I used Basic vs Advanced out of practicality. Mesmer's Armor only has Basic Art.  All other functional types use both Basic and Advanced. It minimizes the number of rows and modules needed.  It helped that all the "Basic" ones can be found in Kaineng and Shin Jea (early parts of the game) and the Advanced are only found later in the game.  I didn't really care about crafting costs, and I don't think we should complicate matters by adding levels due to crafting costs.  BTW, I don't see why anyone would consider Kurzick 15k and Luxon 15k to be the same level as Obsidian.  Even when certain monk/necro obsidian armors didn't need ectos, they still serously outprice the Kurzick/Luxon 15k and are much harder to acquire. - 20:06, 6 September 2006 (CDT)


 * Getting sick of cutting and pasting the border... Anyhow, I've made Kurzick 15k recently and it is Still fairly costly even if the price of Amber has droped (of course AFTER I made it). Anyhow, I spent around 40 ecto to get enough amber to craft the whole thing. True, It takes much more money to make Obsidian and time, but the Factions 15k are closer in price to Obsidian than the other 15k prices. Your right. We shouldn't complicate it, but I think the basic and Advanced armor sections are much better than what we had before. --[[Image:Vulpes_Foxnik.png]]Vulpes Foxnik 20:22, 6 September 2006 (CDT)


 * "Getting sick of cutting and pasting the border..." <- Thank God! My eyes were starting to hurt! ;) --[[Image:TurningL sml.gif|Tetris L]] 08:15, 11 September 2006 (CDT)


 * At current prices, the amount of ecto and obsidian required for a full set of obsidian armour (excluding headgear) is 1197 platinum. At current prices, the 70 jade required for a set of 15k Luxon armor costs 42 platinum, while the 70 amber required for a set of 15k Kurzick armour costs 63 platinum. For comparison, the 350 Vellum required for a full set of ascended Ascetic's or Scar Pattern armour costs 66.5 platinum. I don't remember Amber or Jadeite ever reached the 3k mark, so even when 15k Luxon and Kurzick armour did cost a small fortune they were far more affordable than Obsidian. I believe we went from 15k to Ascended because it was the official term, but I'm not sure about the source. -- Gordon Ecker 00:34, 13 September 2006 (CDT)

Recentchanges page
Is there a method to 'safe' a setting? i was trying to hide all minor edit and output 500 in a page, but the setting is gone after i click reload.
 * Nevermind, found the option... -- [[Image:Ritualist-icon-small.png]] Cwingnam2000 19:46, 6 September 2006 (CDT)

Template for Crafters
Whats the wikicode to call this table up?--Vulpes Foxnik 13:51, 7 September 2006 (CDT)
 * Template:Armor crafting, just subst it. - 06:57, 8 September 2006 (CDT)

Page deletion
What exactly do you want deleting? Category:Candidates for deletion I don't know how they're all included lol &mdash; Skuld 03:05, 10 September 2006 (CDT)
 * It was caused by this. --Fyren 03:14, 10 September 2006 (CDT)

Good job
Good use of the troll template. :) Wish I'd thought to put that there last night.  --Rainith 22:41, 10 September 2006 (CDT)

Your User Page Formatting
Hey mate, are you aware that in IE in your user page all the main text has an indent, obviously caused by the language boxes?! See this image. You might want to add a

tag. -- 08:26, 11 September 2006 (CDT)
 * It has a clear (not as a template, but as div code). THe problem was an unclosed div tag. - 08:29, 11 September 2006 (CDT)

I really want to apologize.
I feel so bad about the whole template not working out as quick as I hoped. I didn't pick up all the language nuances as fast as I though. I also made some false assumptions, and realised some of my sudo code I wrote is wrong or backwards and corrected this in later versions when Aspectacle pointed out why the icons disappeared. Then you did all the work of fixing everything I messed up. I feel bad about this. I also wrote a new template that should be able to clean up our code a bit. Template:Armor icon check.--Vulpes Foxnik 13:14, 11 September 2006 (CDT)
 * Don't worry about it. Such is the fate of those who meddle with templates (-: - 20:53, 11 September 2006 (CDT)

Alpha leaks?
I'm intreguied to what you do with them once people have reported them to you, care to elaborate? --Jamie  09:48, 13 September 2006 (CDT)
 * I email them to Gaile and Andrew. If it's on imageshack or rapidshare, I also use their internam reporting service to request the image be removed.  If the link has been posted on guildwiki I'll delete the entire article and restore to a previous version to wipe it off the history. - 11:10, 13 September 2006 (CDT)

I just got that you mentioned the other one too, which isn't rly an alpha. If i'd have known about that I wouldn't have posted this >< Might want to change your notice? Sorry about that &mdash; Skuld 13:19, 13 September 2006 (CDT)


 * Um, not sure what you are suggesting for me to change my notice to. As for your own edit, I'll let you clean up after yourself d-: - 13:29, 13 September 2006 (CDT)

This is completely screwed up. We're not ANet, we're not ANet's watchdogs, and we're not under an NDA. Pages were deleted in defiance to our deletion procedure. A user was warned that "if it happens again there'll be a ban." If someone wants to post something on a talk page-- loosely, anything that's relevant, not vandalism, and not a copyright violation-- they should be able to. If they want it in an article they need more than speculation. --Fyren 17:28, 13 September 2006 (CDT)
 * Due to the firewall at work, I can't access the guildwars.com site to review the fansite agreements. What, if any, comments/restrictions are placed on official fansites by Arenanet?  That should be the determination on deletion and banning in cases of violation.  However, I would fully expect ArenaNet to ask us to remove any content of this type from our site if it were reported to them; and our relationship with ArenaNet in all areas would be better if we abide by the request rather than permit it to remain. --- Barek (talk • contribs) - 17:48, 13 September 2006 (CDT)
 * They say that ANet may request removal of any content at any time and that content may not be used on a site that contains "objectionable content" defined at ANet's discretion. Both are rather meaningless; ANet can request whatever they want and it's their copyright so they can tell anyone not to use something at their whim.  --Fyren 18:00, 13 September 2006 (CDT)


 * It is of my opinion that any and all alpha leaks should be removed from the wiki. I have no doubt that if Anet learns that GuildWiki has any alpha leaks on it, Anet will tell us to remove it. Therefore my position is we should remove alpha leaks before Anet even tell us to remove it. Since you disagree with me, do you think that we should keep alpha leaks on talk pages even when Anet tells us to remove it?  Or do you think we should keep alpha leaks as long as possible until Anet tells us to remove it?  - 23:17, 13 September 2006 (CDT)


 * My personal opinion would be to leave it. But in any case, the actions that were taken earlier should either not be repeated or our policies be amended to allow them. --Fyren 23:28, 13 September 2006 (CDT)


 * For clarificaion, your opinion would be to leave it even after Anet telling us to remove it? or until Anet telling us to remove it? - 23:33, 13 September 2006 (CDT)


 * Yes, if it were solely my site, I would leave up "leaked alpha information" even after ANet requested removal. Such information, on the scale of "insignificant" to "important," would be pretty close to "insignficiant" even in context of it being about a video game. At the same time, it's still interesting and an excellent topic for discussion. --Fyren 00:00, 14 September 2006 (CDT)


 * I disagree with that opinion, Fyren. Consider the recent deletion of all Nightfall builds.  Why?  Speculative information.  Guess what Alpha leaks are?  Not only that, but supporting such an action indirectly by ignoring it is liable to harm relations with ArenaNet (hopefully that's *all* it'd harm; consider the financial damages possible), the community, and possibly even the game as a whole. - Greven 23:53, 13 September 2006 (CDT)


 * Reread my first comment. Note what I say about talk pages versus articles regarding speculation.  --Fyren 00:00, 14 September 2006 (CDT)