Wowpedia

We have moved to Warcraft Wiki. Click here for information and the new URL.

READ MORE

Wowpedia
Don't have an account?
Register
Register
Wowpedia
Wowpedia
274,795
pages
in: Linux, Technical support

Talk: Naming policy

Back to page | (Difference between pages)
Sign in to edit
(wowwiki->wowpedia)
 
(version numbers)
 
Line 1: Line 1:
  +
{{redirect|Wine|in-game drinks|Drink#Alcoholic Drinks|Alcoholic drinks}}
−
{{archives2|27 June 2006|15:43, 12 September 2007 (UTC)}}
  
  +
{{For|dealing with common problems while ''using'' wine|Wine troubleshooting}}
−
:* For some previous naming related discussion, also see [[Wowpedia talk:Policies/Archive (old discussion page)]]
  
  +
{{Infobox
  +
|title = Wine
  +
|image = [[Image:Wine.png|70px]]
  +
|header1 = Releases
  +
|label2 = Stable release
  +
|data2 = [http://www.winehq.org/announce/1.2.2 1.2.2]
  +
|label3 = Development release
  +
|data3 = [http://www.winehq.org/announce/latest 1.3.13] (4 February 2011)
  +
|header4 = Links
  +
|label5 = AppDB
  +
|data5 = [http://appdb.winehq.org/objectManager.php?sClass=application&iId=1922 AppDB: WoW]
  +
|label6 = WineHQ
  +
|data6 = [http://winehq.org winehq.org]
  +
|header7 = [http://source.winehq.org/git/wine.git/?a=rss Latest commits]
  +
|data8 =
  +
<!--
  +
<div style="font-size:85%; border:1px solid #555; background-color:#2a2a2a; padding:1px; margin:1px; text-align:left;">
  +
<rss>http://source.winehq.org/git/wine.git/?a=rss|short|max=5</rss>
  +
</div>
  +
-->
  +
}}
  +
  +
'''Wine''' is a free software application which aims to allow [[wikipedia:Unix|Unix]]-like operating systems on the x86 architecture to execute programs written for Microsoft Windows.
   
  +
== Introduction ==
−
{{adopted}}
  
  +
This article primarily talks about setting up Wine for running the MS Windows version of {{wow-inline}} [[World of Warcraft]]. Wine also runs on Macintosh computers with x86 CPUs under Mac OS X, but since [[Blizz]]ard makes a Mac OS X native World of Warcraft client, running it under Wine is unnecessary and even silly.
   
  +
World of Warcraft had a client for Linux while it was in the beta phase of development, but it was later dropped and never officially released.<ref>http://www.learninglinux.com/postp734.html#734</ref> Currently, WoW is run on Linux by use of Windows {{wplink|Compatibility layer|compatibility layers}}. Given that the World of Warcraft client is no longer officially developed to work in Linux, the installation of it on Linux is a somewhat more involved process than on Windows, which it is streamlined to install more easily on. However, with some careful research, and a bit of patience, it's very possible to do so.
−
----
  
   
  +
Alternatively a streamlined process of installation and windows installation conversion is available via [http://www.playonlinux.com/ Play On Linux].
−
== Titles ==
  
   
  +
== Installation ==
−
A new discussion!
  
  +
This guide will only cover the Wine compatibility layer. It is however fully compatible with [[#Crossover Games|Crossover]].
   
  +
Before you begin the installation, you should run the following simple command, which will check whether your video card driver has
−
So I notice we appear to have slightly conflicting policies regarding character names. Currently Lore Chars get no title, NPCs do - but what happens when something falls into both categories?
  
  +
[http://en.wikipedia.org/wiki/Direct_Rendering_Infrastructure DRI] enabled, which allows WoW to run much faster (you may need to install package <tt>mesa-utils</tt>):
  +
glxinfo | grep rendering
   
  +
Which should return a line similar to this:<br />
−
My thoughts are the NPC part takes precedence. That way we only ever use the most up to date titles, if any. {{User:Kirkburn/Sig}} 18:23, 27 February 2007 (EST)
  
  +
direct rendering: Yes
−
:Agreed, with a redirect to that name from their name without the title.--[[User:Sky2042|Sky]] 18:25, 27 February 2007 (EST)
  
   
  +
If this line says "No", it means that the graphics data will be handled in software rather than directly by the graphics hardware, thus significantly reducing speed at which WoW will run. Thankfully if you are using relatively recent hardware, enabling DRI is usually just a configuration issue.
−
:How about have all article tiltes be full name, and simply redirect NPC titles to it? I don't really care what variation the article is named, as long as i end up at the right article, directly or redirectly, heh. I see no reason why this can't be done.
  
−
:But, if you're going to go with the above, then atleast remove the lore version so a lack of titles aren't enforced on non-NPCs. Think it's fine to use a probable title for lore characters. --<span style="background-color: #111; border-left: 1px #444 solid; border-right: 1px #444 solid; padding: 0 0.2em;">[[User:Zeal|<span title="Zeal Vurte" style="color: #C0C; font-weight: bold;">Zeal</span>]]</span><span style="padding: 0 0.3em; background-color: #222; border-right: 1px #444 solid; font-size: 0.85em;">[[User talk:Zeal|<span title="Zeal's Talk" style="color: #C0C;">talk</span>]]</span><span style="padding: 0 0.3em; background-color: #222; border-right: 1px #444 solid; font-size: 0.85em;">[[Special:Contributions/Zeal|<span title="Zeal's Contributions" style="color: #C0C;">contr</span>]]</span><span style="padding: 0 0.3em; background-color: #222; border-right: 1px #444 solid; font-size: 0.85em;">[http://www.zealvurte.co.uk <span title="Zeal's Website" style="color: #C0C;">web</span>]</span> 18:50, 27 February 2007 (EST)
  
   
  +
For more information about enabling DRI, refer to the information from your distribution's support guides on graphic card driver installation. For extended personal help, forums and chatrooms are usually a good bet. Just tell them what the Make and Model of your graphic card is and they will be able to point you in the right direction. As always, remember that search engines are your friend.
−
:::My opinion is we should go with a character's full lore name, that is a name that will be mentioned in an article, novel, quest log, or other source of lore. That is for example, instead of "Mekgineer Thermaplugg" we should go with his full name, "Sicco Thermaplugg", or "Mekgineer Sicco Thermaplugg". The NPC title can redirect into the lore name.
 
   
  +
=== Distribution-specific methods ===
−
:::Whereas in the case of minor characters that do not have full names, we can fall back on the NPC title instead, for lack of having a more accurate name.[[User:Baggins|Baggins]] 22:40, 27 February 2007 (EST)
  
  +
Different GNU/Linux distributions use different methods of installing software, which oftentimes makes it hard to make easy installation options available for all distributions, especially for large and complex projects like Wine. Luckily a lot of energy has been put into making the distribution native installation methods available for a large variety of popular distributions. Please see http://www.winehq.org/site/download and follow the installation directions for your particular distribution.
   
  +
=== Compiling Wine ===
−
This is an old discussion, but does a minor NPC whose full name is known, but also has a title in their NPC name, ever ''not'' get moved to a page that omits the title? I am seeing a lot of that.--{{User:Sandwichman2448/Sig}} 21:44, September 12, 2009 (UTC)
  
  +
If you were unable to install Wine with a method found on that site, or if you are an experienced user wanting more control over the installation, then you may want to look into compiling Wine from source code. See the WineHQ wiki for information: http://wiki.winehq.org/Recommended_Packages
   
−
==Quest names, chains==
  
−
This discussion was held in July, but an agreement was not reached, nor has it been brought here, yet, so I'm going to lay out the ideas for further discussion. The question was how to deal with the names of quests that are identical, whether they are part of a chain, or otherwise. It was brought up because of the creation of new articles by [[User:Laurlybot]].
  
   
  +
== Installing WoW ==
−
Here are the different ideas talked about on the pump:
  
  +
This section explains four different methods of installing WoW. If the first method doesn't work for you, or you prefer a different approach, then simply skip to the next method and so on.
−
#Append the unique quest ID to every quest name.
  
−
#*Should the disambiguation at the end of the name be removed?
  
−
#'''(Insinuation)'''Rename quests to the title of the first quest in the chain, using numbered disambiguations.
  
−
#'''(Insinuation)'''Use one article for all quests in a chain that use the same name.
  
−
#*Or one article for ''all'' quests in the chain?
  
−
#Name all quests with a disambiguation.
  
−
#*Including faction disambiguation.
  
−
#*First quest in a chain, or quest without a duplicated title would have (1).
  
−
#*Quest further into a chain, regardless of title, would be disambiguated by it's place in the chain?
  
−
#**For Example:
  
−
#**Quest:Title1 (1)
  
−
#***Quest:Title2 (2)
  
−
#****Quest:Title1 (3)
  
−
#Quests that are not in the same chain, but have the same title should be disambiguated by the zone they are in.
  
−
#*Starting zone, or involved zone?
  
−
--<span style="font-size: 0.85em; font-family: arial, 'comic sans'; padding: .2em .3em; border: 1px #504c50 solid;background-color: #000000">'''[[User:DuTempete|<span style="color:maroon">DuTempete</span>]]''' <small>[[User talk:DuTempete|<span style="color:olive">talk</span>]]<span style="color:maroon">|</span>[[Special:Contributions/DuTempete|<span style="color:olive">contr</span>]]</small></span> 01:07, 14 August 2007 (UTC)
  
   
  +
=== Method 1. Install from CDs ===
−
Here is my opinion:
  
  +
If you're lucky you can properly run the installation from the cds, which require that you are able to change between them while the installation runs.
−
#No way in hell. I'm not typing out quest IDs in links, and having to pipe them to fit them into a sentence as well.
  
−
#Not user friendly. Users are going to search the the title of the individual quest, so unless we create redirects from the individual names, this wouldn't make sense. If we did that, then links could get messy, since identifying sections and using pipes would be necessary to fit it into the article. There would be multiple links of this sort for almost every quest.
  
−
#Same as above.
  
−
#I think if it's not broken, don't fix it. I'm assuming that Laurlybot can have some way of identifying which quest comes first, and if two quests have the same name, otherwise, I'm sure we can prevent it from doing anything at all, if there is a problem, and it can be manually requested, once someone has identified how the problem should be solved. Numbering by place in the quest chain, regardless of title, would only add to the confusion. Part of the quest boilerplate is a listing of the chain progression, and it should suffice.
  
−
#I definitely think this needs to be added to the policy, but only for cases where a duplicate title is found. And in this case, ''both'' articles should contain the disambiguation. [[Quest:Return to the Marsh]] should be [[Quest:Return to the Marsh (Mage)]], as well as having [[Quest:Return to the Marsh (Zangarmarsh)]]. Zone disambigs should come first in a listing, if faction and numbering come into play. So, the proper order would be (zone, faction, #).
  
−
--<span style="font-size: 0.85em; font-family: arial, 'comic sans'; padding: .2em .3em; border: 1px #504c50 solid;background-color: #000000">'''[[User:DuTempete|<span style="color:maroon">DuTempete</span>]]''' <small>[[User talk:DuTempete|<span style="color:olive">talk</span>]]<span style="color:maroon">|</span>[[Special:Contributions/DuTempete|<span style="color:olive">contr</span>]]</small></span> 01:24, 14 August 2007 (UTC)
  
   
  +
Simply put disc 1 in the CD or DVD drive, and do the following (replace /media/cdrom0 with wherever you mount your cds):
  +
wine /media/WoWDisc1/Installer.exe
   
  +
Some dialogs during installation may appear blank or garbled, and the installer may even hang for up to 5 minutes at 100% CPU, while appearing to be doing nothing. Simply wait and click next when possible.
−
:My own not-so-humble opinions are well known to those that have borne the brunt of them, and not applicable to most other people. But in this case...
  
−
:;Chains
  
−
::Having invented the genre, I felt entirely free to name quest chains as I saw fit. They sometimes have the name of the first or last quest in the chain. Often, though, they were named based on the theme of the chain. (eg 'the Terokkar mana bomb') Where I encounter older, automated quest chain names (eg Quest Name/Quest Chain), I try to...
  
−
::#Make a dedicated quest chain page, named " 'something' quest chain" if it is noteworthy
  
−
::#incorporate it into existing pages if short and not noteworthy
  
−
::#leave the page as a transclusion page, but remove it from the Quest Chains category
  
−
::* Where the first quest of a chain is used as a transclusion page for the rest of the chain, I generally only disturb these if (and when) I make a dedicated quest chain page.
  
−
:;Equivalent quests
  
−
::Where pages existed before, I've followed the existing conventions. Where they didn't...
  
−
::# Alliance/Horde - Quite a few quests in Terokkar forest are identical for alliance and horde. I created a single page and gave quest boxes for both sides. In most cases, these got 'voted down', resulting in 3 pages per quest: one horde, one alliance, one disambiguation.
  
−
::# location (eg 'Gnome Engineering') - When they were precisely identical, I did as above; create one page with the base quest name. Where they weren't, I split them up, using (location, faction) (I think)
  
−
:; Sequence: Always, I use the base name for the first quest in the chain, and appended the sequence number for the following ones.
  
−
:; Combinations - where location, sequence, and/or faction conspired ... memory fails me. I THINK I have used (faction, location, sequence), but I don't recall any cases where location and faction were both factors in disambiguating the name.
  
−
:; Disambig page - For any disambig page, my philosophy is: describe the similarities on the disambig page. Two nearly identical quests? Describe them 'nearly completely' right there, and leave the 'horde'/'alliance' pages for those who favor them.
  
−
:--[[User:Eirik Ratcatcher|Eirik Ratcatcher]] ([[User talk:Eirik Ratcatcher|talk]]) 23:11, 19 February 2009 (UTC)
  
   
  +
''Note: If the text is too small, and it annoys you: Please install msttcorefonts per instruction of your distribution.''
−
== Battle pages ==
  
   
  +
If everything works like it should, then the installation will run for a while and then ask for disc 2, you change CDs and it should continue until it asks for the next one and so forth, if it doesn't work, however, you will continue to receive the "Please insert Disc 2" Warning repeatedly. An easy way is to unmount Disk 1 then insert disk 2, it will take a few seconds for it to load and mount, but it will load. Follow these for the rest of the disks and it should be ready to go. If it still doesn't work, skip to method two.
−
A while ago I began creating a series of articles devoted to battles, using Wookiepedia as my model: A template to describe place, outcome, combatants, etc. Each article was named as most battles are named in the real world: Type of battle and place. However, [[User:Baggins|Baggins]], who has the annoying hobby of moving and renaming everything that doesn't fit his views, has moved every single article by using the names of the mission in which each battle is featured, even moving battles that are merly backstory. He has done so without the proper discussion. There's no naming policy for Battles, so let's I believe we should settle with voting before and Edit War between him and those who have created other articles following my convention begins.--[[User:Gonzalo84|Gonzalo84]] 13:52, 12 September 2007 (UTC)
  
   
  +
If you have problems ejecting CDs in wine try:
−
The reason I named each battle the way I did, its simply because that was, in my opinion, the closest you can get to an encyclopedia. And BTW, the Battle of Mount Hyjal should be named that way because there's even an instance named Battle of Mount Hyjal.--[[User:Gonzalo84|Gonzalo84]] 13:57, 12 September 2007 (UTC)
  
  +
Start winecfg, then select Drives, auto detect drives
  +
The you'll probably get a Drive Letter like L: /media/WoWDisc1/
  +
Now you can use wine eject L:
  +
Then press the eject button on your CD/DVD drive.
  +
For the next CD you'll have to run wincfg again and substitute /media/WoWDisc1/ to ... WoWDisc2 and so on.
  +
So the wine eject will work without a Problem.
   
  +
====No Installer.exe?====
−
: We use official names where possible. One thing we certainly don't do is make up our own names for battles and capitalise them to make them look official. {{User:Kirkburn/Sig3}} 17:48, 12 September 2007 (UTC)
  
  +
This may primarily be a Fuse problem, but may appear on other systems not using Fuse as well. Run the following command from a terminal:
   
  +
sudo mount -o remount,unhide /dev/cdrom
−
::"there's even an instance named Battle of Mount Hyjal"
  
−
:Actually the name of the instance is [[Battle for Mount Hyjal]], and yes we stick to official titles. As Kirkburn said, we don't make up names, or capitalize them to try to make them look official..[[User:Baggins|Baggins]] 17:57, 12 September 2007 (UTC)
  
−
::I'm apathetic to this, but I lean more toward the view that we use official names if possible. --[[User:Sky2042|Sky]] ([[User talk:Sky2042|t]] · [[Special:Contributions/Sky2042|c]] · [http://www.wowhead.com/?user=Skyfire w]) 02:00, 13 September 2007 (UTC)
  
−
:::As someone who's not familiar with the Warcraft universe outside of WoW, I was pretty confused to go to a page called [[Misconceptions]] and read about a battle that was called something else. I had to follow a few links to figure out where that name came from. I think if a game campaign name is used as the title, then the intro to the article should reference that name, eg "'''Misconceptions''' is the first mission in the [[Whatever]] campaign covering The Third Battle of Dalaran", or whatever. It would also help IMO if the article was clear whether it was lore/history, or a description of a game element (or to separate these in sections if it refers to both). -- [[User:Harveydrone|Harveydrone]] ( [[User_talk:Harveydrone|talk]] | [[Special:Contributions/Harveydrone|work]] ) 18:00, 13 September 2007 (UTC)
  
   
  +
Note that your CD drive may not be /dev/cdrom! Check by running the command <code>mount</code> without arguments and look for a reasonable device (cd#, sr#, etc...)
−
::::Just a note, the problem with [[Misconceptions]] was only because it was linked to the wrong campaign. It is now quite clear where the name comes from. -- [[User:Raze|Raze]] 02:43, 14 September 2007 (UTC)
  
   
  +
====Problems mounting the DVD (collectors edition for [Vanilla] and [TBC] and standard for [WotLK]) ====
−
::Here is the problem, Misconceptions was not called something else. The other name in the article was fanfic and doesnt' exist in any official source. We are slowly working to correct this and remove all the references to the fake names, and link into source material. Please be patient.
 
  +
The issues might be related to either a defective (auto-)mount for the Hybrid Disks used (ISO 9660 and HFS+) or defective (auto-)mount without UDF support.
  +
For the Hybrid disks please refer to the specific documentation available on the internet. However the most likely cause is the missing UDF support when mounting the disc.
  +
In case it is mounted please unmount it
   
  +
umount /dev/drivename (e.g. cdrom)
−
::As for your concern of it being about game element or lore/history. I'd have to say its both. In warcraft III and the earlier RTS games it was all pretty much tied together at the hip. The later books rarely describe these earlier encounters except occasionally. Some were described in small paragraph descriptions giving an overall outcome, but hardly went into any details, or gave names to the battles.[[User:Baggins|Baggins]] 18:02, 13 September 2007 (UTC)
  
   
  +
then use the following line to mount it again with UDF support:
−
Thats because battles are named after the place they happen. Besides, what would yo do, Baggins, about the final two missions of the Scourge campaing of Reign of Chaos. Two missions, one battle. Under your convention, we should have an article using the name of the two missions, whereas in my convention, we would use the much simpler title of "Siege of Dalaran", or "First Battle of Dalaran". These battles are the only case in which there are no official names, therefore we need to develop an accurate naming policy, not based on the policy we use for units, since every unit has an official name.--[[User:Gonzalo84|Gonzalo84]] 20:24, 13 September 2007 (UTC)
  
   
  +
mount -t udf -o ro,unhide,uid=1000 /dev/drivename /mountpoint (e.g. /mnt)
−
::Each level will have its own article. It makes it easier to keep track of the information that way.[[User:Baggins|Baggins]] 23:42, 13 September 2007 (UTC)
  
−
:::Should*. Nothing is set in stone until a vote is had, and not even then; policies can be overturned if the populace feels it. --[[User:Sky2042|Sky]] ([[User talk:Sky2042|t]] · [[Special:Contributions/Sky2042|c]] · [http://www.wowhead.com/?user=Skyfire w]) 02:24, 14 September 2007 (UTC)
  
   
−
:Apart from the policy, the official mission names are much clearer anyway. I found the old battle names quite hard to follow since I don't know the exact location each mission took place, and I'm sure not many users do. Since the missions are numbered it makes it much clearer, and names like [[The Siege of Dalaran]], [[Under the Burning Sky]], and [[By Demons Be Driven]] are what my mind associate with those battles anyway. What's the reason to make up names if they're not gonna be more helpful. -- [[User:Raze|Raze]] 02:56, 14 September 2007 (UTC)
  
   
  +
===Method 2. Copy CDs to HD===
−
Added <s>Template:Warcraft III Campaign</s>[[Template:Warcraft III campaigns]] to help navigate through the campaigns while browsing through the mission names. Examples - [[Curse of the Blood Elves]], [[Legacy of the Damned]] (Stole the dungeon template design). What do you think? -- [[User:Raze|Raze]] 03:26, 14 September 2007 (UTC)
  
  +
Create a new folder on your computer. Copy all of the files from the first CD and all but the Installer.exe file from the rest to this directory on your hard drive (overwrite when prompted). Copying the Installer.exe from the other CD's will cause the install to fail with
  +
Unrecognized key "options". (AttributeParser::Parse)
   
  +
Then run:
−
: Please remember to categorise templates! (Fixed) {{User:Kirkburn/Sig3}} 03:57, 14 September 2007 (UTC)
  
  +
cd /<path-to-directory>/
  +
wine Installer.exe
   
  +
Replace <path-to-directory> with the right path to the directory where you copied all the files. You should now have the installation running, but make sure the CD media is out of the drive or it will check there and you'll be stuck in it again.
−
== Spells? ==
  
   
  +
===Method 3. Copy or run from Win===
−
Should there be a Spell:SpellName Naming for spells? [[User:Terrybader|~Terry]] 16:17, 21 December 2007 (UTC)
  
  +
You can also just install WoW in Windows and then copy the entire World of Warcraft folder over from your Windows installation.
   
  +
Or if you've already got WoW installed on your Windows partition, you can just use Wine to launch WoW directly from this installation. There is an added benefit to doing this, if you actively multiboot between Linux and Windows, because you will only need to have one copy of WoW on your hard drive for it to run in both environments. Please keep in mind that you must have both read and write access to your Windows partition for this to work, and only the most recently released GNU/Linux distributions, are currently providing write access to NTFS (Windows XP) partitions out of the box. If you do not have write access to your NTFS partition, you will need to consult with your distributions documentation for directions on enabling the NTFS-3G driver, which adds this feature.
−
== NPC vs. RPG capitalization ==
  
   
  +
Note: Using this method results in there being no entries for WoW in Wine's registry, but this does not cause any issues at all with running WoW.
−
If the RPG lists info on a overall type of Creature, and an obscure creature exists by this name in WoW, should...
  
−
 
−
* the info go on the obscure Mob page with the mob info ([[Fleshbeast]] or [[Nightsaber]])?
  
−
* there be two pages with the Mob as it is cased in WoW, and the RPG info in lower case ([[Blue Dragonspawn]]/[[Blue dragonspawn]] or [[Carrion Grub]]/[[Carrion grub]] or [[Core Hound]]/[[Core hound]] or [[Void Terror]]/[[Void terror]])?
  
−
* there be two pages with how it is cased in WoW, and how it is cased in WoW with a (Mob) at the end ([[Blue Dragonspawn]]/[[Blue Dragonspawn (mob)]], [[Grell]]/[[Grell (mob)]])?
  
−
* the info be like on [[Bloodpetal]] or [[Nightsaber]] where the lore has taken the place of the info about the mob by that name deliberately?
  
   
  +
Note 2 : Some computers might experience low FPS , while trying to run WoW in opengl mode . In that case , removing Config.wtf file ( it is localised in WTF folder ) , running WoW to generate that file again , and then making changes ( to opengl mode ) might help. Make sure , to give read/write access to WTF folder ( otherwise WoW will crash ). Add this line to your Config.wtf file using your favorite text editor:
−
I would prefer if there was a written rule.--{{User:Sandwichman2448/Sig}} 21:27, 22 December 2007 (UTC)
  
−  
−
: Yes, there should be. I'd go with:
  
−  
−
* Where the mob is named differently (including case), have the articles as written. This will mean the lore is lowercase, whilst the mob is title case.
  
−
* Where the names are identical, have the mob take (Mob).
  
−  
−
:Covers all possibilities? {{User:Kirkburn/Sig4}} 17:54, 24 December 2007 (UTC)
  
−  
−
== Vanity redirects ==
  
−  
−
Since I've been rather zealously deleting vanity guild/character redirects (and created {{t|vanity}}), perhaps it's time it gets put on the policy page? Something to the effect of:
  
−  
−
:Vanity redirects to articles not in the main namespace as per other portions of this policy (e.g. [[WW:GUILD]]/[[WW:PA]]/[[WW:PC]]) may not be created in the main namespace. --[[User:Kaydeethree|<span style="cursor:help;" title="WoWWiki Admin">k</span>]]_[[User_talk:Kaydeethree|d]]<sup>[[Special:Contributions/Kaydeethree|3]]</sup> 01:46, 8 January 2008 (UTC)
  
−  
−
::And whats the problem with a redirect, if that page is nonexistant? --[[User:TheAdamant|TheAdamant]] 20:20, 17 January 2008 (UTC)
  
−
:::It might possibly need to be in the future. --[[User:Sky2042|Sky]] ([[User talk:Sky2042|t]] | [[Special:Contributions/Sky2042|c]] |<span class="plainlinks"> [http://www.wowhead.com/?user=Skyfire w]</span>) 02:10, 19 January 2008 (UTC)
  
−  
−
The word is "possibly." The page can be changed then, its not like anything on this site is permanent. Its rather stupid to implement this in my PoV. It seems like a desperate attempt to isolate pages. --[[User:TheAdamant|TheAdamant]] 14:33, 21 January 2008 (UTC)
  
−  
−
:Well seeing as no one else said it.. Main namespace vanity redirects show an unfair and advantageous bias towards those lucky articles that have an opertunity to have a main namespace redirect. It's also there not polute the namespace with information from other namespaces which are subject to different rules, as it's being presented under the guise of main namespace information to browsers (eg. a user page in the main namespace). If i'm not mistaken, a search for the article will also go to the redirect, rather than correctly provide alternative search results because the article doesn't actually exist. This is even more of a problem if a user is searching the main namespace only, as they will recieve results they do not want. --&nbsp;<ul style="font-size: 0.85em; margin: 0; padding: 0; list-style: none; list-style-type: none; list-style-image: none; display: inline; white-space: nowrap"><li style="display: inline;"><imagelink>http://www.zealvurte.co.uk/temp/sig-av/wiki_zeal.png|User:Zeal</imagelink></li><li style="display: inline;"><imagelink>http://www.zealvurte.co.uk/temp/sig-av/wiki_talk.png|User talk:Zeal</imagelink></li><li style="display: inline;"><imagelink>http://www.zealvurte.co.uk/temp/sig-av/wiki_contribs.png|Special:Contributions/Zeal</imagelink></li><li style="display: inline;"><imagelink>http://www.zealvurte.co.uk/temp/sig-av/wiki_end.png|User:Zeal</imagelink></li></ul>&nbsp; 15:18, 21 January 2008 (UTC)
  
−  
−
== "The ..." articles; vote start ==
  
−  
−
{{Vote/Vote}} <!-- Possible tags: Vote/Vote Vote/Closing Accepted Declined -->
  
−
===Votes===
  
−
Whether to '''remove''' the part of the policy where "The" should not be a starting part of articles, and namely zones.
  
−  
−
<div style="margin-left: 0.5em;">
  
−
;<span style="color:#44CC44;">Yes</span>: <!-- Add: {{vote|Yes|~~ ~~|optional comment}} below (remove space between "~ ~")-->
  
−
{{vote|Yes|{{User:WoWWiki-Murph/Sig}} 08:40, 21 December 2008 (UTC)|But replace it with a rule that says it should only be used where it is commonly capitalised *or* is consistently used as a complete label (e.g. full faction name, full zone name, titles, organisations). If it's essentially optional, e.g. you can say "the Cenarion Circle" without raising any eyebrows, but it's clear from other usage that "Cenarion Circle" is the faction name, then omit "the". My vote is to improve what we have, not simply remove it.}}
  
−
{{vote|Yes|[[User:Benitoperezgaldos|Benitoperezgaldos]] ([[User talk:Benitoperezgaldos|talk]]) 22:59, September 26, 2009 (UTC)|If Blizzard always use the word "the" in the zone name, then, who are we to change that?; We should stick to what Blizzard uses.}}
  
−
{{vote|Yes|-- [[Image:IconSmall_BloodElf_Male2.gif‎]][[Image:IconSmall Rogue.gif]] [[User:Sebreth|Sebreth]] ([[User talk:Sebreth|talk]]) 22:37, December 16, 2009 (UTC)|Exactly what Benito said. See my post below.}}
  
−
{{vote|Yes|[[User:Navalu|Navalu]] ([[User talk:Navalu|talk]]) 09:28, December 17, 2009 (UTC)|it makes the articles look ugly, if you ask me.}}
  
−
{{vote|Yes|[[User:Bfx|Bfx]] ([[User talk:Bfx|talk]]) 15:47, December 21, 2009 (UTC)}}
  
−
{{vote|Yes|[[User:Ewolfg1|Ewolfg1]] ([[User talk:Ewolfg1|talk]]) 02:00, February 5, 2010 (UTC)|If blizz is calling it with a The or A or w/e why differ from that?}}
  
−
{{vote|Yes|[[User:Monty845|Monty845]] ([[User talk:Monty845|talk]]) 21:48, June 8, 2010 (UTC)|Its better to deal with this on a case by case basis}}
  
−
{{vote|Yes|[[User:Ddcorkum|ddcorkum]] ([[User talk:Ddcorkum|talk]]) 15:56, October 11, 2010 (UTC)|[[Eye_(Tempest_Keep)]] should be called "The_Eye_(Tempest_Keep)". Its not normal English, but it is what Blizzard does.}}
  
−  
−
;<span style="color:#CC4444;">No</span>: <!-- Add: {{vote|No|~~ ~~|optional comment}} below (remove space between "~ ~")-->
  
−
{{vote|No|sig=[[User:Sky2042|Sky]] ([[User talk:Sky2042|t]] · [[Special:Contributions/Sky2042|c]] · [http://www.wowhead.com/?user=Skyfire w]) 03:52, 30 July 2008 (UTC)||See below}}
  
−
{{vote|No|{{User:Pcj/sig}} 04:52, 30 July 2008 (UTC)|Seems arbitrary.}}
  
−
{{vote|No|--[[User:Eirik Ratcatcher|Eirik Ratcatcher]] ([[User talk:Eirik Ratcatcher|talk]]) 18:53, 26 February 2009 (UTC)|comments below}}
  
−
{{vote|No|-- [[User:Harveydrone|Har]][[User_talk:Harveydrone|vey]][[Special:Contributions/Harveydrone|drone]] 20:50, 6 March 2009 (UTC)|but I may be confused....}}
  
−
{{vote|No|{{User:Sandwichman2448/Sig}} 22:42, December 16, 2009 (UTC)|See comments.}}
  
−
{{vote|No|sig={{User:Gourra/Sig2}} 23:13, June 8, 2010 (UTC)||Nominated, and changed my mind.}}
  
−
</div>
  
−  
−
=== Comments ===
  
−
<div style="margin-left: 0.5em;">
  
−
<!-- Add :your comments <nowiki>--~~~~</nowiki> below -->
  
−
</div>
  
−
<hr style="color: #555;" />
  
   
  +
SET gxAPI "OpenGL"
−
<!-- END OF VOTING BOOTH AND COMMENTS -->
  
−
I'm getting a real headache now with the articles who start with "The", namely [[The Nexus]] but also other zones like [[The Barrens]] and [[The Oculus]]. According to the current policies the "The" should be ''removed entirely'' from the article name and be referred to as just the zone after the "The". To me this sounds ridiculous as I can't find a real good reason. Perhaps only because of sorting issues, but that's what <nowiki>{{DEFAULTSORT:<zone>}}</nowiki> is so good for.
  
   
  +
Note 3 : Intel 945 integrated video chipset does not take kindly to OpenGL. If your game crashes frequently, try not using OpenGL.
−
Now I want a vote on whether you want to '''remove''' the part of the policy where "The" should not be a starting part of articles, and namely zones. {{User:Gourra/Sig2}} 03:12, 30 July 2008 (UTC)
  
   
  +
In a system with Fuse, such as Ubuntu or Fedora, a default install of wine will run WoW from a mounted drive that has World of Warcraft installed just by adding the -opengl flag at the end:
−
:The reason it exists is because actual name of something may not be "The Barrens", but "the Barrens". Another example is the Dragonblight, which is not "The Dragonblight", even if it is referred to with a "the". {{User:Kirkburn/Sig4}} 03:30, 30 July 2008 (UTC)
  
  +
wine "/media/windowsdrive/WorldofWarcraft/Wow.exe" -opengl
−
::The zone name, going after the ''actual'' in-game zone, is [[The Barrens]] and should be called that. [[Dragonblight]] isn't called "The Dragonblight" in the same way, and you shouldn't take that as an example. {{User:Gourra/Sig2}} 03:34, 30 July 2008 (UTC)
  
  +
where "windowsdrive" is the name of the drive in /media that you have mounted. Replace the path name with your install! You could have installed it in Program Files or a different folder. Something to note; if you run WoW in Windows after running it in linux, you will have to change a few video settings back, like the shadow quality. See https://help.ubuntu.com/community/MountingWindowsPartitions for instructions on getting your Windows drive to mount automatically on startup using fstab.
−
:::That's rather arbitrary &mdash; why-so? We have a definite rule here at the moment, and that is to redirect "The x" to "x" (unless the article is on an NPC/item, though I'm not sure why anymore on the former). Redirects are cheap, so if someone wants to use the 'the', they can. It also ''does'' make categorization a breeze &mdash; while a defaultsort isn't difficult, it's not something we need, I don't think. In other words, I think Kirk's reading of it is correct. --[[User:Sky2042|Sky]] ([[User talk:Sky2042|t]] · [[Special:Contributions/Sky2042|c]] · [http://www.wowhead.com/?user=Skyfire w]) 03:51, 30 July 2008 (UTC)
  
   
  +
===Method 4. Download client===
−
::Only issue I have is with categories... both ways are used:
  
  +
Or if you have lost a CD, do not have access to a cd drive or simply would not want to bother with patching and messing with the CD's, you can download the trial version, which is in fact the full game almost fully patched, from the blizzard torrentlike downloader. They work very nicely with wine. You may be asked to log in with your WoW account.
−
:::Examples where 'The' is used [[:Category:The Barrens]], [[:Category:The Hinterlands]], and [[:Category:The Eye]].
 
−
:::Examples where 'The' is not used [[:Category:Slave Pens]], [[:Category:Botanica]], and [[:Category:Steamvault]]. {{User:Coobra/Sig3}} 04:07, 30 July 2008 (UTC)
  
   
  +
All European WoW clients in all languages:
−
This policy hardly makes any sense. I'm new to WoWWiki, but I'm no stranger to them; I'm admin to two. Though each are understandably not as large as this one, I still think it's important to be as specific as possible to what's canon. It's like, going by the naming policy and using Undercity as an example, it is always referred to by characters as "the Undercity," but appears solely as "Undercity" in the zone name, so it's reasonable that the article be titled simply "Undercity." But in the case of zones that are referred to both in lore and by zone name prompt with "The" or such, not that it's inaccurate, but then again it's not necessarily accurate either. [[User:Mantecon|Mantecon]] ([[User talk:Mantecon|talk]]) 04:24, 31 July 2008 (UTC)
  
  +
* [http://www.wow-europe.com/en/burningcrusade/download/ WoW-Europe.com]
   
  +
US Version:
−
:It's actually a very rare case when you end up with an article with has to remain with the "the" &mdash; [[Special:PrefixIndex/The|As you can see]], there aren't many which aren't redirects. If they aren't redirects, then the majority I can safely say are mobs or items. --[[User:Sky2042|Sky]] ([[User talk:Sky2042|t]] · [[Special:Contributions/Sky2042|c]] · [http://www.wowhead.com/?user=Skyfire w]) 17:03, 13 August 2008 (UTC)
  
  +
* [https://www.worldofwarcraft.com/account/download_wow.html Worldofwarcraft.com]
  +
* [http://www.worldofwarcraft.com/downloads/files/pc/wowclient-downloader.exe WoW Vanilla client]
  +
* [https://www.worldofwarcraft.com/account/download/bc-clientdownload.html Burning Crusade client]
   
  +
Alternatively you can simply log into your account at your regional WoW community site, and download the full client from the [https://us.battle.net/account/management/wow/dashboard.html Battle.net Dashboard]
−
How helpful would it be to follow Blizzard's naming conventions?
  
−
[[User:Jsgelk@yahoo.com|Jsgelk@yahoo.com]] ([[User talk:Jsgelk@yahoo.com|talk]]) 00:09, 3 December 2008 (UTC)
  
   
  +
In order to use the Blizzard Downloader effectively, you must 1) open certain ports on your computer and 2) enable port forwarding on your router.
−
I find that what I would have said, has been said. DEFAULTSORT is cheap and easy to add, and so often appropriate, and not just on "the" pages. And redirects can be made that go in both directions ("the" <--> "no the") depending on which name wins the popular vote. --[[User:Eirik Ratcatcher|Eirik Ratcatcher]] ([[User talk:Eirik Ratcatcher|talk]]) 18:57, 26 February 2009 (UTC)
  
   
  +
# The easiest way to open these ports is to use the open-source firewall program [http://www.fs-security.com/ Firestarter]. When it is running, select the "Policy" tab, right-click in the Allow Service area, and select Add Rule. Under port, type 6112 and make sure that the "Anyone" radio button is selected. Make a note in the comments field that this port relates to Blizzard. Repeat these steps for ports 3724 and for the range 6881-6999 (which will be recognized as BitTorrent ports).
−
I'm a little confused. The policy is to exclude "the" from all other articles without their own policy, unless it's capitalized in running text. There is no zone page specific naming policy that I see, though I thought there was one at one time (to use the exact zone name from the game). So the policy as is should exclude "the" from most examples I've seen (the Barrens, the Crossroads, the Slave Pens). I think this policy should stay as is. It's a different question whether there should be a new policy for naming zone articles, and what it should be. -- [[User:Harveydrone|Har]][[User_talk:Harveydrone|vey]][[Special:Contributions/Harveydrone|drone]] 21:00, 6 March 2009 (UTC)
  
  +
# Next, configure your router to forward those ports on the router to your computer only. The steps are similar to the above, but vary slightly from router to router and may be found on Blizzard's website: http://www.blizzard.com/support/wow/?id=aww01199p
   
  +
===Method 5. In case of having an intel graphics===
−
:I agree that even if we, in the case of zones and subzones, go with exactly the minimap says, there will still be problems. Things like articles are rarely capitalized in running text, just look at race names. It is too inconsistant, and many 'also known as' lists are messes as it is. I do '''not''' want to see anything like [http://www.wowwiki.com/index.php?title=Barrens&diff=2050902&oldid=2050619 this], but backwards. Redirects and categorization do not seem to be an issue, beyond the effort of doing it.--{{User:Sandwichman2448/Sig}} 22:26, September 26, 2009 (UTC)
  
   
  +
Follow the steps from this blog:
−
I believe that the articles should be like... It should be [[The Barrens]], as that is what it is referred to in-game. The game specifically calls it "the Barrens" in quest dialogue and stuff, so it should be part of the article name. However, as the quest dialogue does capitalize the "the", the "the" in the zone name should not be capitalized outside of the article name and the beginnings of sentences. It may be easier to name it simply "Barrens", but it is incorrect, as Blizzard refers to it as "the Barrens". -- [[Image:IconSmall_BloodElf_Male2.gif‎]][[Image:IconSmall Rogue.gif]] [[User:Sebreth|Sebreth]] ([[User talk:Sebreth|talk]]) 09:22, December 17, 2009 (UTC)
  
  +
* [ http://translate.google.com.br/translate?hl=pt-BR&langpair=pt|en&u=http://www.ladolinuxdaforca.com.br/linux/jogos/instalando-world-of-warcraft-linux-intel&prev=/translate_s%3Fhl%3Dpt-BR%26q%3Dwww.ladolinuxdaforca.com.br/linux/jogos/instalando-world-of-warcraft-linux-intel%26sl%3Den%26tl%3Dpt]
  +
I google it so much and this page get me to the solution.
   
  +
== Playing ==
−
The article should match whatever the name is in game. If item/zone/object of your desire has the "the" so be it. This will eliminate confusion when new players come here for resources. For a concrete example, the player title [[Merrymaker]] does not have a "the" whereas [[The Hallowed]] does. [[User:Ariule|Ariule]] ([[User talk:Ariule|talk]]) 23:52, December 17, 2009 (UTC)
  
  +
=== Start from the Desktop Icon ===
  +
Double click the icon you find on your Desktop titled World of Warcraft, this will start the launcher. If you have never used something requiring HTML rendering with Wine you will be prompted to download and install the Gecko rendering engine, you should do this as it will enable the WoW Launcher to do display news.
   
  +
=== Start from the Terminal ===
−
It's obvious that this isn't going to be getting any more votes. Is this going to just stay open indefinitely then? [[Image:Ability_rogue_shadowstrikes.png|20px|link=User:Sebreth]] [[User:Sebreth|Sebreth]] <span style="font-size:10px; color:aqua">([[User_talk:Sebreth|T]].[[Special:Contributions/Sebreth|C]])</span> 23:44, January 9, 2010 (UTC)
  
  +
Starting from the terminal is simple, just enter:
  +
wine "C:\\Program Files\\World of Warcraft\\Launcher.exe"
  +
(install when prompted about the Gecko rendering engine)
   
  +
Or, dive right into the game with:
−
:A side has to win by five for three days for anything to happen. Unless one side is made up of idiots or sockpuppets, but I do not see that here.--{{User:Sandwichman2448/Sig}} 23:49, January 9, 2010 (UTC)
  
  +
wine "C:\\Program Files\\World of Warcraft\\WoW.exe"
   
  +
Be certain to add <code>-opengl</code> to the command if you didn't add the gxApi line as described in the [[#Config.wtf|Config.wtf]] section above.
−
::I am aware of this. However, Yes has been winning by one for at least a month now and I highly doubt there will ever be a victory by five votes. [[Image:Ability_rogue_shadowstrikes.png|20px|link=User:Sebreth]] [[User:Sebreth|Sebreth]] <span style="font-size:10px; color:aqua">([[User_talk:Sebreth|T]].[[Special:Contributions/Sebreth|C]])</span> 23:53, January 9, 2010 (UTC)
  
   
−
===Idea===
 +
=== Desktop menu icon ===
   
  +
To make an icon for the desktop menu in GNOME or KDE:
−
I am not sure if anyone brought up this idea in the past. What if we name articles that we know have a "The" in them, like "The Kalu'ak", like this instead "Kalu'ak, The"? This way we keep the word "The" but it does not mess up the whole alphabetized policy. It can also work with something like "Stromgarde, Kingdom of" so that we get the whole name in but the word "Stromgarde" is in front. [[User:Rolandius|Rolandius]] [[Image:Paladin.gif|25px]] <small>([[User talk:Rolandius|<span title="Rolandius's Talk">talk</span>]] - [[Special:Contributions/Rolandius|<span title="Rolandius's Contributions">contr</span>]])</small> 07:03, 21 December 2008 (UTC)
  
   
  +
* Download [http://images.wikia.com/wowwiki/images/d/d3/Wow-icon-scalable.svg the application icon] to some directory.
−
:I can't say I like that style of naming. It looks ugly to me, makes the URLs ugly, and I don't really see what it buys us. With judicious use of <code><nowiki>{{DEFAULTSORT:<key>}}</nowiki></code>, and <code><nowiki>[[Category:<name>|<key>]]</nowiki></code>, the automatic aplhabetisation is easily tweaked for the relatively few occasions that it's necessary to do so, and it's not difficult to adjust manually created lists to look good. If need be, templates can relatively easily strip standard prefices from <code><nowiki>{{PAGENAME}}</nowiki></code>, if that's an issue. What advantage do you think it gives over the current policy? Do you have some examples of lists or categories where it would look better the way you propose? I guess I'm really just trying to figure out what problem you are trying to solve. --{{User:WoWWiki-Murph/Sig}} 07:31, 21 December 2008 (UTC)
  
  +
* Open the menu editor by right-clicking the menu button on the GNOME/KDE panel, and create a new application entry. Choose the newly downloaded icon as the application icon. In the "Command line" field, you will need to write:
   
  +
wine '''''LAUNCHER'''''
−
::I was just wondering if there was a way of keeping the whole term of something in the title of an article when a term has something like "The" or "Kingdom of" in them, like "The Kalu'ak" and "Kingdom of Stromgarde" instead of naming the article just "Kalu'ak" and "Stromgarde". I picked Kalu'ak as an example because if you look at the NPCs in-game it says "The Kalu'ak" and not just "Kalu'ak". I picked Stromgarde as an example because everyone knows it was a kingdom. [[User:Rolandius|Rolandius]] [[Image:Paladin.gif|25px]] <small>([[User talk:Rolandius|<span title="Rolandius's Talk">talk</span>]] - [[Special:Contributions/Rolandius|<span title="Rolandius's Contributions">contr</span>]])</small> 07:44, 21 December 2008 (UTC)
  
   
  +
where '''''LAUNCHER''''' is the full path to the application .exe file, either Launcher.exe or WoW.exe (see above).
−
:::I have to admit, I'm about 50/50 on whether "The Kalu'ak" should come under the existing clause ''There is an important exception to this rule: "the", "a" or "an" is included when it would be capitalized if it appeared in text.''. As for Stromgarde, that's a trickier example - it's commonplace in WoW to simply refer to it as Stromgarde or Stromgarde Keep, and exceptionally rare to hear someone talking of the "Kingdom of Stromgarde". In real life, the "Kingdom of Fife" is typically just referred to in all as simply "[[wikipedia:Fife|Fife]]" - even the local government is simply "Fife Council", although it is well known in the local area as the "Kingdom of Fife", and it's not particularly unusual to hear that form of the name. I'm still less than convinced that reversing the names around a comma would be a step forwards. --{{User:WoWWiki-Murph/Sig}} 08:30, 21 December 2008 (UTC)
  
   
  +
In Xfce, there currently is no menu editor. You can instead create a text file in <code>~/.local/share/applications</code> named <code>wow.desktop</code>, and paste this:
−
::::I agree with you on "The Kalu'ak" as it could go either way. Although, in the case of "The Kalu'ak" it does have support in that in-game the info when you click on them says "The Kalu'ak" and the official website calls them "The Kalu'ak". With Stromgarde, it is more in lore where you see the word kingdom a lot. Although, I think there is an in-game book or two that talks about "The Seven Kingdoms". Another thing is that on WoWWiki, we do have "Kingdom of Stormwind" and "Kingdom of Azeroth" as articles and no one in WoW uses those terms. [[User:Rolandius|Rolandius]] [[Image:Paladin.gif|25px]] <small>([[User talk:Rolandius|<span title="Rolandius's Talk">talk</span>]] - [[Special:Contributions/Rolandius|<span title="Rolandius's Contributions">contr</span>]])</small> 10:21, 21 December 2008 (UTC)
  
   
  +
&#91;Desktop Entry&#93;
−
== Prepositions and articles in quest titles ==
  
  +
Name=World of Warcraft
  +
Exec=wine '''''LAUNCHER'''''
  +
Icon=Wow-icon-scalable.svg
  +
Terminal=false
  +
Type=Application
  +
Categories=Application;Game;
  +
StartupNotify=false
   
  +
Remember that you should also edit the Exec= line to reflect your WoW installation path, if you've installed to a special location.
−
It seems that Blizzard does not work consistently with prepositions (in, on, before etc.) and articles (the, a, an etc.) in quest titles. While some are written correctly, others are just capitalized. For example:
  
−
*[[Quest:The Might Of The Scourge]]
  
−
*[[Quest:In Search of The Excavation Team]]
  
−
*[[Quest:Cleansing of the Infected]]
  
   
  +
=== Troubleshooting===
−
Should we just follow the spelling Blizzard used in the game, or make a rule for it? I prefer to write prepositions and articles in lowercase.--[[User:Iggey|Iggey]] ([[User talk:Iggey|talk]]) 16:24, 29 January 2009 (UTC)
  
   
  +
See [[Wine troubleshooting]].
−
:MNSHO - First letter capitalized (wiki will do it anyway), and "name of quest in-game", so people searching for the quest can find it. (Part of what frustrates me so with disambiguations.) --[[User:Eirik Ratcatcher|Eirik Ratcatcher]] ([[User talk:Eirik Ratcatcher|talk]]) 18:59, 26 February 2009 (UTC)
  
   
  +
== Miscellaneous ==
−
::If we have a lot of frustration from horrible capitalization used by Blizzard, at least the most common variants can be given redirects. For instance, in the above "of the" examples, redirects with "of the", and "Of The" could be added. (Yes, took me a moment to see your point, sorry.) --[[User:Eirik Ratcatcher|Eirik Ratcatcher]] ([[User talk:Eirik Ratcatcher|talk]]) 19:02, 26 February 2009 (UTC)
  
  +
* For other relevant various information and tips please see [[Wine miscellaneous info]].
−
:::According to Pcj in [[Wowpedia talk:Village Pump#Prepositions and articles in quest titles]], we should always follow the spelling Blizzard used. Personally, I'm not too happy with this, because it causes a certain inconsistency. Making redirects is really no problem, but it's the policy itself that needs to be changed.--[[User:Iggey|Iggey]] ([[User talk:Iggey|talk]]) 00:49, 1 March 2009 (UTC)
  
  +
* For troubleshooting tips (including common problems and their workarounds), see [[Wine troubleshooting]].
  +
* For Linux Native Ventrilo check out [http://www.mangler.org http://www.mangler.org].
   
−
== CVar articles ==
 +
== References ==
  +
{{reflist}}
   
  +
== External links ==
−
Propose we add a CVar article naming policy, as some of the new cvars are now 2 words, and have the 2nd word capitalized. With this naming policy, it'll be easier to keep track of the cvars as they won't be moved to new name to follow "Other articles" naming rules (and thus the complete CVar list won't have to be updated as often).
  
  +
{{elink|site=WineHQ.org|link=http://winehq.org|desc=Official website}}
−
Something like the following should be acceptable?
  
  +
:{{elink|site=AppDB.WineHQ.org|link=http://appdb.winehq.org/|desc=The WineHQ Application Database}}
−
<br /><br />
  
  +
:{{elink|site=Wiki.WineHQ.org|link=http://wiki.winehq.org/winetricks|desc=Wine Wiki: Winetricks}}
−
CVar Articles
  
  +
[[Category:Linux]]
−
<br />
  
  +
[[Category:Technical support]]
−
Shortcut: WP:CVA
  
−
<br />
  
−
Console Variable articles are prefixed with "CVar " and then exactly as the console variable name, with the same capitalization and no whitespace (unless its part of the variable name). For example, CVar bgLoadThrottle and CVar cameraDistanceBarber Shop.
  
−
<br /><br />
  
−
Thoughts? Comments? [[User:Ressy|Ressy]] ([[User talk:Ressy|talk]]) 16:08, 22 October 2010 (UTC)
  
−
:Implementing as {{t|Grandfathered}} since this is already the practice. --{{User:Pcj/sig}} 16:12, 22 October 2010 (UTC)
  

Revision as of 23:27, 9 February 2011

"Wine" redirects here. For in-game drinks, see Drink#Alcoholic Drinks. For Alcoholic drinks, see Wine (disambiguation).
For dealing with common problems while using wine, see Wine troubleshooting.
Wine
File:Wine.png
Releases
Stable release 1.2.2
Development release 1.3.13 (4 February 2011)
Links
AppDB AppDB: WoW
WineHQ winehq.org
Latest commits

Wine is a free software application which aims to allow Unix-like operating systems on the x86 architecture to execute programs written for Microsoft Windows.

Introduction

This article primarily talks about setting up Wine for running the MS Windows version of WoW Icon update World of Warcraft. Wine also runs on Macintosh computers with x86 CPUs under Mac OS X, but since Blizzard makes a Mac OS X native World of Warcraft client, running it under Wine is unnecessary and even silly.

World of Warcraft had a client for Linux while it was in the beta phase of development, but it was later dropped and never officially released.[1] Currently, WoW is run on Linux by use of Windows compatibility layers. Given that the World of Warcraft client is no longer officially developed to work in Linux, the installation of it on Linux is a somewhat more involved process than on Windows, which it is streamlined to install more easily on. However, with some careful research, and a bit of patience, it's very possible to do so.

Alternatively a streamlined process of installation and windows installation conversion is available via Play On Linux.

Installation

This guide will only cover the Wine compatibility layer. It is however fully compatible with Crossover.

Before you begin the installation, you should run the following simple command, which will check whether your video card driver has DRI enabled, which allows WoW to run much faster (you may need to install package mesa-utils): 

glxinfo | grep rendering

Which should return a line similar to this:

direct rendering: Yes

If this line says "No", it means that the graphics data will be handled in software rather than directly by the graphics hardware, thus significantly reducing speed at which WoW will run. Thankfully if you are using relatively recent hardware, enabling DRI is usually just a configuration issue.

For more information about enabling DRI, refer to the information from your distribution's support guides on graphic card driver installation. For extended personal help, forums and chatrooms are usually a good bet. Just tell them what the Make and Model of your graphic card is and they will be able to point you in the right direction. As always, remember that search engines are your friend.

Distribution-specific methods

Different GNU/Linux distributions use different methods of installing software, which oftentimes makes it hard to make easy installation options available for all distributions, especially for large and complex projects like Wine. Luckily a lot of energy has been put into making the distribution native installation methods available for a large variety of popular distributions. Please see http://www.winehq.org/site/download and follow the installation directions for your particular distribution.

Compiling Wine

If you were unable to install Wine with a method found on that site, or if you are an experienced user wanting more control over the installation, then you may want to look into compiling Wine from source code. See the WineHQ wiki for information: http://wiki.winehq.org/Recommended_Packages


Installing WoW

This section explains four different methods of installing WoW. If the first method doesn't work for you, or you prefer a different approach, then simply skip to the next method and so on.

Method 1. Install from CDs

If you're lucky you can properly run the installation from the cds, which require that you are able to change between them while the installation runs.

Simply put disc 1 in the CD or DVD drive, and do the following (replace /media/cdrom0 with wherever you mount your cds): 

wine /media/WoWDisc1/Installer.exe

Some dialogs during installation may appear blank or garbled, and the installer may even hang for up to 5 minutes at 100% CPU, while appearing to be doing nothing. Simply wait and click next when possible.

Note: If the text is too small, and it annoys you: Please install msttcorefonts per instruction of your distribution.

If everything works like it should, then the installation will run for a while and then ask for disc 2, you change CDs and it should continue until it asks for the next one and so forth, if it doesn't work, however, you will continue to receive the "Please insert Disc 2" Warning repeatedly. An easy way is to unmount Disk 1 then insert disk 2, it will take a few seconds for it to load and mount, but it will load. Follow these for the rest of the disks and it should be ready to go. If it still doesn't work, skip to method two.

If you have problems ejecting CDs in wine try: Start winecfg, then select Drives, auto detect drives The you'll probably get a Drive Letter like L: /media/WoWDisc1/ Now you can use wine eject L: Then press the eject button on your CD/DVD drive. For the next CD you'll have to run wincfg again and substitute /media/WoWDisc1/ to ... WoWDisc2 and so on. So the wine eject will work without a Problem.

No Installer.exe?

This may primarily be a Fuse problem, but may appear on other systems not using Fuse as well. Run the following command from a terminal: 

 sudo mount -o remount,unhide /dev/cdrom

Note that your CD drive may not be /dev/cdrom! Check by running the command mount without arguments and look for a reasonable device (cd#, sr#, etc...)

Problems mounting the DVD (collectors edition for [Vanilla] and [TBC] and standard for [WotLK])

The issues might be related to either a defective (auto-)mount for the Hybrid Disks used (ISO 9660 and HFS+) or defective (auto-)mount without UDF support. For the Hybrid disks please refer to the specific documentation available on the internet. However the most likely cause is the missing UDF support when mounting the disc. In case it is mounted please unmount it

umount /dev/drivename (e.g. cdrom)

then use the following line to mount it again with UDF support:

mount -t udf -o ro,unhide,uid=1000 /dev/drivename /mountpoint (e.g. /mnt)


Method 2. Copy CDs to HD

Create a new folder on your computer. Copy all of the files from the first CD and all but the Installer.exe file from the rest to this directory on your hard drive (overwrite when prompted). Copying the Installer.exe from the other CD's will cause the install to fail with 

Unrecognized key "options". (AttributeParser::Parse)

Then run: 

cd /<path-to-directory>/
wine Installer.exe

Replace <path-to-directory> with the right path to the directory where you copied all the files. You should now have the installation running, but make sure the CD media is out of the drive or it will check there and you'll be stuck in it again.

Method 3. Copy or run from Win

You can also just install WoW in Windows and then copy the entire World of Warcraft folder over from your Windows installation.

Or if you've already got WoW installed on your Windows partition, you can just use Wine to launch WoW directly from this installation. There is an added benefit to doing this, if you actively multiboot between Linux and Windows, because you will only need to have one copy of WoW on your hard drive for it to run in both environments. Please keep in mind that you must have both read and write access to your Windows partition for this to work, and only the most recently released GNU/Linux distributions, are currently providing write access to NTFS (Windows XP) partitions out of the box. If you do not have write access to your NTFS partition, you will need to consult with your distributions documentation for directions on enabling the NTFS-3G driver, which adds this feature.

Note: Using this method results in there being no entries for WoW in Wine's registry, but this does not cause any issues at all with running WoW.

Note 2 : Some computers might experience low FPS , while trying to run WoW in opengl mode . In that case , removing Config.wtf file ( it is localised in WTF folder ) , running WoW to generate that file again , and then making changes ( to opengl mode ) might help. Make sure , to give read/write access to WTF folder ( otherwise WoW will crash ). Add this line to your Config.wtf file using your favorite text editor: 

SET gxAPI "OpenGL"

Note 3 : Intel 945 integrated video chipset does not take kindly to OpenGL. If your game crashes frequently, try not using OpenGL.

In a system with Fuse, such as Ubuntu or Fedora, a default install of wine will run WoW from a mounted drive that has World of Warcraft installed just by adding the -opengl flag at the end: 

wine "/media/windowsdrive/WorldofWarcraft/Wow.exe" -opengl

where "windowsdrive" is the name of the drive in /media that you have mounted. Replace the path name with your install! You could have installed it in Program Files or a different folder. Something to note; if you run WoW in Windows after running it in linux, you will have to change a few video settings back, like the shadow quality. See https://help.ubuntu.com/community/MountingWindowsPartitions for instructions on getting your Windows drive to mount automatically on startup using fstab.

Method 4. Download client

Or if you have lost a CD, do not have access to a cd drive or simply would not want to bother with patching and messing with the CD's, you can download the trial version, which is in fact the full game almost fully patched, from the blizzard torrentlike downloader. They work very nicely with wine. You may be asked to log in with your WoW account.

All European WoW clients in all languages:

US Version:

Alternatively you can simply log into your account at your regional WoW community site, and download the full client from the Battle.net Dashboard

In order to use the Blizzard Downloader effectively, you must 1) open certain ports on your computer and 2) enable port forwarding on your router.

  1. The easiest way to open these ports is to use the open-source firewall program Firestarter. When it is running, select the "Policy" tab, right-click in the Allow Service area, and select Add Rule. Under port, type 6112 and make sure that the "Anyone" radio button is selected. Make a note in the comments field that this port relates to Blizzard. Repeat these steps for ports 3724 and for the range 6881-6999 (which will be recognized as BitTorrent ports).
  2. Next, configure your router to forward those ports on the router to your computer only. The steps are similar to the above, but vary slightly from router to router and may be found on Blizzard's website: http://www.blizzard.com/support/wow/?id=aww01199p

Method 5. In case of having an intel graphics

Follow the steps from this blog:

I google it so much and this page get me to the solution.

Playing

Start from the Desktop Icon

Double click the icon you find on your Desktop titled World of Warcraft, this will start the launcher. If you have never used something requiring HTML rendering with Wine you will be prompted to download and install the Gecko rendering engine, you should do this as it will enable the WoW Launcher to do display news.

Start from the Terminal

Starting from the terminal is simple, just enter: 

wine "C:\\Program Files\\World of Warcraft\\Launcher.exe"

(install when prompted about the Gecko rendering engine)

Or, dive right into the game with: 

wine "C:\\Program Files\\World of Warcraft\\WoW.exe"

Be certain to add -opengl to the command if you didn't add the gxApi line as described in the Config.wtf section above.

Desktop menu icon

To make an icon for the desktop menu in GNOME or KDE:

  • Download the application icon to some directory.
  • Open the menu editor by right-clicking the menu button on the GNOME/KDE panel, and create a new application entry. Choose the newly downloaded icon as the application icon. In the "Command line" field, you will need to write:
wine LAUNCHER

where LAUNCHER is the full path to the application .exe file, either Launcher.exe or WoW.exe (see above).

In Xfce, there currently is no menu editor. You can instead create a text file in ~/.local/share/applications named wow.desktop, and paste this: 

[Desktop Entry]
Name=World of Warcraft
Exec=wine LAUNCHER
Icon=Wow-icon-scalable.svg
Terminal=false
Type=Application
Categories=Application;Game;
StartupNotify=false

Remember that you should also edit the Exec= line to reflect your WoW installation path, if you've installed to a special location.

Troubleshooting

See Wine troubleshooting.

Miscellaneous

References

 
  1. ^ http://www.learninglinux.com/postp734.html#734

External links

External link WineHQ.org Official website
External link AppDB.WineHQ.org The WineHQ Application Database
External link Wiki.WineHQ.org Wine Wiki: Winetricks
Community content is available under CC BY-SA 3.0 unless otherwise noted.
More Fandoms