Hey, guys. I've been looking at our different articles, and I thought it would be great if we could standardize our sourcing methods for our info from The Old Republic. That way, when we contribute on the same articles, we can sync up our references. Personally, I'd suggest we go with the method I've been using: I think it's a good way to differentiate between different quests and general info from TOR.

Here's how I've been doing it:

  • Moved below

The last one should realy only be used if it's on a planet where both factions play, like Tatooine or Alderaan. Even then... I don't really see the necessity for specifying whta faction. If it's info about the environment, like general locations, or characters that everyone can access, I just use <ref name="TOR">''[[Star Wars: The Old Republic]]''</ref> . That way, people can tell what quests this info is coming from, just like issue numbers in comics.

If you guys can't find the name of a quest, I'd suggest using SWTOR Spy, TORHead, or DarthHater Database. They're excellent resources for finding quests.

So, what do you guys think? Cade Calrayn StupidRepublicEmblem-Traced-TORkit 17:49, May 26, 2012 (UTC)

  • Looks good; don't forget these:
    • Moved below

Are we missing anything else? Darth Trayus(Trayus Academy) 08:14, May 28, 2012 (UTC)

  • Oh, and space mission. For the Esseles flashpoint, I italicized Esseles because it's a ship name. Probably good to do that for the Black Talon too.

So, here's the summary table:

Source Type Sourcing Method
General (any/multiple classes) <ref name="QUEST TITLE">{{TORCite|Mission: "QUEST TITLE"}}</ref>
Specific Class <ref name="QUEST TITLE">{{TORCite|CLASS NAME Mission: "QUEST TITLE"}}</ref>
Area Mission <ref name="QUEST TITLE">{{TORCite|Mission: [Area] "QUEST TITLE"}}</ref>
Daily Mission <ref name="QUEST TITLE">{{TORCite|Mission: [Daily] "QUEST TITLE"}}</ref>
Heroic Mission <ref name="QUEST TITLE">{{TORCite|Mission: [Heroic] "QUEST TITLE"}}</ref>
Faction-Exclusive <ref name="QUEST TITLE">{{TORCite|FACTION NAME Mission: "QUEST TITLE"}}</ref>
Codex Entry <ref name="Codex: ENTRY TITLE">{{TORCite|Codex Entry: "ENTRY TITLE"}}</ref>
Flashpoint <ref name="FLASHPOINT TITLE">{{TORCite|Flashpoint: "FLASHPOINT TITLE"}}</ref>
Operation <ref name="TITLE">{{TORCite|Operation: "OPERATION TITLE"}}</ref>
Crew Mission <ref name="MISSION TITLE">{{TORCite|SKILL NAME Skill Crew Mission: "CREW MISSION TITLE"}}</ref>
Space Combat <ref name="MISSION TITLE">{{TORCite|Space Combat: "MISSION TITLE"}}</ref>
General (Locations, etc.) <ref name="TOR">''[[Star Wars: The Old Republic]]''</ref>
  • If two ref names are the same, just use a prefix for each of them to differentiate between the two, like Operation or "Class name". Cade Calrayn StupidRepublicEmblem-Traced-TORkit 19:14, May 28, 2012 (UTC)
    • Another note: the stuff in caps would be the part that changes for different quests/missions. Include the quotation marks, so it shows where the quest names start and end. Cade Calrayn StupidRepublicEmblem-Traced-TORkit 01:53, May 29, 2012 (UTC)
      • I'd love to see the TORCite template updated to include fields for all this stuff. Right now, this system is good, but it's kludgy to use the template. ~SavageBOB sig 19:30, May 30, 2012 (UTC)
        • Hmmm... I'll experiment on that. Cade Calrayn StupidRepublicEmblem-Traced-TORkit 19:30, May 30, 2012 (UTC)
        • Here's a rough wikitext-draft of the templates. I showed it to Xd, and he said he would come up with something. Cade Calrayn StupidRepublicEmblem-Traced-TORkit 20:22, May 30, 2012 (UTC)
          • Take a look at User:Xd1358/test and see if that's what you're looking for. 1358 (Talk) 20:50, May 30, 2012 (UTC)
            • That's exactly what I was looking for. All of the different source types, combined into one template. Excellent!! Cade Calrayn StupidRepublicEmblem-Traced-TORkit 21:00, May 30, 2012 (UTC)

Ad blocker interference detected!

Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.