![]() |
|
#11
|
|||
|
Oh, also note that this is just a fix for the "disappearing hot button bars" problem, and not for converting the 2x5 hotbutton bar to a 1x10 - there's other threads addressing that issue.
__________________
The Thread Necro has spoken.
| ||
|
|
|||
|
#12
|
|||
|
Good to know. It seems in the other thread on copying over the files fixed also my missing hotbar issue (as well as the 1X10 change to a 2X5). I thought at first I was just me not remembering what my key binding was for it. Then I checked, and still wasn't working. I never did go through the actions, but I am assuming it would not have worked either.
__________________
Etara - 60 Shaman
Ateria - 55 Druid Alarya - 35 Cleric Man destroys God. Man creates dinosaurs. Dinosaurs eat man. Woman inherits the earth. | ||
|
|
|||
|
#13
|
|||
|
If you want to preserve the formatting of XML etc, post it inside CODE tags - like this but without the spaces inside the square brackets:
Code:
[ code ] <?xml version = "1.0"?> <XML ID = "EQInterfaceDefinitionLanguage"> <Schema xmlns = "EverQuestData" xmlns:dt = "EverQuestDataTypes"/> [ /code ] | ||
|
|
|||
|
#14
|
|||
|
Also, if you want to install a custom UI, it's best to put it inside its own folder.
Inside your EQ directory there's a folder called uifiles. Inside there there's default. Create a new folder for your UI alongside default. Put your new UI files into that folder. Then, from inside the game, load your UI using the options window or the command /loadui my_ui_folder_name (I think that's the right command, I always use the window). When EQ loads a UI, if any file it needs isn't found, it then looks in the default folder. So, you could create a folder my_ui, and just put the EQUI_HotButtonWnd.xml file in there. When you load it, your hot button window will be custom, and the rest of the UI will be the default one. This means that when the files inside default change in a patch, it won't overwrite your custom UI. | ||
|
|
|||
![]() |
|
|