Small visual bug
Wolfgars text is overwriting
Started by Neon, Mar 13 2014 14:40
5 replies to this topic
#1
Neon
-
- Members
-
- 2,000 posts
Veteran
ELDEVIN
Neon
Level 40
- United Kingdom
#2
Crusader
-
- Members
-
- 321 posts
Member
ELDEVIN
Crusader
Level 45
- United Kingdom
Posted 13 March 2014 - 15:43
I've noticed that on a few of the new quests. Also, some of the new quests aren't appearing on the quest log, so when you track a different quest you can't track them:/
Characters:
Crusader - Assassin [Level 45] | Dusk - Mage [Level 1] | Hex - Ranger [Level 6]
Gathering Professions:
Crystal Cutting: 13 | Farming: 10 | Fishing: 10 | Foraging: 41 | Forestry: 19 | Prospecting: 40 | Skinning: 11
Crafting Professions:
Alchemy: 45 | Armoursmithing: 9 | Cooking: 11 | Jewelry: 6 | Leatherworking: 6 | Tailoring: 5 | Weaponsmithing: 2
#3
Anakiro
-
- Members
-
- 1,542 posts
Veteran
ELDEVIN
Anakiro
Level 23
Posted 13 March 2014 - 15:53
Also, some of the new quests aren't appearing on the quest log, so when you track a different quest you can't track them:/
That sounds a little off. Any chance you remember the quest names? Or maybe the book or where you were when you picked it up? If I've got an example I can go look into it. 
#4
Susej
-
- Members
-
- 1,092 posts
Veteran
ELDEVIN
Susej
Level 45
#5
Neon
-
- Members
-
- 2,000 posts
Veteran
ELDEVIN
Neon
Level 40
- United Kingdom
Posted 13 March 2014 - 23:15
Oh yeah I literally just did the nidaros mine quest series and noticed on one of the quests towards the end that it clipped, however I forgot to screenshot. :/
#6
Cygnus
-
- Hunted Cow Staff
-
- 162 posts
Game Programmer
ELDEVIN
Cygnus
Level 35
Posted 11 April 2014 - 11:21
The worst case that broke the positioning of the text altogether should have been fixed in an earlier patch.
For the case of Wolfgar's "The Tower of Noctis" quest the full xp text width wasn't being taken into account when positioning the money/gold text causing overwriting. This probably would have happened with other quests with larger xp values also.
This fix will probably be in our next update.
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users