-
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! 👋
- Thread starter Ionis
- Start date
My advice is to not use Full Screen.
IonBC is intended to be used in windowed mode on the host machine, client machines shouldn't matter. If you look in the instructions on the resource page, it's under step 4!
I have never tried to circumvent this in-app, but a few ways you could potentially resolve the issue are:
1. In eqclient.ini, make sure AlwaysOnTop is set to 0. This likely only impacts windowed mode(s), but it's worth a shot!
2. There are some utilities out there that will allow you to run applications in windowed borderless. These can get a bit finnicky with EQ though so I'd test em out a bit and make sure they work before considering this a full solution.
I could build a borderless windowed mode utility for EQ in to IonBC itself, but I'm not sure if Daybreak would or wouldn't use it as another excuse to potentially target the program. That's probably just me being very, very overly paranoid though! It's something for me to consider.
Is there any videos I could look up to maybe help me learn how to get set up and going . Im not super tech savvy and sometimes seeing videos help me figure out things easier. Been reading all the old post seem like a super cool and could be super useful when 6boxing on 6 different computes. right now I do it all by hand but when your turning and hitting 3 on 5 Pcs non stop forever makes you think there has to be a better way
2.5.10 for QA should be out by Wednesday, comes with a bunch of new stuff and some better tools for debugging to speed up the process.Any word on the new version? Starting to get the itch.
If interested in the QA progress, you can check out the resource here.
I am hoping to have QA Wave 3 out sometime over the next month, once that's finished it will be released!
Unfortunately the older content got taken down due to an old account termination (long story). I plan to update all of the documentation, including videos, on release of the new version but if you need help or have any questions you can join our Discord where a lot of folks can help you out or PM me directly!Is there any videos I could look up to maybe help me learn how to get set up and going . Im not super tech savvy and sometimes seeing videos help me figure out things easier. Been reading all the old post seem like a super cool and could be super useful when 6boxing on 6 different computes. right now I do it all by hand but when your turning and hitting 3 on 5 Pcs non stop forever makes you think there has to be a better way
QA Wave 2.5.10 has been released, you can check out the new stuff/changes here!
With that finally being complete, outside of bugfixing from QA reports, I'll be moving in to Wave 3.
This update set me back a bit due to pushing up features that were requested by users that were intended to be in Wave 3, but this also cuts down the time Wave 3 should take!
I plan to have it in QA before the end of November and hopefully finally fully release before Teek hits PoP, but this is barring issues QA run in to.
I'll keep everyone posted as we move forward! Thanks, as always, for all the support!
With that finally being complete, outside of bugfixing from QA reports, I'll be moving in to Wave 3.
This update set me back a bit due to pushing up features that were requested by users that were intended to be in Wave 3, but this also cuts down the time Wave 3 should take!
I plan to have it in QA before the end of November and hopefully finally fully release before Teek hits PoP, but this is barring issues QA run in to.
I'll keep everyone posted as we move forward! Thanks, as always, for all the support!
Development on QA Wave 3 has begun!
As a reminder, here's what's will be releasing with Wave 3:
-Triggers
-Main Window controls keybind logic
-Defaults
-Updater
-Button Manager
-Button Importing
My plan is to have this out before the end of the month or very early December. From there, I plan to update documentation as QA tests the wave. Once QA is done on the wave (1-2 weeks max, if that, barring any severe issues) we'll be on full release!
As with the previous version, I plan to continuously update IonBC as we move forward with the project! Once QA Wave 3 is publicly released, I will open up the floor for feature requests yet again!
Thanks, as always, for your patience and continued support. It's been a very long road, but we're finally on the last wave before public beta release!
As a reminder, here's what's will be releasing with Wave 3:
-Triggers
-Main Window controls keybind logic
-Defaults
-Updater
-Button Manager
-Button Importing
My plan is to have this out before the end of the month or very early December. From there, I plan to update documentation as QA tests the wave. Once QA is done on the wave (1-2 weeks max, if that, barring any severe issues) we'll be on full release!
As with the previous version, I plan to continuously update IonBC as we move forward with the project! Once QA Wave 3 is publicly released, I will open up the floor for feature requests yet again!
Thanks, as always, for your patience and continued support. It's been a very long road, but we're finally on the last wave before public beta release!
Unfortunately, MacroQuest of any flavor is against > DBG's Terms of Service <
DBG's stance on 3rd party apps and DBG's "What constitutes as cheating" > here <
Please consider submitting a suspension report >>> Here <<<
Please keep discussion to suspensions/bans to the mega thread in fippy's - I left this here since you may not be using mq/myseq at all, and might just be using ionbc
All 6 accounts got a 2 week. It seems they are paying some attention again as I have played peacefully for the past couple months with no issues.
Using parsec and IonBC. I only send keypresses to the other PCs.
My plan is to open up the QA version for public use, I haven't had too many reports this time around but I have had 0 suspensions from the community that's currently using the QA version.
I have some stuff to hash out, will share more details later. But expect it to be unlicensed in the next week or so!
Quick update on this, I have received an exorbitant amount of requests for access to the QA version so I've put my other work on hold so I can make changes to the codebase to get this done ASAP.
Expect an update to the QA version with the license removal over the next couple of days.
Once all's said and done, I'll be sharing a relatively large info dump as well just for clarification on what's in there, what's not in there, installation procedure, update procedure, so on and so fourth
One last quick update before public QA release!
Wanted to let everyone know that the license will be removed somewhere between Thursday & Friday evening!
With that being said, I want to be transparent in letting everyone know that some logic will still be locked behind a list of pre-approved users.
There's some sensitive database structures that I am still actively tinkering with to create a system for users to store their settings non-locally. This alleviates issues with corrupted settings on machines that are less than physical (they don't always like to play nice with JSONs), having to setup IonBC how you like it every new machine, so on and so fourth.
These structures are still heavily in testing and, as I wasn't planning on releasing the experimental publicly until QA Wave 3, there were no systems in place to restrict their usage.
A system has been created for allowing said pre-approved users access as opposed to everyone but I am still open to allowing those who would like access to these features the ability to use them if your usability of the application fits certain criteria.
This doesn't restrict any of the usual usage of IonBC, this is strictly for features within the application that currently use the non-local database backend (and all of these features are, also, new).
Nothing anyone has to worry about, just a heads up so there's no confusion if there's some functionality that you appear to be "locked out of".
Appreciate everyone's patience as I scramble to get this ready for public usage asap. Looking forward to dropping this come Thursday/Friday time! Thanks again!
Wanted to let everyone know that the license will be removed somewhere between Thursday & Friday evening!
With that being said, I want to be transparent in letting everyone know that some logic will still be locked behind a list of pre-approved users.
There's some sensitive database structures that I am still actively tinkering with to create a system for users to store their settings non-locally. This alleviates issues with corrupted settings on machines that are less than physical (they don't always like to play nice with JSONs), having to setup IonBC how you like it every new machine, so on and so fourth.
These structures are still heavily in testing and, as I wasn't planning on releasing the experimental publicly until QA Wave 3, there were no systems in place to restrict their usage.
A system has been created for allowing said pre-approved users access as opposed to everyone but I am still open to allowing those who would like access to these features the ability to use them if your usability of the application fits certain criteria.
This doesn't restrict any of the usual usage of IonBC, this is strictly for features within the application that currently use the non-local database backend (and all of these features are, also, new).
Nothing anyone has to worry about, just a heads up so there's no confusion if there's some functionality that you appear to be "locked out of".
Appreciate everyone's patience as I scramble to get this ready for public usage asap. Looking forward to dropping this come Thursday/Friday time! Thanks again!
Experimental is now live and available here!
Please be sure to read the overview before using and let me know if you have any questions or concerns!
Thanks folks!
Please be sure to read the overview before using and let me know if you have any questions or concerns!
Thanks folks!
Last edited:
New trigger system is coming for the experimental, I expect it to be up and running here in the next week or two.
It will include a handful of new options, tighter responsiveness, the ability to send commands to other clients via triggers (I.E. one client gets the trigger and sends the command to a different client), individual profiling and more!
If you'd like to try out new features as they come around before the official release of IonBC 2, check out the experimental version!
Appreciate all of the feedback I've received over the first week of the experimental's public release! I'll keep y'all posted as we progress towards this update.
It will include a handful of new options, tighter responsiveness, the ability to send commands to other clients via triggers (I.E. one client gets the trigger and sends the command to a different client), individual profiling and more!
If you'd like to try out new features as they come around before the official release of IonBC 2, check out the experimental version!
Appreciate all of the feedback I've received over the first week of the experimental's public release! I'll keep y'all posted as we progress towards this update.
Happy Holidays!
A new mechanic for triggers came to me in a dream last night (yes, actually) so I'm going to throw it in there.
It's called trigger lockouts!
It will be a togglable that allows users to lockout triggers activating for a determinant amount of time. This should allow for ease of access when using toons for assisting.
For example, you can have a trigger setup for:
Which starts assist on your toons, then set the trigger lockout to enabled and, let's say, 1 minute.
That trigger will no longer fire for the entire minute, instead only firing once.
Alongside this, there will be a new command:
Which will allow the user to reset the trigger lockout.
You could have this command tied to something like:
To reset the trigger lockout every time an enemy dies, allowing for the assist trigger to reset.
Just spitballing ideas for the new mechanic, but expect it with the experimental 2.7.0 release as well as a bunch of other new trigger junk!
A new mechanic for triggers came to me in a dream last night (yes, actually) so I'm going to throw it in there.
It's called trigger lockouts!
It will be a togglable that allows users to lockout triggers activating for a determinant amount of time. This should allow for ease of access when using toons for assisting.
For example, you can have a trigger setup for:
Soandso slashesWhich starts assist on your toons, then set the trigger lockout to enabled and, let's say, 1 minute.
That trigger will no longer fire for the entire minute, instead only firing once.
Alongside this, there will be a new command:
/resetlockout triggernamehereWhich will allow the user to reset the trigger lockout.
You could have this command tied to something like:
You have slainTo reset the trigger lockout every time an enemy dies, allowing for the assist trigger to reset.
Just spitballing ideas for the new mechanic, but expect it with the experimental 2.7.0 release as well as a bunch of other new trigger junk!
2.7.0 of the Experimental is here and it brings with it the full trigger suite!
Check out the notes here!
This is a massive overhaul to the trigger system so I plan to make a video over the next week going over usages and the changes, will update everyone when that's posted.
Going to take a break for a week or so then start cranking out the next update, this one took a lot out of me the past month going to reset.
If you have any questions, concerns or issues, don't hesitate to reach out to me!
Check out the notes here!
This is a massive overhaul to the trigger system so I plan to make a video over the next week going over usages and the changes, will update everyone when that's posted.
Going to take a break for a week or so then start cranking out the next update, this one took a lot out of me the past month going to reset.
If you have any questions, concerns or issues, don't hesitate to reach out to me!
Ionis updated IonBC (TrueBox) with a new update entry:
Experimental 2.7.5
Read the rest of this update entry...
Experimental 2.7.5
Read the rest of this update entry...
Ionis updated IonBC (TrueBox) with a new update entry:
0.29.4 Reupload
Read the rest of this update entry...
0.29.4 Reupload
Read the rest of this update entry...
Work on Experimental 2.8 has commenced!
This will contain:
-Importing/Exporting Hotbars/GUIs/Triggers
-Button Manager
-Button Defaults
-Small UI additions such as patch note window, first launch agreements, et. al.
-Testing for Pantheon usability/optimization (due to user requests)
I expect the update to be ready by the end of February to mid-March at the latest as I've been having a spot of health issues. (I am recovering, nothing to worry about!)
Huge shoutout to all the current experimental users that have been enjoying the application and giving feedback/bug reports, I greatly appreciate it.
I'll keep everyone posted as we progress in to this new update! In the meantime, don't hesitate to let me know if you have any issues, questions, concerns or suggestions relating to the current experimental!
This will contain:
-Importing/Exporting Hotbars/GUIs/Triggers
-Button Manager
-Button Defaults
-Small UI additions such as patch note window, first launch agreements, et. al.
-Testing for Pantheon usability/optimization (due to user requests)
I expect the update to be ready by the end of February to mid-March at the latest as I've been having a spot of health issues. (I am recovering, nothing to worry about!)
Huge shoutout to all the current experimental users that have been enjoying the application and giving feedback/bug reports, I greatly appreciate it.
I'll keep everyone posted as we progress in to this new update! In the meantime, don't hesitate to let me know if you have any issues, questions, concerns or suggestions relating to the current experimental!
I'll have to check this out... Just started on Teek over thanksgiving break.
Then over Christmas Break I literally wrote a TCP broadcaster with repeaters etc... similar architecture pilot from host and connect clients.
I was browsing around and came across this thread, and used redcents to reactivate my lvl 2 just to read through what you've done.
Cool shit man.
Then over Christmas Break I literally wrote a TCP broadcaster with repeaters etc... similar architecture pilot from host and connect clients.
I was browsing around and came across this thread, and used redcents to reactivate my lvl 2 just to read through what you've done.
Cool shit man.
Appreciate the kind words!
I'd recommend checking out the experimental if you're interested as it's the next stage in the application's development and completely modernizes the codebase!
The production version works fine if you'd prefer to use that, but the experimental houses a whole new suite of utility and security features as well as a more optimized experience! The experimental will also be replacing the production version over the course of this year!
If you do choose to use the experimental, please be sure to read over the overview covering data collection, security, etc. prior to usage.
Feel free to check out our Discord as well! Lots of great folks over there with a wealth of information if I'm not around to answer any questions.
Regardless, let me know what you think or if you have any questions/issues! I'm always open to feedback and suggestions on how to better improve the program!
Last edited:
Experimental or production version?
They have some fairly fundamental differences in logic, let me know which you're using and I can help out!
using the production version,Experimental or production version?
They have some fairly fundamental differences in logic, let me know which you're using and I can help out!
Apologies for the late reply, was away for the weekend.
Last edited:
Not a problem!
Try out the Experimental version and see if you have any luck! If not, I can take a look as the Experimental will be taking over as the new production version over the next few months anyhow!
Last edited:
Not a problem! Let me know if the issue persists in the future at all or anything else you may run in to!
frenchysonline
Active member
- Joined
- Sep 25, 2017
- RedCents
- 337¢
Just bought a brand new laptop. Installed EQ and IonBC. Everything is running, except for "processing command" on new laptop. IonBC receives the command, but it is never executed. Any ideas or suggestions?
frenchysonline
Active member
- Joined
- Sep 25, 2017
- RedCents
- 337¢
Pretty much all of them. Tried to do /assist, /follow, etc
Can you send me the profile or the exact command text?
Hey everyone! It's been a while.
I know I haven't been super consistent with updating the experimental over the past half a year or so, I had landed a lead position at a studio back in May which resulted in me losing practically any free time I had to dedicate to personal projects such as IonBC. I feel like I really dropped the ball for folks who were waiting for the dedicated updates to the Experimental and I sincerely apologize for that.
Now for the good news, my time is starting to free itself up again! I plan to go back and start implementing updates to the Experimental starting today.
I have drastically cut down some feature parity that either seemed redundant for release or bloated. My goal is to avoid the redundancy that a lot of the original IonBC features caused when implemented.
As such, the following features:
Process Manager
Global Feature Keybinds
Will be cut from the current experimental version as they're either redundant or not core enough for me to spend time on pre-release. However, this doesn't mean that they are cut forever. I do plan to implement the Process Manager back in at some point down the line but I'd rather keep that for a post-alpha then spend time working on it while there's still core features that need implementation.
With that being said, once the following are complete:
Button Defaults
Button Manager
Importing Buttons/Triggers
The current Experimental version will be replacing the production version of IonBC.
For those of you that would like to stick with the legacy version you are happy to do so! I plan to make an entirely different resource page for IonBC 2 (Experimental) once it's ready to be pushed in to production. This should keep the integrity of the legacy (current production) versions auth in-tact.
That's all for now, I'll do my best to keep everyone posted as we move forward. Most of the weekend for IonBC will be done in the evenings and weekends so if you have any questions it'd be best to reach out to me then (and through Discord at zerxes0809).
Thanks fellas!
I know I haven't been super consistent with updating the experimental over the past half a year or so, I had landed a lead position at a studio back in May which resulted in me losing practically any free time I had to dedicate to personal projects such as IonBC. I feel like I really dropped the ball for folks who were waiting for the dedicated updates to the Experimental and I sincerely apologize for that.
Now for the good news, my time is starting to free itself up again! I plan to go back and start implementing updates to the Experimental starting today.
I have drastically cut down some feature parity that either seemed redundant for release or bloated. My goal is to avoid the redundancy that a lot of the original IonBC features caused when implemented.
As such, the following features:
Process Manager
Global Feature Keybinds
Will be cut from the current experimental version as they're either redundant or not core enough for me to spend time on pre-release. However, this doesn't mean that they are cut forever. I do plan to implement the Process Manager back in at some point down the line but I'd rather keep that for a post-alpha then spend time working on it while there's still core features that need implementation.
With that being said, once the following are complete:
Button Defaults
Button Manager
Importing Buttons/Triggers
The current Experimental version will be replacing the production version of IonBC.
For those of you that would like to stick with the legacy version you are happy to do so! I plan to make an entirely different resource page for IonBC 2 (Experimental) once it's ready to be pushed in to production. This should keep the integrity of the legacy (current production) versions auth in-tact.
That's all for now, I'll do my best to keep everyone posted as we move forward. Most of the weekend for IonBC will be done in the evenings and weekends so if you have any questions it'd be best to reach out to me then (and through Discord at zerxes0809).
Thanks fellas!
Experimental has been updated to 2.8.00
This is a massive overhaul to our authorization library that I've been working on the past couple of months. I, for the most part, rewrote it in it's entirety and reimplemented it over the IonBC 2 and it's associated Updater.
Let me know if you run in to any issues!
This is a massive overhaul to our authorization library that I've been working on the past couple of months. I, for the most part, rewrote it in it's entirety and reimplemented it over the IonBC 2 and it's associated Updater.
Let me know if you run in to any issues!
Experimental has been updated to 2.9.00
This comes with a full refactor to our UI engine, mostly under the hood stuff that should make UI interactions quicker, cleaner and more responsive (as well as easier to expand upon).
Feel free to check the patch notes at the link above and let me know if you have any issues.
This comes with a full refactor to our UI engine, mostly under the hood stuff that should make UI interactions quicker, cleaner and more responsive (as well as easier to expand upon).
Feel free to check the patch notes at the link above and let me know if you have any issues.
