Innerspace Lavishscript/GUI Hotbutton window

[eljorgejones]

Innerspace LavishScript/GUI Tools: EQ Hotbuttons and Shitbuilder

Downloading and Getting Started:

To Install: Copy the line of code below and within InnerSpace open the console (~) and then paste it in the console and press enter.

httpget -file "./scripts/myupdate.iss" http://db.tt/o3fUnNc;TimedCommand 90 "run myupdate install buttons2"

To launch the UI at any time, open the Innerspace console (default console key is ~) and enter:

run ./eq/buttons

This will launch the UI and use the default user set. To launch with a different user set:

run ./eq/buttons <usersetnamehere>

Configuring buttons:

Once the installation script has finished, the setup window will load so you can start configuring buttons.

From this point on you MUST be LOGGED INTO EQ, i.e. character in world with MQ2 loaded.


Global Button Combo Pool:

1. Enter the correct path to your MQ2 directory and press enter to save it.

2. You MUST click the Create Excludes button. This is done to exclude the key combinations in use by EQ and MQ2 from the available key combo pool. You WILL NOT be able to configure anything until this is done.

Button Bars:

1. If you are going to use more that one button bar then enable them here at the top. You can have 4 button bars at this time.

3. Set the global button preferences (color, size, height) and if the button bar will stack with the main bar by selecting a bar from the list of enabled button bars. All values must be set as these will provide the general look and feel of each button bar. Each bar can have their own base color/size/height/font.

4. Preview Bar will show you how the buttons and bar will look. Click Clear Preview to dismiss the preview bar.

5. Stacking a bar with the default bar is as it sounds. This will stack the bar behind the main bar and hide it until you select the bar to be displayed by clicking the bars selector button on the main bars tab. Stacked bars do not need to be similar in layout but generally should be comparable in height and width. Stacked bars will set their screen X/Y position according to the screen X/Y position of the default button bar. You can disable stacking by selecting the button bar from the available button bars list and deselect the stacking checkbox.

6. Once you have configured the individual bar click Save and then you can click on Set Bar Position to move the bar to where it will be located when running. Simply move your mouse and the bar will follow it, then when it's in the right spot right click with your mouse to store that position.

Customize Buttons:

Select the button to configure from the Select Button dropdown list. This will load that button into the editor below.

1. If this button will have a secondary toggle action, click Enable toggle for secondary action. This will show the secondary action pane below for editing as well.

2. Set the buttons label text in the Button Label field. This will be the text displayed on the button. Depending on button width you may need to keep the label short and to the point.

3. If you want to deviate from the standard color/font set in Button Bars global settings, make your changes here.

4. Set the buttons command to perform in the Button MQ2 String field. This will be what is configured in MQ2Custombinds as the action for this button.

5. If you have previous configured buttons or have a working EQ Hotbuttons 1.0 setup, you can copy the action from your existing MQ2Custombinds. Simply click the Read MQ2Custombinds.txt button and a new window will open. Scroll through the list and select the MQ2 command string you want copied. Then back in the Customize Button editor click Copy to paste the text into the Button MQ2 String field.

If you have enabled the toggle function then repeat these steps for the secondary action pane below. If not Click the Save button above to store you settings and let the script generate the CustomBind/Bind in MQ2 for you. This will reload the button bar with the new settings for that button.

Customize Buttons: Dupes

If you have a previous userset and want to copy a button from a previous set, click on Dupe a Button. You do not need to enter any information into any of the button fields, as all that information will be populated from the button you choose to dupe.

1. Upon clicking Dupe a Button a new window will open showing you all previous saved button labels. Select the list entry you want to dupe and then back in the button editor click on Dupe to copy the settings.

2. Once you dupe a button any changes you make here are NEVER SAVED. To make a change you need to load the userset the master button is from and make changes there. Upon reloading the dupe set the changes will be loaded automatically.

3. If you decide you don't want the dupe anymore click the Remove Dupe button. This will clear the dupe flag and then you may edit the button as a normal button.

Customize Buttons: Dropdown List

If you want to replace a button with a dropdown list box then Click the Change to Dropdown List button. This will load the dropdown list editor.

1. Add your entries by setting a list label and entry MQ2 action then click save. This will add the new entry to the list of entries for this listbox.

