• You've discovered RedGuides, an EverQuest multi-boxing and scripting community 🧙‍♀️⚙️. We want you to play several EQ characters at once, come join us and say hello! 👋

  • A TLP without truebox has thawed (Very Vanilla ready)
    Frostreaver
IonBC Legacy READ OVERVIEW

💾Software IonBC Legacy READ OVERVIEW (2 Viewers) 0.29.5

No permission to download
Ionis updated IonBC (TrueBox) with a new update entry:

0.28.8.5.10

**Note: This is a FULL update, you'll have to replace both client AND host side. Make sure you also replace the bin folder! As our obfuscation requires it.

Bug Fixes:
-Fixed a bug that would cause abnormal commands (/click & /ibt) to occasionally misfire and other unintended functionality.

Let me know if you run in to any issues!

Read the rest of this update entry...
 
Just a quick update!

Bug reports have started to slow down considerably so we're going to move in to 0.28.8.6 here starting Monday!

Here's a reminder of what's coming in that patch:
[CODE title="0.28.8.6"]
New Stuff:
-You can now minimize (hide) hotbars so they're no longer visible but still active!
-There is now a menu for navigating over all buttons that exist on a hotbar for easy manipulation of stacked buttons.
-You can now use the /enableevent & /disableevent command to toggle whether or not an event is enabled quickly (syntax: /enableevent "Event Name Here" ex. /disableevent "OMM Gaze").
-When client receives a command it can now switch to a designated EQ window before processing that command if a checkbox is flipped!

Changes:
-All elements for all windows now activate linearly when tabbing from top to bottom.
-Repeaters and cooldowns values have been changed so they can take a range as opposed to being static. (I.E. instead of 5 you can do 5-10).
-Changed the range of values possible when using a delimiter on /pause, cooldown, repeater and interval to be much less patternized.
-Changed the multi-service IP fields to be hidden based on a boolean as opposed to their default values.
-Changed the /click command to take a |off or |on delimiter. This allows you to declare whether or not the click should be turning a repeater ON or OFF, that way, buttons with multiple /click's don't fall out of their intended sync.
-The event trigger's log boxes will now show the full logpath via a tooltip upon hovering.[/CODE]

Since we're moving forward, just note if a reported bug does not need an urgent fix it will more than likely be released simultaneously with 0.28.8.6.

Thanks for all of the reports we've had over 0.28.8.5's lifespan, all the feedback received has been great and I deeply appreciate it! 🙂
 
Last edited:
Just wanted to let everyone know that work on 0.28.8.6 has commenced! I expect it to hit testing sometime within the week assuming I don't hit any major roadblocks, after that expect a release sometime shortly after if nothing goes horribly awry! :)
 
0.28.8.6 has entered experimental!

Here's a peek at the current finalized patch notes:
[CODE title="0.28.8.6"]
New Stuff:
-You can now minimize (hide) hotbars so they're no longer visible but still active!
-There is now a menu for navigating over all buttons that exist on a hotbar for easy manipulation of stacked buttons. You can find this on the toolbar by pressing the "Btn Manager" button!
-You can now use the /enableevent & /disableevent command to toggle whether or not an event is enabled quickly (syntax: /enableevent "Event Name Here" ex. /disableevent "OMM Gaze").
-When a client receives a command it can now switch to a designated EQ window before processing that command via the switch on receive checkbox in the new Options tab!

Changes:
-All elements for all windows now activate linearly when tabbing from top to bottom.
-Reworked our function that handles command processing. This should eliminate some issues regarding minimal delays in execution.
-Repeaters and cooldowns values have been changed so they can take a range as opposed to being static. (I.E. instead of 5 you can do 5-10 etc.).
-You can now hover over active repeater & cooldown buttons to see the time remaining on their current cycle.
-Changed the range of values possible when using a delimiter on /pause to be much less patternized.
-Changed the multi-service IP fields to be hidden based on a boolean as opposed to their default values.
-Changed the /click command to take a |off or |on delimiter. This allows you to declare whether or not the click should be turning a repeater ON or OFF, that way, buttons with multiple /click's don't fall out of their intended sync.
-The event triggers log boxes will now show the full logpath via a tooltip upon hovering.
-Added a small delay between the static LShift keypress and target keypresses. This should, for the most part, help to remedy occasional capitalization inconsistencies.
-Overhauled the client-side layout, added a Main and Options tab. It is now more consistent with the overall style of the application.

