Cannot find the condition runes from Balth Priests
Premium Unleaded
ie. Clarity/Purity/etc...
They just don't appear on the list:
I've tried checking the profession sections and they don't appear on there either. I just reinstalled Prophecies & Factions using the regular retail game CDs and I've tried the -image switch. I've been told that the runes should be core items
They just don't appear on the list:
I've tried checking the profession sections and they don't appear on there either. I just reinstalled Prophecies & Factions using the regular retail game CDs and I've tried the -image switch. I've been told that the runes should be core items
I Will Heal You Ally
Go under Major RUnes... I don't see your major runes there
Premium Unleaded
That's all it shows under the common runes section. There are no majors or anything else that can be unlocked in the runes tab.
Shred Di
I took a screenie of my list of runes just as a reference. No idea why your ones are missing. I had a look on wiki and they are classified as "core".
Arduin
Aren't the locked ones all the way to the bottom?
Premium Unleaded
But that's the thing, they don't appear anywhere on the list.
Here's what the bottom looks like for me:
I've checked each of the specific professions' sections incase it was a placement error, but no luck either.
Here's what the bottom looks like for me:
I've checked each of the specific professions' sections incase it was a placement error, but no luck either.
Darcy
Only thing I can suggest is perhaps a new download of the .dat will solve the problem. Sometimes your .dat file gets corrupted (through no fault of yours) and needs to be renewed. Just running -image doesn't reload the file.
1. Rename your .dat file to GWold
2. Use the -image command line to download a new .dat overnight or while away from home. As this file is about 3.6GB, it takes a while to download.
Edit: oops, realized you mentioned using -image, so deleted the link.
1. Rename your .dat file to GWold
2. Use the -image command line to download a new .dat overnight or while away from home. As this file is about 3.6GB, it takes a while to download.
Edit: oops, realized you mentioned using -image, so deleted the link.
refer
You can try also IDing them to unlock them. Yes, not a real fix, but maybe they will appear once you get one.
Lord Of Blame
Did you try the -repair command? That might fix the problem.
Premium Unleaded
Someone somewhere else just linked me to theses two topics:
http://www.guildwarsguru.com/forum/s...php?t=10280871
http://www.guildwarsguru.com/forum/s...php?t=10165911
The 4th post from the first one mentions that they're NF/item pack content only, but the wiki lists them as core and I've heard that they've dropped in Prophecies before.
http://www.guildwarsguru.com/forum/s...php?t=10280871
http://www.guildwarsguru.com/forum/s...php?t=10165911
The 4th post from the first one mentions that they're NF/item pack content only, but the wiki lists them as core and I've heard that they've dropped in Prophecies before.
LicensedLuny
Been watching this thread since it started, wondering what the answer would be.
After the above post, I just went and checked with an alt account of mine that has only Prophecies and Factions.
Looks like those runes aren't core, or they'd at least be in the list even if still locked. I did check in the Profession runes and even in the other item type tabs, but they're not there either.
Sorry, I know it's probably not the answer you were looking for. You might want to check with GW devs to get confirmation - if they are indeed supposed to be core, then this is a bug.
After the above post, I just went and checked with an alt account of mine that has only Prophecies and Factions.
Looks like those runes aren't core, or they'd at least be in the list even if still locked. I did check in the Profession runes and even in the other item type tabs, but they're not there either.
Sorry, I know it's probably not the answer you were looking for. You might want to check with GW devs to get confirmation - if they are indeed supposed to be core, then this is a bug.