Change log

Version 1.71, 7/19/2008

• 
  
• Updated all UI files to current official version (7/18/2008)
  

Version 1.7, 7/17/2008

• 
  
• Updated all UI files to current official version (7/17/2008)
  
• Numerous tweaks, updates and fixes to implement the recent official changes to the user interface into the Mirage UI.
  

Version 1.62, 7/03/2008

• 
  
• Corrected another error specific to the default 3-Bar-Normal sized player and target frames that prevented the new health, stamina and mana bar graphics from displaying.
  

Version 1.61, 7/03/2008

• 
  
• Corrected an error on the player and target frames that prevented the new health, stamina and mana bar graphics from displaying.
  

Version 1.6, 7/02/2008

• 
  
• Updated all UI files to version 50752 (7/02/2008)
  
• Group and Pet panels redesigned with new and smaller more compact versions of the health bars (they are still larger than the default game health bars)
  
• Necromancer pet panel control point display raised from a cap of 8 to 11 to include the 3 points obtainable through feats. (thanks to Brian from ledmirage.net)
  
• Text color changes: All public global chat is now a light brown color, all tells and whispers are pink, all system messages and XP gain are yellow, on-screen messages remain a darker blue, all general grey colors brightened up a bit to make them easier to read.
  
• Font and color changes to the quest journal, description, names and objectives to make them easier to read.
  
• Numerous small tweaks all around.
  
• Fixed all reported problems with some variations not centered when the XP Bar is hidden.
  
• Moved all custom Mirage UI TGA files into the ..\Default\gfx\MirageUI\ folder to make life easier for those of you tweaking them.
  

Known caveats

If you have any problems not listed below it is highly recommended that do a clean installation of the Mirage UI as indicated in the Installation section, if this does not resolve your issue or if you have more specific questions on how to further customize the Mirage UI package please let us know in the forums at http://ledmirage.net/

• 
  
• If you don't see health, stamina and mana bars and are missing the all of the images for the buttosn (invisible button backgrounds) then most likely you didn't extract all the graphics from the zip file into the correct location - All TGA files go in the ..\cd_image\Gui\Default\gfx\MirageUI\ folder path. Don't worry about them overwriting any base game files as they go in their own custom "MirageUI" folder.
• There are no extra buttons (Q, V & E) on all the variations except the 4-Bar version, this is by design since you can map hotkeys for any of the 34 additional buttons - including Q V and E, and when you hit level 40 the two extra attacks are on your abilities panel where you can drag them to any button you wish (with the keybindings of your choice).
• The player and target frames display both positive and negative effects, this is by design to circumvent a current game bug that tags many of the player stances as negative effects (debuffs). As of yet I have not been able to create a new separate buff frame to split negative and positive but I am still looking for a better solution. If you *REALLY* need to filter out positive or negative effects there are plenty of posts explaining how to do it on my forums at http://ledmirage.net
• Duplicate shortcut overlays (keybindings text) for ability icons on the floating shortcut bars and the new mirage ui bars are a known glitch that does not cause any problems. You can use all the buttons on the additional floating bars with the only limitation being that there are no keybindings for them (as they are used to bind the new custom Mirage UI shortcut bars)
• The "LEAVE" button from the guild panel was removed by design, if you need to leave your guild use the text command "/guild leave".
• As of the July 17th patch Funcom made the text display of hotkey shortcuts use a longer format (instead of "C" not it's "CTRL" and instead of "S" it's "SHIFT") which prevents the user from seeing the complete keybinding text on the buttons, this is an issue that only funcom can resolve as we do not have access to modifty that part of the user interface.