Quote:
|
Originally Posted by gaitano
..... ran the script to make sure my mainhud was up to date and it still will not show up.
Gaitano
|
Hey pal,
Yeah, let us know what exactly you did and we can try to help.
In short:
1] Make a folder called 'custom'; or whatever you want for your custom ui under your \EverQuest II\UI\ folder (probably going to be C:\Program Files\EverQuest II\UI\custom)
2] Place the eq2ui_mainhud_ammo.xml that you downloaded into the new 'custom' folder; or whatever you called it. It just needs to be in a folder under the 'EverQuest II\UI' folder.
3] Copy the eq2ui_mainhud.xml file from your '\EverQuest II\UI\Default' to your '\EverQuest II\UI\custom' (or whatever) folder.
Now, we have to edit the eq2ui_mainhud.xml file that we placed under our 'custom' folder. Don't edit the one under the 'Default' UI folder, just the one under the 'custom'.
Goto the end of that file and tack on '<include>eq2ui_mainhud_ammo.xml</include>'
example...
<include>eq2ui_mainhud_startbutton.xml</include>
<include>eq2ui_mainhud_letterboxframe.xml</include>
<include>eq2ui_mainhud_ammo.xml</include>
</Page>
Notice the '</Page>' is at the very end of the file still. Don't place your '<include>eq2ui_mainhud_ammo.xml</include>' after the '</Page>'!
Then fire up the game and once inside type '/show_window MainHUD.Inventory' with no quotes ''; but with the exact capital letters.
A ammo window should show up!
Now, just released is new
UI mod to autoload the ammo window so you don't have to type/macro that show_window command.
Also, I made a
script that assists in copying the eq2ui_mainhud from your Default to custom folder; since that's really boring to do by hand. If you use the script, you will need to edit it with notepad to make sure a few settings at the top of the file are correct; else it probably won't work!
Just recently, SOE made it so the mainhud has that </Page> line at the bottom of the file; the old script wasn't coded for this; so it was placing the <include> line AFTER the </Page>; which causes it to not work. There is a very good chance that if you did ALL of the above steps and used the old script, then that is the only problem. Download the updated version and try again