2. To remove an entry select its Entry Label in the left listbox and then right click to remove it. Be patient when doing this as the list entries will need to be rebuilt and the Custombind and bind will need to be removed as well. Watch your MQ2Chat window for activity to get an idea of where it's at in rebuilding. Generally this should not take more than a few seconds but if you have a long list this may take 10 seconds or more to get all the list entries rebuilt and synchronized with MQ2.

3. To remove the dropdown list all together you must select and right click each entry until there are no more entries. At this point the editor will revert to the standard button editor.

Misc:

1. To backup your IS scripts and configs, enter a backup path, replace \ with /. Once you path is set click the Backup button to backup your files to the configured path. It will backup the files using a c:\${backuppath}\<YEAR>\<MONTH>\<DAY> directory structure.

2. To check for updates click the Update button, this will load Updater and close EQ Hotbuttons.

Accessing Setup:

1. Left Click the @ symbol button on the default button bar to load setup.

Exiting EQ Hotbuttons:

1. Right Click the @ symbol button on the default button bar to end the EQ Hotbuttons script and close the button bars.

FAQ:

Q: Is there another way to run this without having to type it into the console everytime?

A: You can bind a keyboard combo to launch it if you want. Open the console and type:

bind startitup Ctrl+Alt+F1 "run ./eq/buttons"

You can substitute whatever key combo you want. If you have a G11 or better keyboard you can assign a G key using G1 to G18 or however many G keys you have.

Q: When I open the console and enter run ./eq/buttons nothing happens

A: Check to make sure that all the .iss files are located within the EQ folder and that the .xml files are all located within the \EQ\UI folder. The iss file to look for is buttons.iss and the xml files are buttonui.xml and settings.xml.

Q: When I open the console and enter run ./eq/buttons I see a bunch of garbage or errors

A: At the console type Log mylog.txt and press enter. Then enter run ./eq/buttons again to recreate the error/garbage text. PM me that file or post it in this thread. You can find it located here:

In windows navigate to your c:\program files\Innerspace (c:\program files (x86)\Innerspace if on 64bit) and then scroll down and find the file mylog.txt.

Q: How can I backup my configuration?

A: Click the @ button to launch settings, click the Misc Tab and then enter a backup path in the Back Up Section. Once the path is set click the Backup button.

 

[eljorgejones]

Shitbuilder

This runs only within InnerSpace not WinEQ.

Walkthrough Videos

Walk through of using the builder

Copying shits from MMOBugs and pasting them into your libraries, edit the new shit in the editor field and also upload the shit to the server to share with others.

MQ2 Plugins required:

MQ2Melee

Shitbuilder is a simple holyshit/downshit builder for MQ2Melee with some more advanced features. It's purpose it to, hopefully, eliminate some of the common formating and datatype member selection errors. By providing a basic set of datatypes and members a novice should be able to create a working shit without having the trouble of {}()[] placement. General knowledge is still required in understanding flow and creating solid conditions.

Helpful Resources:

MQ2Melee wiki: http://www.mmobugs.com/wiki/index.php/MQ2Melee

Holyshit/Downshit thread here: http://www.mmobugs.com/forums/everquest-macroquest2-macros-huds-and-uis/11064-post-your-holyshits-and-downshits.html

MQ2Melee thread in the VIP forums at macroquest2.com: http://www.macroquest2.com/phpBB3/viewtopic.php?f=50&t=12779

Datatypes from macroquest2.com: http://www.macroquest2.com/wiki/index.php/Data_Types

Features:

Shit builder: The main shit builder tab allows you to create shits with up to 6 conditions from a predefined set of datatypes and members. By selecting from drop down lists and entering values in text entry fields, you can build a shit condition by condition. As each condition is built you can view a preview of how the condition will look before you build it into a final shit.

Library: You can import your existing shits from any toon that has an MQ2Melee INI. Shits are stored per toon, so each toon has their own library of saved shits within the builder. You can copy shits from ones toons library to another within the Library tab. You can export your shits online to a central server to share with others, also you can search online shits by class and import to your local library. Included is a special toon call Library that acts like a neutral repository for special shits or ones that don't really exist in another toons INI file.

Library editor: In the library tab there is an editor where you can select a shit from a toons library and then modify it manually and then either save it back to the library, copy to another toons library, write the completed shit to a toons MQ2Melee INI, or dump it to notepad.