Bug Fixes:
-Fixed a bug where, when trying to throw /click over a button using it's name as opposed to ID, the calling thread would sometimes fail due to a dispatcher issue.
-Fixed a bug where, textboxes that could take a - delimiter, could accept more than one - character causing unintended formatting issues.
-Fixed a bug where, when attempting to assign keybinds, some key arguments weren't being properly handled causing certain keys to return incorrect values.
-Fixed a bug where enabling and disabling triggers wasn't properly distinguishing between server and client triggers.
[/CODE]

If all goes well, expect a release at the end of the week! :)
 
Last edited:
Ionis updated IonBC (TrueBox) with a new update entry:

0.28.8.6: Minimizing, Button Manager, /enabledevent & /disableevent, switch on receive & more!

**Note: This is a FULL update, you'll have to replace both client AND host side. Make sure you also replace the bin folder! As our obfuscation requires it.

New Stuff:
-You can now minimize (hide) hotbars so they're no longer visible but still active!
-There is now a menu for navigating over all buttons that exist on a hotbar for easy manipulation of stacked buttons. You can...

Read the rest of this update entry...
 
Ionis updated IonBC (TrueBox) with a new update entry:

0.28.8.6.1: Toggle GUI when Minimized Bufix

**Note: This is a FULL update, you'll have to replace both client AND host side. Make sure you also replace the bin folder! As our obfuscation requires it.

Bug Fixes:
-Fixed a bug where, when unhiding a hotbar via Toggle GUI on Window Change, the window would show when it was intentionally minimized.

Let me know if you run in to any issues!

Read the rest of this update entry...
 
Hey y'all! I'm glad to see that everyone's been enjoying the new features that came with 0.28.8.6, your feedback has been much appreciated! :)

It's been a couple days since it's official release, but we're moving right along in to 0.29 here soon given there hasn't been much noise regarding any issues.

I figured I'd take this time to give a little update on where we are in development since I haven't really done one in a while! So to give a little overview of my plans for the rest of the year, I made a little roadmap for a quick visualization:

IBRoadmap2022.png

This should give everyone an idea as to what I have planned for development coming up here.

For patch notes on 0.29, 0.30 and 1.0 themselves you'll just have to wait around and see. :)

We have been moving pretty swiftly through all of the community requested functionality that I've been compiling since the start of IonBC's development cycle!

While development on the beta will conclude come sometime December and the application will be considered fully launched, I will still be doing regular maintenance and support on the application as well as adding features that I find it to be lacking or are heavily requested by a large portion of the community.

I'm not entirely sure how we're going to handle monetization when the full 1.0 release rolls around but I'll have that sorted and fully announced prior to it's release!

If anyone has any questions, feel free to ask! :) Look forward to getting all of this stuff released over to y'all in the following months!
 
Last edited:
Thank you so much for this tool, its great and I am boxing 6 sometimes 12

Have you had a chance to think about the console/chat bar we spoke of?
Using eq-channels for feedback of client actions/errors/alerts makes me uncomfortable...
 
Last edited:
Thank you so much for this tool, its great and I am boxing 6 sometimes 12

Have you had a chance to think about the console/chat bar we spoke of?
Using eq-channels for feedback of client actions/errors/alerts makes me uncomfortable...
Hey thanks for the feedback! I appreciate it.

There will be an in-game overlay console added sometime between 0.29 and 1.0 (Now-End of December), as well as an associated /echo command.
 
Ionis updated IonBC (TrueBox) with a new update entry:

0.28.8.6.2: Mouse Functionality Rework & Bugfixes

**Note: This is a FULL update, you'll have to replace both client AND host side. Make sure you also replace the bin folder! As our obfuscation requires it.

Changes:
-Reworked how IonBC handles designated mouse clicks, this functionality should now work as intended.
-When adding a /M1 or /M2 command to a button, the command will now insert itself at the position of the carat...

Read the rest of this update entry...
 
Ionis updated IonBC (TrueBox) with a new update entry:

0.28.8.6.3: More Mouse Stuff

