Wikia

WoWWiki

Raylan13

Staff
39,435 Edits since joining this wiki
November 29, 2010
  • I live in Seattle area
  • My occupation is Content Editor
  • I am /facepalming a little too much...

Archived comments:

I'm back! Edit

Tankingmage (talk) 10:48, August 16, 2014 (UTC)

Woot! Glad to hear it Smiley Raylan13@Wikia (talk) 16:40, August 16, 2014 (UTC)

Current Project Edit

As my Youtube series WoW Pro Lore will hopefully at some point cover all of WoW Lore, with some mini series to go into more detail about certain points in WoW's history. I've noticed how incomplete the timeline is, along with many pages missing information which is relevant to them and present elsewhere in the wiki. So I'm going to revamp the timeline, adding in as much detail as possible, so that all significant events are listed there. I will also focus on fixing pre Mists-Logo-Small lore and fixing the irregularities there. Appologies for going AWOL. Tankingmage (talk) 16:49, August 19, 2014 (UTC)

Rewards vs GainsEdit

Shouldn't these be listed in separate sections? "Rewards" are what the quest states you get for completion, while "Gains" are unannounced until the quest is complete. For example, a level 25 character will get the same rewards (cash, loot) as a level 85 character for completing a quest, but the XP they gain will be based on scaling. Reputation gains aren't listed in the quest log (in the basic, no add-on, out-of-the-box Blizz quest log), so they should not be listed as "rewards". This is how Wowhead is set up, and I assumed the same would go for the wiki. AlexSUCF (talk) 21:27, August 21, 2014 (UTC)

OK, do we want to use "Rewards" or "Gains" as the section header? I feel we should keep it consistent across all (as many as possible?) quest pages.
AlexSUCF (talk) 23:43, August 21, 2014 (UTC)

Modification to Quest template (NYI) Edit