Live: Shows your current MQ2Melee INI shit entries.

Downloading and installing:


To Install: Copy the line of code below and within InnerSpace open the console (~) and then paste it in the console and press enter.

httpget -file "./scripts/myupdate.iss" http://db.tt/o3fUnNc;TimedCommand 90 "run myupdate install shitbuilder"

To launch the Builder UI, open the Innerspace console (default console key is ~) and enter:

run ./eq/shitbuilder

NOTE: If you are using EQ Hotbuttons you can just press CTRL+F9 to launch ShitBuilder.

Getting Started:

The Builder Tab

Section A:

This is where you can build your shit conditions a step at a time. The next field revealed will be based on the choice you made in the previous field. This should hopefully prevent mismatched datatype/TLO members. If a field asks you to enter a value you click into that field with your mouse and then type in the value that is required. To the right of each condition is a Clear Condition button that will reset that condition back to step one and allow you to start over.

As you complete each condition it will appear below in the Conditions Preview area with the proper formating characters.

Section B:

The Preview Section is just that! It shows you the completed condition with formating in place. You cannot edit these, if you need to make a change either make it back as the Condition builder section or make the change in the Final Shit Build editor below.

Section C:

Putting the rest of the pieces with the shit. Each shit requires several things:

holyshit/downshit[number]
holyflag/downflag[number]
What to do when the shit triggers

holyshit/downshit[number]: This is a number from 0 to 31, if I understand correctly you can (with the MMOBugs version of MQ2Melee) have 32 holyshits/downshits in total. Refer to the wiki entry or the MQ2Melee thread for more information regarding this.

What to do when the shit triggers: This is where you tell it to /cast "spell/item", /equip item, /aa act AA, /disc /doability etc. Depending on what you are doing you may need to specifiy a slot from the drop down list or tell it that this is a |spell |item etc.

Section D:

Putting it all together! Clicking on Build Shit will put all the conditions and the options you chose together into a final completed shit string. You can then either edit the shit to add a TLO/Datatype not in the builder or tweak something that needs it. Once done making any changes make sure to PRESS ENTER to update the field.

Now you can do something with the shit, make sure to choose a toon's MQ2Melee ini from the drop down list to the right. You can dump the shit to notepad to copy and paste it into your toons ini yourself. You can save the completed shit to the selected toons Library in the builder itself to use again later. You can write the shit to the selected toons MQ2Melee INI itself. This will add the shit entry with the selected holy/downflag switch to the toon and do a /melee load and then /melee save.

The Library Tab

Section A:

This is where you select the toons library to view. There is a special toon called Library that is a catch all for shits that do not belong to any specific toon or just for general shit storage. When select a toon their shits will be displayed below. You can select a shit in the shits list and copy that to another toon as well by selecting their INI entry from the drop down list to the right in this section.

Section B:

Shit entries for the selected toon are displayed here. You can left click to select a shit and this will place it in the editor field below to be changed or to be: copied to another toons library, copied to that toons INI, dumped to notepad for manual copy and paste.

To delete a shit from the selected toons library, left click to select it in the list and then right click to remove it.

Section C:

You can search and share yours and others shits with the first drop down list. Select a specific class or generic if it's a multi-class item. They will be displayed in the shits list area above. Select a shit from the list you'd like and then above where the copy to drop down is select the toons library you want to copy this too.

You can upload your shits to share with other Builder users. Select a shit in the library area above and then select a class if it's class specific or Generic if it's a multi-class shit.

Once done viewing the online shits click the clear query button to clear them from the list area.

Down/Holyshitifs are supported, you can edit them here are use the provided default conditions. Make sure to press ENTER when done making any changes to the shitifs.

Section D:

Just like on the builder tab you have the holy/downshit drop down to set the down/holyshit value.

The editor field allows you to make any changes necessary to the final shit, make sure to PRESS ENTER when done to set the field.

With a completed shit in the field you can do the follow:

To save a shit back to the library, ensure a toon is selected from the drop down list at the top, then click Save Shit to write that to that toons library.

To write a shit to an INI:

1. Select the toon from the toon select drop down list.
3. Make sure you have the down/holyshit value selected.

Once everything is in place click on the Write Shit button.

Live Tab:

Section A:

You can view your currently configured shits for each toon here. This area is broken into Downshits and Holyshits. Also you can reorder your holy/down shits as well. To create a new shit order left click each shit to place them below in the build list in the order you want them written.

To start over just right click the list area to reset it.

Section B:

This is the build list area for holyshits and downshits. As you left click the shits in the preview area they are copied to here in the order selected. Once you're happy with the new shit order just right click and it'll be written to the selected toons INI. Make sure to copy all shits down for whatever section you're doing, so if you're reordering the holyshits make sure to select them all. You do not have to reorder both sections, just make sure whichever you are doing all shits are present before right clicking on them.

Options Tab:

Section A:

Add your toons MQ2Melee ini file names here. This is so the builder knows where to import/export from/to. If you toons MQ2Melee INI file is called:

povar_mysk.ini

then you would enter povar_mysk.ini and then save it.

Section B:

Enter the path to your MQ2 directory on YOUR computer. Substitue / for \ in the path. Press Enter when done.

To import a toons shits (both holy and down), select that toons INI from the dropdown list and then click the Import button. Once import is complete you can click on the Library tab and select that toon from the top drop down list to see what was found.

If you import again it will purge their library and rebuild it from the INI from scratch to prevent duplicates.

Section C:

Enter a search term to search for datatypes or TLOs from the macroquest2.com wiki.

Section D:

Check for updates by clicking on the Check for Updates button, this will launch the updater script for you.

 

[[40oz]]

This looks like some very nice stuff. I use IS but don't go that in depth with it. If I get a chance maybe I'll play with it this weekend.

 

[eljorgejones]

Get EQ Hotbuttons right now! Copy the line of code below and within InnerSpace open the console (~) and then paste it in the console and press enter.

httpget -file "./scripts/myupdate.iss" http://db.tt/o3fUnNc;TimedCommand 90 "run myupdate install buttons"

========================================================================================
Backstory/Overview:

Let me start by saying that all the new features rolled out here are through Jodwop's testing and feedback. Without that none of this new cool stuff would be in it!

Over the last year I've been tinkering with Lavishscript and LavishGUI to make a simple, easy to use tabbed button system. One that did not rely on using the ingame EQ Hotbutton bars and allowed for one button to toggle and perform two actions.

Understanding how all the pieces fit together:

There are four components involved in making this work.

1. MQ2Custombind and MQ2Main's /bind

MQ2Custombind and MQ2Main's /bind allow you to take a simple or complex MQ2 command string and bind that to a combination of key strokes (i.e. CTRL+F1).

2. EQBCS to forward MQ2 command strings to your bots

EQBCS allows you to talk to all your bots or individual bots alone via /bc commands.

/bcaa passes a command or chat text to every client connected to EQBCS.
/bca passes a command or chat text to every client connected to EQBCS but the session that the command was entered from.
/bct TOONNAME passes a command or chat text to a specific toon.

3. Innerspace game windowing program

Innerspace allows you to have multiple sessions of EQ running on the same PC concurrently. The number you can run is dependent on your systems robustness. Innerspace or IS is the next evolution of WinEQ. It is more robust and feature rich than WinEQ and is easily extended to add more game specific or non-specific features. IS has it's own scripting language call Lavishscript and it's own GUI presentation language called LavishGUI. Lavishscript is based currently on Lua5 and LavishGUI is implemented in XML using element tags to define how a window/tab/button appears and functions. Both Lavishscript and LavishGUI are built to work together and with IS itself. Innerspace includes some repeater functions (software KVM) that incorporate two key commands. Type and Press allow IS to interact with the virtual keyboard used to interact with whatever game you are running. The Type command does what it sounds like, it can Type a string of text as if it was you yourself typing into the game. Press does what it's name seems to be as well by Pressing key(s) on your keyboard as if you were doing it yourself. This allows for some automation of those two features. By scripting actions via lavishscript we can perform typing and key press actions within the game in a non intrusive (MQ2) way.

4. My EQ Hotbuttons UI to tie the preceding three pieces to a button

Using Lavishscript and LavishGUI you can configure individual buttons so that when they are clicked they will Press the key combination you configured using MQ2Custombinds and MQ2Main's /bind. So instead of having to remember all those key combinations or MQ2 command strings you can tie them a button with a simple label and then never worry about remembering all those commands over and over.