**Note: This is a FULL update, you'll have to replace both client AND host side. Make sure you also replace the bin folder! As our obfuscation requires it.

Changes:
-Changed mouse functionality globally so the new rework should work for all elements that could possibly use mouse functionality.

If you have any issues, don't hesitate to contact me!

Read the rest of this update entry...
 
We're almost in to October and patch 0.28.8.6 has gone off without much of a hitch!

Next month marks the beginning of 0.29 which will be a bit of a lighter patch (content-wise) as most of the work is going in to the auto-updater which will be released alongside it!

I'll keep everyone posted as development continues, if you have any issues please don't hesitate to contact me!
 
Feature request
Ability to specify/limit an event to all or a specific client

Implemented similar to the format for the clients in hotbuttons (you can specify all or a single or multiple comma separated)
 
Last edited:
Just a quick update!

0.29 is coming along, but things may be a bit slower than I originally intended due to life circumstances.

I am in the final semester of my Master's and recently had to move due to work so I've been a bit busier than usual.

I know a lot of you folks already know this but I figured I'd throw it out here in-case patches get a little delayed as a result!

I'm still working on everything, so don't worry! It's just been a bit hectic recently. :)

In the meantime, if you have any problems don't hesitate to contact me.
 
bug report
if you open a hotbar, then use the option to "load a hotbar" of a different hotbar the original hotbar hotkey-binds are still active even thou the original hotbar is not loaded or minimized
 
bug report
if you open a hotbar, then use the option to "load a hotbar" of a different hotbar the original hotbar hotkey-binds are still active even thou the original hotbar is not loaded or minimized
Can't recreate this on my end, tried with numerous profiles and keybinds, always returned logic as intended. I'd make sure that you haven't assigned keybinds to be identical as the one you're trying without noticing.

We get an instance of all active hotbars on keyup so if the hotbar isn't loaded then we can't iterate through it's assigned keybinds. It's probably either the hotbar is getting stuck in memory somewhere and isn't properly disposing (which is very unlikely), it's not actually closed, there's a duplicate keybind on the newly loaded hotbar, has multiple instances or there's something else going on here. We don't store the keybinds from hotbars so there's nothing that should be antiquating.

I'd hazard a guess that it's probably a duplicate keybind.
 
Last edited:
Just a quick update for everyone since I know it's been quite a while!

All of 0.29 is officially in testing with our QA team! Once any bugs are ironed out expect a full release!

Here's a peek at the patch notes:
[CODE title="0.29"]New Stuff:
-Auto-Updater! IonBC now detects when your application is out of date and uses our fancy new updater to fix that for you!

Changes:
-You can now choose, and save, which side of the hotbar the widget bar sticks to via a new option on the toolbar!
-You can now enable launching directly in to the host or client application!
-You can now enable auto-starting (host-side) and auto-connecting (client-side) upon launch!
-You can now delete buttons from the button manager!
-Key commands (/keyhold, /keypress etc.) now recognize the arrow and numpad keys! Syntax: left, right, up, down, num0-9, num/, num*, numplus, num-, num=, num., numlock
-Returns are now enabled for triggers and buttons content/action textboxes respectively! Rejoice, you can now make your macros readable!

Bug Fixes:
-Fixed a bug that was causing non-guild triggers to fire as guild triggers.
-Fixed a bug that was preventing changes to the global black & whitelists from saving in instanced structures.
-Fixed a bug that was causing a null reference when interrupting a processing command that no longer existed.
-Fixed a bug that was preventing the /click command from performing the proper action when called by a non-local hotbar using the |on or |off routine.
-Fixed a bug that was preventing the /click command from working appropriately when called from a triggered action when it was using the |on or |off routine.
-Fixed a bug that was causing triggers using expressions to return undesired results if the expression was located at the very end of a trigger with punctuation.[/CODE]

Some bug fixes may be added before the end of the experimental period so I'll update the notes as necessary!

You can keep track of the experimental's progress by checking the update notes on the resource located ->here<-.

With the auto-updater comes a all machines update! 0.29 will require all other machines be up-to-date before connecting as this version is not backwards compatible. Don't worry though, you'll only have to manually update one more time and then the auto-updater will do the fun stuff for you! :)

If anyone has any questions, don't hesitate to contact me anytime!