I merged the existing {{quest}} template and my {{U}} template into a single one that won't break any existing quest links but also formats the links with "(Part 1)" as small text outside of the link.
Example:
Current {{quest}} link: The Missing Diplomat (3)
Link using {{U}}: The Missing Diplomat (Part 3)
Link using {{Test}}: (Removed cos it's been changed)
I noticed that the only way to get the tool-tip to appear was to use {{quest}}, but the way {{U}} displays the link looks much prettier IMHO. I didn't want to change a core template (again...sorry...) without running the change past a lead admin first tho. I can also modify the {{questlong}} template to do the same. Lemme know what you think. If approved, I'll go through the pages that use {{U}} and change them back to {{quest}}, and then you can delete {{U}}. Well, not delete "you". Just delete {{U}}.
AlexSUCF (talk) 02:52, August 23, 2014 (UTC)

I'd also like your feedback on {{Test1}}...it is an update to {{Questchain}} in that it adds a link to Quest chain after the name of the chain. It also incorporates the catches from the original template (display name is field 2 and "alt text" is field 3). Docs can be written/revised if you approve of the change.
AlexSUCF (talk) 03:56, August 23, 2014 (UTC)
I made tooltips work on {{U}}. I'm not sure what {{Test}} is for, but it looks like there just needs to be more spans with put in all the links to get tooltips to work there also. --Gengar orange 22x22Beware the sneaky smile! Fandyllic (talk · contr) 23 Aug 2014 9:56 AM Pacific
I made {{Test}} as a combination of {{U}} and {{Quest}}, so that i wouldn't break {{Quest}} on all of the pages it is used on. But if you've already added the tooltip coding to {{U}} then I suppose there's no need to do that. I'll go ahead and repurpose {{Test}} today for another project I'm working on. Templates are one of my fortes. Thanks for the support :)
AlexSUCF (talk · contr) 21:14, August 24, 2014 (UTC)


More on Quests...Edit

I don't know if you or Fandyllic have noticed, but I've been working on some fancy new imitation displays for the paperdoll and quest log. Paperdoll is already completed, and active at Template:Paperdoll (though I haven't had a chance to fix that page's outdated documentation yet). I just finished preliminary work on the quest log which you can check out at the (revamped) test page...which I won't directly link here cos when that page changes again it'll make your talk page look all funky (that's why I took the link to it out from our previous conversation). If you like the quest log look, I can start implementing it on pages as I go through them. The idea (once I finish the other two portions of it, which won't take long at all now) is that instead of the Objectives/Description/Progress/Completion sections on quest pages, the quest log would be displayed instead. In theory, the existing questbox could be thrown into includeonly tags, allowing tooltips to continue referencing them while only displaying the quest log format of the quests. Check out my test for an example of the first portion of a quest. Don't ask how I picked that quest to use as my example...I think I "random page"d to it.
Features of this template:

  1. Next/Previous buttons and links only appear if there is a next/previous quest in the chain
  2. Rewards for the quest are displayed exactly as they are in-game, with the money earned following "You will receive", then the choice rewards, then the guaranteed rewards. Any XP and rep bonuses are displayed after the item rewards.
  3. Quest level, difficulty levels, and zone are displayed at the bottom where Accept/Decline would be.
  4. Scrolling text, with the scrollbar located where the in-game scroll bar would be

Possible upgrade:

  1. Change the book icon in the corner based on when the quest was introduced (WoW, BC, WotLK, Cata, MoP, WoD) or when it was removed (overlay an X on the removal expansion)

Also on this test page:

  1. Quest chain sidebox under the infobox. Can be made into a template. Just needs to be in a div with the infobox to float properly.
  2. Short description about the quest before the pages are displayed. More wiki-esque IMO.

Please let me know if you like this and are interested in me implementing it. If you do like it, I would also like the addition of a new .a class in the CSS so I can darken the links. The light blue on parchment isn't really working.

Finally (I think), let me know if you're ever on Chat so I don't have to leave messages on your talk page ^_^.

Oh! One last thing...I'm thinking about putting my name in for admin rights...thoughts? AlexSUCF (talk · contr) 05:47, August 29, 2014 (UTC)


  • I can work on the quest frame and see if I can make it wider without making it look too funky. I'll also see what I can do with the existing questbox frame to make it look less empty. Possibly have the questbox be a top-float instead of a right-float, and be across the top of the page? IDK, I'll play with it.
    • Can I get a new .a class with a darker color (MidnightBlue perhaps) in the CSS for the questlog?
  • As I don't have Beta access, I'm going to continue going through old quests marking them as obsolete and adding the Cata/MoP quests that are missing. For the time being, I'll stick with the old layout but I'll have the questboxes added to each page in comments; if we can find a way to make them look better then we can easily un-comment them.
  • I know very little about the Blizz API. I work with HTML and image editing; scripting and importing character models is out of my realm of expertise. I tried making sense of the API hooks and all that jazz while trying to find where the game populates vendor inventories from, but all I got was a headache. If someone else can show me the ropes then I'd be happy to incorporate character (and NPC?) models into the paperdolls.
  • Agree on the vendor boxes being for current inventory only. Old inventories will be moved to the "Patch Notes" section of the vendor's page.
  • Family trees in WoW don't tend to be very large yet (two, maybe three generations for most families). I updated the Ladimore family page to include all of Lys' information because she was an unnecessary stub. The Eva page may be very simple (four characters, each with their own page), they are still a family. Do they deserve their own page? Maybe not.
  • {{MaxXPCoin}} already has the current max level as the default. Essentially, once WoD comes out we can update the template to use level 100 (and I'll add in the new math for it at that point). Any quests that don't have a max level hardcoded onto their page (that field left blank) will be updated to a lvl 100 max and get the new math added in. Quests that are removed with WoD can be then edited to remain at a max of 90. As I wrote in the documentation for it:

Q u o t e:

Please do not put the current level cap in this field. As new expansions are released the level cap is raised, and this template can be adjusted to reflect the new cap as the default. Any quests that had the old cap coded into their page would then need to be manually adjusted. More often than not, the number of quests that are removed from the game is *much* smaller than the number that remain active (unless another Cataclysm happens, in which case we're all doomed).

  • Cash rewards in-game are listed in the completion window after the "choice" rewards. On the example page, I split the choice rewards into two choice (Axe and Dagger) and two automatic (Hammer and Sword) to show how it would display multiple types of rewards. So you're right, the rewards for *that quest* are split, but it was intentional for displaying an example.
  • Changing the book icon will be incorporated into the next version of the questlog.
  • Admin nomination will be put in soon :)
Thank you again for all of your support for my template craziness!

AlexSUCF (talk · contr) 03:22, September 5, 2014 (UTC)

Idea for Quest pagesEdit

I just did a quick modification to the sample quest page with the issues surrounding empty space cleared up. Of course, a new questbox would be needed (easy fix) and a revision to the questlog template would need to involve the change, but those are doable. Also, the colors are just for placeholders. I'm not awake enough to go finding the necessary images and coding all that right now. But this is a fairly rough work-up of what I have in my mind right now.

  • Original {{Questbox}} is gone, replaced with one across the top of the page
    • Red box: Faction symbol
    • Blue box: Quest title
    • Green box: Quest level and/or difficulty levels, not sure which looks better yet cos its 12am here.
    • Purple box: Whatever information from the original box we want to keep there. Most of the information is redundant because of the questlogs, but we'd need to keep stuff like NPC and rewards for tooltips to populate properly. On that note, is "Solo" necessary on all of the quest pages? Shouldn't it be assumed that if a quest isn't marked as Group/Dungeon/Raid/Party/Bring-your-besties that it is a solo quest? Just sayin'.
  • Short blurb about the quest directly below the infobox.
  • Quest chain floating where the infobox used to be.
  • Jump links to the three sections of the quest (Accept/Progress/Complete)
  • {{clr}} immediately after the jump links in case the chain is long. Possibly avoid this by using a collapsing box for the chain.
  • The three quest log panels
    • Next to the Accept panel would be an image/modelviewer (eventually) of the quest giver along with any notes about the NPC (coords, etc)
    • Next to the Progress panel would be images of the mobs to kill/loot, the items to collect (world objects like a pile of papers to loot or pinecones to pick up), and coords/etc for them
    • Next to the Complete panel would be an image/modelviewer of the quest completing NPC along with notes

This would make full use of the 680px wide frame we have to work in while getting all of the information in. I can update the template to automatically pull the NPC images for the side bar, and a new field for mobs/items to collect can be added too. If we're going to go this route, I think a template with a switch for objects and mobs based on ID numbers would be beneficial. I could code the new field so that the editor just has to enter "M42536,M42555" or "O19030" and it'll display the image (model eventually) for the corresponding mob/object. I can also then size the images based on how many are being displayed by using a string function which could otherwise fail if the mob/object name has a funky character in it.

I think I'm rambling now, so let me know if that made any sense. AlexSUCF (talk · contr) 04:30, September 5, 2014 (UTC)

Login Problems Edit

Hey Raylan, it's Tankingmage, I've been having login problems, will hopefully get this sorted. :)

Around Wikia's network

Random Wiki