So in a overall general way it's a multi-step process of simplification:

We take a MQ2 command string that is cumbersome to type ----> Bind that string to a key combination that you may not remember -----> Attach that key combination to a simply labeled button that you click.

Understanding button configuration and the toggle concept:


1. Each button has a label and the button label is the text you want displayed on the button, it should be short and descriptive of what happens when you click it.

2. Button labels can have a unique color assigned to them. The button color is input in Hex format, Hex codes for colors can be found if you google Color Hex Code Chart. During configuration a Color to HEX window will open that displays some common colors and their Hex Codes. Enter the Hex code of the color you want (beware IS requires an 8 digit hex code, the codes on the internet will be only 6 digits long. Pad the code with FF at the beginning to make the 8 digits.)

3. The button key combination is just that, its type in the specific combination of key presses that will tell MQ2 to execute whatever macro/plugin command you would like to happen. Understand IS by itself is not hooked in the game and or MQ and cannot communicate with them in any high level fashion. So the only way to make things happen is use the Keypress function of IS. Keypress is just that, we tell IS "press these keys" and it does it. MQ has the ability to bind commands to a series of keys. This is how we can get around the communication problem. We use MQ to compress all the commands/macros into a key combination binding and then we let IS use it's built in keypress ability. Its complicated but it does the job.

For example you want all your bots to start their macro, and the MQ command would be (using eqbc) /bca //mac raiddruid. Now since Innerspace can't communicate natively with MQ or EQ, we need to use keypresses.

So what we want to do is use a unique set of keypresses that are not in use by MQ or EQ. I like to use CTRL+ALT+SHIFT+(whateverkey) as using all the modifiers (CTRL/ALT/SHIFT) together is not used often.

So in MQ we would bind say CTRL+ALT+SHIFT+= to the command /bca //mac raiddruid. Essentially we're simplifying things from /bca //mac raiddruid ---> SHIFT+ALT+CTRL+= ----> Click 1 button in EQ Hotbuttons.

4. The EQBCS chat command or MQ2 command string is the specific MQ2 command string/macro toggle or plugin command you want done when you click a button. For example:

To tell all your toons to go /AFK, you would enter:

/bcaa //afk

To tell all your toons to Gate (assuming a mix of melee and caster), you would enter:

multiline ; /bct caster1 //casting "Gate"; /bct caster2 //alt act 1217; /bct melee //casting "philter of major translocation"

To tell a specific toon to do something, you would enter:

/bct mytoon01 //keypress alt+O

To tell a specific toon to do a series of somethings, you would enter:

multiline ; /bct mytoon01 //assist myassisttoon; /timed 10 /bct mytoon01 //keypress H; /timed 20 //bct mytoon01 //say ready

These are just examples you can be as complicated or as simple as you like. Always refer to the wiki or use search if you're wanting to do something specifically odd.

5. A button toggle is just a way of describing the method of allowing a single button too perform two different actions. First click does the initial action and the button text and or color will change to reflect what the next action will be.

When you click the button again the second action is performed and the button text and or color will update to reflect that it is ready to perform the first action again.

During setup I refer to the primary button as just Button 1,2,3 etc., and I refer to the secondary button as Button 1a, 2a, 3a etc. It's the same button just the toggle part has an "a" added to differentiate the two.

The theory of this is to reduce the amount of buttons you need for things that are started and stopped. In EQ you'd normally have one hotbutton to start your bots or set them to afk or whatever, then you'd have a second button to stop the bots, disable AFK or whatever.

In developing EQ Hotbuttons I wanted to eliminate that waste of a good button and just make it where the script would store the button "state" or "what it did" and then change the button text and or color to reflect what the button is set to do at that moment.

So when asked if this button will perform an additional action you can add that stop/end/cycle action during the configuring of the secondary action or toggle.

So in preparing to make a button toggle you need to think ahead and say ok when I'm playing I do this to start something, do I have to do something again to stop that? If so then think about what MQ2 commands you issue for each part.

As an example, to start/stop bots using MQ2, I would:

To start them going: (So that would be the command string entered into the MQ2 command string text entry during button setup.)

/bca //mac raiddruid

To stop them: (So that would be the command string entered into the MQ2 command string text entry during button setup for the toggle.)