Look forward to putting out 0.29 here soon!
 
0.29 testing has been going well! I'm going to give it a few more days but it's been a couple without any bug reports so we're nearing a stable build!

Huge shoutout to my QA team (@battlenet, @bobthebuilder, @Sookinik, @kauegi, @tehfeer, @garbald) for all of the work they've put in over the past 2-3 weeksish that we've been working on this update, really appreciate all the feedback and I hope the patch is up to everyone's standards!

On a side-note, I am moving for work (yes, again...) so 0.30's start will be delayed until my move is done. I'll still be bugfixing and changing things as needed, but start on 0.30 won't begin until I am comfortable in my hopefully permanent residence. :)

If all goes according to plan, expect 0.29 come Monday!

Current Patch Notes:
[CODE title="0.29"]New Stuff:
-Auto-Updater! IonBC now detects when your application is out of date and uses our fancy new updater to fix that for you!

Changes:
-You can now choose, and save, which side of the hotbar the widget bar sticks to via a new option on the toolbar!
-You can now enable launching directly in to the host or client application!
-You can now enable auto-starting (host-side) and auto-connecting (client-side) upon launch!
-You can now delete buttons from the button manager!
-Key commands (/keyhold, /keypress etc.) now recognize the arrow and numpad keys! Syntax: left, right, up, down, num0-9, num/, num*, numplus, num-, num=, num., numlock
-Returns are now enabled for triggers and buttons content/action textboxes respectively! Rejoice, you can now make your macros readable!
-Triggers using expressions now have the ability to check within specific partitions of a string for stricter output.
-You can archive your profiles before updating in-case anything goes horribly awry with the update! You can find this in the options menu of the Updater!

Bug Fixes:
-Fixed a bug that was causing non-guild triggers to fire as guild triggers.
-Fixed a bug that was preventing changes to the global black & whitelists from saving in instanced structures.
-Fixed a bug that was causing a null reference when interrupting a processing command that no longer existed.
-Fixed a bug that was preventing the /click command from performing the proper action when called by a non-local hotbar using the |on or |off routine.
-Fixed a bug that was preventing the /click command from working appropriately when called from a triggered action when it was using the |on or |off routine.
-Fixed a bug that was causing triggers using expressions to return undesired results if the expression was located at the very end of a trigger with punctuation.[/CODE]
 
Ionis updated IonBC (TrueBox) with a new update entry:

0.29.1: Edge Detection Removal & Importer Bugfix

Changes:
-Removed edge detection for the primary screen from the tool and widget bars. This will allow the bars to be freely dragged across any screen. Logic related to this will be reworked and added as a togglable server-side in the following patch (0.30).

Bug Fixes:
-Fixed a bug that was causing the importer to fail to import the full command of triggers & buttons when including returns.

Thanks to @LamahHerder for...

Read the rest of this update entry...
 
Ionis updated IonBC (TrueBox) with a new update entry:

0.29.3: Repackaged Control Primitives

Changes:
-Reworked low-level control primitives to remove the latency-like delay caused when using a /click command.

Thanks to @battlenet and @LamahHerder for giving me some insight on how this issue was occurring. This is a pretty intensive change that directly modifies imported system control primitives so if you run in to any issues with IonBC, as always, don't hesitate to contact me!

Read the rest of this update entry...
 
Work has officially started on 0.30, no official release or experimental date yet since this ones pretty hefty.

Here's the current planned patch notes as a peek at what's to come with 0.30:
[CODE title="0.30"]
New Stuff:
-You can now replace full strings in triggers using #num*#! (ex. Trigger: Your #1*# spell has worn off of #2# would catch something like "Your Unity of the Spirits spell has worn off of playername")
-Buttons/triggers now have the option to ignore all stacking rules and immediately process the command even if there's one already executing! (Does not interrupt, will overlap)
-Triggers can now utilize in-line command targeting via /ibt!
-Buttons now have the option to be uninterruptable!
-We now have the start of a basic top-level language that utilizes two types of variables (bools and ints)! You can use if/else statements to control certain aspects of commands using these variables!

Changes:
-You can now toggle primary screen edge detection for the toolbar and widget bar!
-Reworked our network code for authorization and communicating with the XF API, it should be cleaner and errors more clear.
-Saving hotbars now have a DSTA associated with them.
-/keypress & /keyhold now include M1, M2 and M3