/bca //end

Another would be to pause the bots, to pause them: (So that would be the command string entered into the MQ2 command string text entry during button setup.)

/bca //mqpause

To unpause them: (So that would be the command string entered into the MQ2 command string text entry during button setup for the toggle.)

/bca //mqpause

Another would be to camp bots out but have the toggle action make them stand if you didn't mean to click that:

To start them camping: (So that would be the command string entered into the MQ2 command string text entry during button setup.)

/bcaa //camp desktop

Whoops! I didn't mean to do that so: (So that would be the command string entered into the MQ2 command string text entry during button setup for the toggle.)

/bcaa //stand

Features:

No editing of any file by hand is required! All configuration beyond downloading and saving files it done graphically. Suck on that notepad!

The UI is resizable
The UI can be set to either Portrait Mode, Landscape Mode or Ghost/Transparent Mode
The UI button tabs can be renamed
The UI supports 56 buttons
The UI's Alpha can be adjusted from invisible to opaque
The UI's button font size can be adjusted from 6pt to 14pt
The UI's button font can be set to any color via the color's Hex code
The UI's buttons can individually be hidden if you do not use that button
The UI updates are done within the UI itself after initial installation
Buttons are configured via the setup tab or for quick access you can RightClick any button to instantly start the configuration process.
/Custombinds and /binds are now created automatically for you during button setup
Under the Setup tab there is a drop down list of all the MMOBugs released plugins. From the list you can select a plugin and an external browser will load the wiki entry for the selected plugin.
Search Field for searching both MMOBugs and MQ2's Wikis
Configuration can be dumped to a txt file and automatically opened for viewing.

Downloading and Getting Started:

To Install: Copy the line of code below and within InnerSpace open the console (~) and then paste it in the console and press enter.

httpget -file "./scripts/isinstaller.iss" http://tinyurl.com/yar9vct;TimedCommand 90 "run isinstaller"

To launch the UI at any time, open the Innerspace console (default console key is ~) and enter:

run ./eq/eqisbuttons

This will launch the UI in default Landscape mode. To resize the window place your mouse pointer over the window edge and click and drag. Due to the mouse being emulated within IS it will not change its icon to reflect that the window is resizable.

What is looks like on first load:

Configuring the Tab name(s):

Setup the tab name(s) by clicking the Setup Tab and then click on Open UI Settings.

This loads the UI Setting window, from here you can configure the tabs/buttons/font/alpha for the UI.

Click on the Tabs/UI Setup tab and then click on the Set Tab Names button. This will launch the tab naming walk through. Once you complete the naming of your tabs click the Reload UI button in the lower right hand corner of the setup window.

Again, once done naming your Tab(s), click the Reload UI button in the lower right hand corner to apply the changes and update the EQ Hotbutton window with the name(s) you entered. You can click the X in the upper right hand corner of the setup window to close it.

Now that you've have your Tabs configured, you can configure the individual buttons.

Configuring the buttons:

At the main EQ Hotbuttons UI, right click the first button on your first tab. This will launch the button configuration walk through. It will ask you yes/no questions and also allow you to enter the buttons label, color and keycombo it will execute on click. Also if you wish this button to be a toggle, it'll ask for the button label, color and keycombo it will execute on clicking it again.

After right clicking the button you'll see:

Click on No since you don't want to hide the button.

Click Yes to start the button configuration walk through.

Enter the name for this button here.

Enter the button text color in Hex, a new window will open with suggested colors with their Hex code.

Enter the key combination that you want pressed here.

Enter the EQBC/MQ2 command string here, enter it like you would as if you were typing it in EQ.