Bug Fixes:
[/CODE]

Things may change in these patch notes as development continues, I'll keep everyone in the loop with the goings ons. If you have any questions feel free to contact me! :)
 
Last edited:
Just a quick update on the conditionals and statements of our top-level language coming in 0.30!

Currently we will accept 3 statements: if, else and else if.

They will be determinant on user-generated variables that do all the declarations for you in the backend, you just have to add them to the button/trigger via the new variables tab. You will be able to modify the assignment of these variables dynamically via commands.

This will allow you to dynamically change the logic of your buttons on the fly by modifying variables when certain conditions are met!

Here's a little sneak peek at what's to come:


There's still quite a lot to do, but the foundation is there. This is going to be quite the loaded update so it will take me a bit longer than usual, but it will be worth it! :) Let me know if you run in to any issues in the mean time!
 
Last edited:
Wanted to share my setup and some tips.... I run 6box sometimes 12box and have 2 separate groups
  1. Use /click instead of /ibt, shorter clearer code and more consistent results
  2. Use a /pause at the end for all casts so you can properly stack commands
    1. I also /pause at the end of some non-casting hotbuttons
  3. Aggressively limit your main bar
    1. Make a hidden bar for complex and/or orchestrated things to call with /click
    2. Use the top border bar as shown in screen for infrequently used things
  4. Events are great, but be wary as they tend to fire at inappropriate times, especially as we dont have conditionals yet.
    1. Having your primary with the events using a /click to a hotbutton for the client works well in some situations
    2. Dont forget a tiny /pause at the end of the majority of your events
    3. Prioritize GINA for reporting and use events for reactions only if needed
      1. Only have GINA running on main PC and map log files for all characters over the network \\pcname

1669888954781.png
1669888970505.png
 
Is there a way to uniformly resize the buttons? Currently adjusting each button manually and attempted to resize it to the same size. Possible eyestrain. Something akin to the Hotbar change size option in EQ would be fantastic.
 
Wanted to share my setup and some tips.... I run 6box sometimes 12box and have 2 separate groups
  1. Use /click instead of /ibt, shorter clearer code and more consistent results
  2. Use a /pause at the end for all casts so you can properly stack commands
    1. I also /pause at the end of some non-casting hotbuttons
  3. Aggressively limit your main bar
    1. Make a hidden bar for complex and/or orchestrated things to call with /click
    2. Use the top border bar as shown in screen for infrequently used things
  4. Events are great, but be wary as they tend to fire at inappropriate times, especially as we dont have conditionals yet.
    1. Having your primary with the events using a /click to a hotbutton for the client works well in some situations
    2. Dont forget a tiny /pause at the end of the majority of your events
    3. Prioritize GINA for reporting and use events for reactions only if needed
      1. Only have GINA running on main PC and map log files for all characters over the network \\pcname

View attachment 43749
View attachment 43750
How are you making one of the hotbars invisible?

Is there a way to uniformly resize the buttons? Currently adjusting each button manually and attempted to resize it to the same size. Possible eyestrain. Something akin to the Hotbar change size option in EQ would be fantastic.
Same
 
Is there a way to uniformly resize the buttons? Currently adjusting each button manually and attempted to resize it to the same size. Possible eyestrain. Something akin to the Hotbar change size option in EQ would be fantastic.
After you close IonBC you can use regex find and replace to set the width/height of all the boxes in the bar
With vscode editor this is how you do regex for find/replace
.* means everything before next line

1670908750137.png
 
Is there a way to uniformly resize the buttons? Currently adjusting each button manually and attempted to resize it to the same size. Possible eyestrain. Something akin to the Hotbar change size option in EQ would be fantastic.
Button defaults are currently planned, once released you'll be able to normalize your button sizes. Until then, what Lamah mentioned is a working solution.
 
It's been a while since I've thrown an update out there so I figured I'd give everyone a heads up about what's been going on! This may be a bit of a long one.

When I started IonBC I didn't think it would end up being as popular as it became over the past couple of months. I didn't expect to have such a great community and be constantly expanding the application, I figured I'd create a simple solution to help ease boxing on TrueBox servers with simple key broadcasting and move on.

That being said, we've definitely progressed past that point but there are some problems:

1. I didn't develop IonBC with the intent of continuously expanding it.

2. I've learned quite a great deal about developing in the environment I've chosen since I started IonBC's development.

With those two things being said, it's created a rift in development that's fairly difficult to overcome. There's a lot of code maintenance that needs to be done and a lot of implementations that need to be rewritten to be cleaner, more efficient and more user-friendly.

I talked to my QA chat about this a little bit and showed them a small demo, but I've decided to rewrite the majority of IonBC. I'll be keeping modernized logic like the communication rewrite, but the majority of the application will be rewritten to allow for a cleaner user-experience, ease of access for continuous updates and my own sanity.

This is a bit of a bummer because I expect it to take me a little while with my new work schedule, but I hope to have a experimental out in the near future for the QA to play with.

I plan to have everything up to 0.30 implemented for this update as well as some other logic I think should be included.

I currently have already finished rewriting the entirety of our authorization process and redesigning the application to be centralized in to one single form.

Here's a sneak peek:


This entirely bypasses the need for any shell executable and seamlessly authorizes user access in-application.

Regardless, I'll keep everyone posted as we move forward. I'm pretty excited to release the new version to everyone coming up here since it's coming together quite nicely. Sorry if I let anyone down with the delay on this, I just really want to make sure the application is up to my own standards as well as everyone else's moving forward.

Hope y'all had a good holiday! :)
 
It's been a while since I've thrown an update out there so I figured I'd give everyone a heads up about what's been going on! This may be a bit of a long one.

When I started IonBC I didn't think it would end up being as popular as it became over the past couple of months. I didn't expect to have such a great community and be constantly expanding the application, I figured I'd create a simple solution to help ease boxing on TrueBox servers with simple key broadcasting and move on.

That being said, we've definitely progressed past that point but there are some problems:

1. I didn't develop IonBC with the intent of continuously expanding it.

2. I've learned quite a great deal about developing in the environment I've chosen since I started IonBC's development.

With those two things being said, it's created a rift in development that's fairly difficult to overcome. There's a lot of code maintenance that needs to be done and a lot of implementations that need to be rewritten to be cleaner, more efficient and more user-friendly.

I talked to my QA chat about this a little bit and showed them a small demo, but I've decided to rewrite the majority of IonBC. I'll be keeping modernized logic like the communication rewrite, but the majority of the application will be rewritten to allow for a cleaner user-experience, ease of access for continuous updates and my own sanity.

This is a bit of a bummer because I expect it to take me a little while with my new work schedule, but I hope to have a experimental out in the near future for the QA to play with.

I plan to have everything up to 0.30 implemented for this update as well as some other logic I think should be included.

I currently have already finished rewriting the entirety of our authorization process and redesigning the application to be centralized in to one single form.

Here's a sneak peek:


This entirely bypasses the need for any shell executable and seamlessly authorizes user access in-application.

Regardless, I'll keep everyone posted as we move forward. I'm pretty excited to release the new version to everyone coming up here since it's coming together quite nicely. Sorry if I let anyone down with the delay on this, I just really want to make sure the application is up to my own standards as well as everyone else's moving forward.

Hope y'all had a good holiday! :)

Thank you for your efforts. It's already a great program! I for one can't wait to see the next iteration :)
 
Has anyone experienced ID numbers changing? I use /click <ID> a lot. I've found that there are instances where the ID changes unexpectedly so I'll have to delete the button and start over so the ID stops changing and I can actually reference the new button.
 
I have trouble logging in this morning. When I click the IonBC icon, then click host, it got stuck at 30% of "getting user sign in. Then it bump to Redguides and give the following message.

Oops! We ran into some problems.​


Invalid client.

I tried delete the app and re-install IonBC and problem remained the same. Please help.

I am level 2 Redguide user, renewal date is Jan 15, 2023.
 
Fixed the API issue in this most recent update, updater won't work for this specific update as it uses a new API. Let me know if you run in to any issues, sorry about that folks was my fault! In all my infinite wisdom I accidentally deleted our API.
 
Last edited:
💾Software IonBC Legacy READ OVERVIEW

Users who are viewing this thread

  • Ionis
Back
Top
Cart