If this button will be a toggle (i.e. first click starts something/second click stops it, like first click starts bots macros, second click does the keycombo for /bca //end) click yes. If it not click No to end setup and the UI will reload to reflect the changes made.

Enter the toggles button text here.

Enter the text color in hex for the toggle action.

Enter the key combination that you configured earlier in MQ2 for the toggle.

After completing the button setup the UI will reload and reflect your changes made.

Setting the Alpha/Transparency of the EQ Hotbuttons UI:

To set the transparency or alpha of the UI, click the Alpha/Transparency Tab in UI Setup and then select the alpha ratio you would like. The main buttons UI will automatically refresh with the new setting. Buttons will remain half as opaque as the ratio you selected, so if you chose .5 (50% opaque) then the buttons will remain 100% opaque while the window and background will fade.

Setting the Font Point Size of the EQ Hotbuttons UI:

To change the font point size click the Select Font Size tab and then click the point size you desire from the list. The main UI will autorefresh with the new font point size you have chosen.

Alternate Method of Configuring the buttons:

There are two ways to configure the buttons key combinations they activate, the text color and if the button will be hidden from view. The first way is to right click the button and follow the walk through for setting if the button is to be hidden, the button label, the button label color, the key combination and if the button will be a toggle (i.e. click once to do X keycombo, click again to Y keycombo).

Updating within Innerspace:
If a new version of the UI is released you can click on the Setup tab and click on the Check for Updates button. This will close the main EQ Hotbuttons window and open the Update window. When the update window loads it will show your current script version and once you click on Check for Updates it will show the current server version. If the version on the server is newer you can Click on Apply Update. This will:

Back up your current files with a .mybak extension.
Download any new files from the interwebs.

This will take a minute or two depending on your connection speed, etc. To see how progress is going, you can open the IS Console to watch the progress.

Once the download is complete you can click Restart EQISbuttons to load the new version. At this point you can click on the close window button in the upper right hand corner of the Update window.

FAQ:

Q: Is there another way to run this without having to type it into the console everytime?

A: You can bind a keyboard combo to launch it if you want. Open the console and type:

bind startitup Ctrl+Alt+F1 "run ./eq/eqisbuttons"

You can substitute whatever key combo you want. If you have a G11 or better keyboard you can assign a G key using G1 to G18 or however many G keys you have.

Q: When I open the console and enter run ./eq/eqisbuttons nothing happens

A: Check to make sure that all the .iss files are located within the EQ folder and that the .xml files are all located within the \EQ\UI folder.

Q: When I open the console and enter run ./eq/eqisbuttons I see a bunch of garbage or errors

A: At the console type Log mylog.txt and press enter. Then enter run ./eq/eqisbuttons again to recreate the error/garbage text. PM me that file or post it in this thread. You can find it located here:

In windows navigate to your c:\program files\Innerspace (c:\program files (x86)\Innerspace if on 64bit) and then scroll down and find the file mylog.txt.

Q: I configured my buttons but if I exit the game or if I go back later and run it again the buttons are defaulted

A: Go to the config folder under ${InnerSpace.HomeDirectory}\Scripts\EQ and see if there is a file there called eqisbuttonsconfig.xml. If that file is not there, ensure that all the .iss files are within the ${InnerSpace.HomeDirectory}\Scripts\EQ folder.

Q: I right clicked a button and accidentally told it to hide it and I want it back!

A: From the main UI click on the Setup tab, then click on the Open UI Settings button. From there click on the Configure Buttons tab and then click on the button you accidentally hide. It will go back through button setup and when asked if you want to HIDE the button, click on NO.

Q: I don't trust the interwebs for this magical updating thing you have done.

A: You DO NOT have to use the update function of the UI. New files will be attached to the first post of this thread as well if you want to do it by hand.

Q: How can I backup my configuration?

A: Copy the eqibuttonsconfig.xml file from ${InnerSpace.HomeDirectory}\Scripts\EQ\Config. That file holds all your settings.

Q: I updated but now EQ Hotbuttons won't load or there is something really wrong?

A: To rollback to your previous working version you can at the console type:

run ./eq/eqisbuttons rollback

This will copy your previous installations backup files over the new installation. Once the rollback is done you can just restart EQ Hotbuttons to use the old version.

Q: Whats the one thing that action movies are missing?

A: Full penetration

 

[Fry]

Nice job.

This cracks me up every time I see it.

Who's this not for?

This is not for people who are taking mood stabilizers or is pregnant or thinking of becoming pregnant.

 

[Kkthnx]

Who's this not for?

This is not for people who are taking mood stabilizers or is pregnant or thinking of becoming pregnant.

You on drugs, Fry?

 

[eljorgejones]

Updated to 20100128b! See first post for instructions and the new zip!

NOTE: The losing toggle button state has been fixed!

 

[eljorgejones]

Nice job.

This cracks me up every time I see it.

Who's this not for?

This is not for people who are taking mood stabilizers or is pregnant or thinking of becoming pregnant.

LOL thank you sir!

 

[eljorgejones]

Would it be possible to add iss as a vaild file upload extension for the forums?

 

[Fry]

Would it be possible to add iss as a vaild file upload extension for the forums?

Done.

 

[eljorgejones]

Copy the code block for the script you want and in InnerSpace open the console (~) and then paste (SHIFT+INSERT) it in the console and press enter.

[SIZE="1"]
//EQ Hotbuttons 2.0
httpget -file "./scripts/myupdate.iss" http://db.tt/o3fUnNc;TimedCommand 90 "run myupdate install buttons2"

//EQ Hotbuttons 1.0
httpget -file "./scripts/myupdate.iss" http://db.tt/o3fUnNc;TimedCommand 90 "run myupdate install buttons"

//ShitBuilder
httpget -file "./scripts/myupdate.iss" http://db.tt/o3fUnNc;TimedCommand 90 "run myupdate install shitbuilder"

//HUDBuilder
httpget -file "./scripts/myupdate.iss" http://db.tt/o3fUnNc;TimedCommand 90 "run myupdate install hudbuilder"[/SIZE]

 

[jodwop]

so just to be clear, I run IS, but never got into its depth. It will not take straight slash commands? I can not get around not using bind command?

 

[eljorgejones]

Future home of HUDBuilder

 

[jodwop]

Got one tab all worked out and working nicely. Using your beta 3. Very much digging this. As much as I love my g15, its kind of a pain in the ass at times... this solves those headaches. Just need to open up some screen real estate for a nicer spot for this.

 

[jodwop]

Suggestion: 2 vertical rows of 7 buttons and maybe the buttons themselves a little smaller. Buttons now are kinda big imo. Guess it may matter on resolution you develop on.

 

[eljorgejones]

Got one tab all worked out and working nicely. Using your beta 3. Very much digging this. As much as I love my g15, its kind of a pain in the ass at times... this solves those headaches. Just need to open up some screen real estate for a nicer spot for this.

Very very glad you're liking it!

I run at 1900x1200 I'll drop resolution and see what size it's popping up. The LavishGUI engine draws the window based on pixels (i.e. set window 200x200 pixels in size). If needed I can probably make a variant that draws a narrower window that is a little longer or something.

Some things I'm researching now is a click to update function where it'll check here and compare what version you have vs. what's posted here and if here is newer it'll let you download the new version and reload it. Also a backup settings function would be awesome. Also looking at a drop down menu listing all the MMOBugs plugins and you'd click it to open your external browser which would take you to the wiki entry for it. I'd use the ingame browser but for some reason that POS won't log into mmobugs lol. But there's a bug with the IS TLO I would have to use and hopefully that'll be fixed soon.

 

[eljorgejones]

Suggestion: 2 vertical rows of 7 buttons and maybe the buttons themselves a little smaller. Buttons now are kinda big imo. Guess it may matter on resolution you develop on.

Will knock that out tonite and post it up for you to try.

 

[eljorgejones]

Horizontal Bar Beta (Works only with Brokeback in the post above)

Replace the:

eqisbuttonstest.xml
tab1.xml
tab2.xml
tab3.xml

in your ${InnerSpace.HomeDirectory}\Scripts\EQ\UI folder. After than do a run eqishotbuttonstest from the IS console and give that a look.

 

[eljorgejones]

Thinking the only direct way to communicate to eqbc would be to make a one off ISXEQBC extension for IS. It would act like a proxy or gateway between IS and the eqbcs. More than likely a one way message forward with a built in user of buttonbot or something. There was a conversion of eqbc to ISXEQ a few years back, the code is here http://www.macroquest2.com/phpBB2/viewtopic.php?t=15286. That might be a good start, the ISXEQ and MQ2 stuff would have to be yanked out and it stripped down to expose:

/bc
/bct
/bca
/bcaa
/bccmd

to IS that would allow Lavishscript to access it like a TLO. Then the use of binds could be abandoned and I could modify the script to use the TLO commands to forward regular /commands to eqbcs. Only downside would be to add whatever the extensions connecting user to whatever macros require a master toon name in there ini's.

 

[jodwop]

Think I like this horizontal version more. Thank you. So far you have done some excellent work.