I may just be missing something. Clicking hot buttons to send commands works fine. But clicking keyboard won't send it over. I've tried numpad and the 1 key so far. Working right now so maybe play with it more later.
-
Hail, we're RedGuides. We want you to play six (yes, 6!) EverQuest characters at once. We have scripts and a friendly community to help, please join our playstyle and say hello! 👋 -
We've added LLM sections to our Terms & Rules and Resource Rules, for everyone's sanity & in-game safety.Read more
a. Do not replace your voice with an LLM. This goes for your posts and your scripts. Drafting and editing with a tool is fine, but don't take you out of what you share.
b. Do not replace your EQ character's voice with an LLM. We don't want scripts that speak over/ooc,/shoutor other public channels. This has been an unwritten rule that's kept casino scripts off the site for decades, but we're now compelled to make it clear: keep automated communication private.
Why Does RG Review Scripts?
Nearly every LLM-written Lua script we see is making your character do impossible things, and rarely in a way that's beneficial to you. We've seen heavy server hammering,/targetover impossible distances when/nav spawnwould passively accomplish the same thing, a spawn search that fires 20+ times per second, and other pointless actions that are likely annoying GMs.
You are welcome to use LLMs as a tool to structure, draft, and edit your work, but please read critically before hitting/lua run
💾Software IonBC Legacy READ OVERVIEW [Deleted]
- Thread starter Ionis
- Start date
- Status
Vexen
Member
I'm far from an expert at using this as I just started using it recently but the basic buttons and commands that get sent are working good. Hopefully someone else chimes in with more support. I hope you get it working.
Vexen
Member
/keypress is a little funky for me if that's what you're trying. Try /keyhold {key}|{duration ms} - /keyhold s|100
Hey all!
Sorry for my absence, have been focusing a great deal of my time working on the new RGManager but I wanted to take a moment and let anyone know who may not be in the Discord that updates for IonBC are currently on pause while the rewrite is in development.
There are a handful of currently known issues that you may run in to and, back in September/October time, I asked the community whether they'd like me to push back the rewrite to solve these issues or focus primarily on the release of the new version. It was more or less overwhelming weighted on the side of working on the new version as it will almost entirely replace the current one. With that being said, you may run in to issues that have been long overdue for a fix on this current iteration of IonBC and I apologize for that!
I target to have a stable build of the rewrite out and ready for the upcoming TLP come May, until then if you have any issues that you think may be related to user error feel free to reach out to me and I'd be happy to take a look at things!
Again, I'm sorry it's been quite a long time between releases here. Between life, work, some new projects & my own general issues with wanting to get everything as perfect as it can be, it's been taking an exorbitant amount of time. I will have some news in the coming months here about an upcoming release date but until then, I'll try to keep everyone posted as we move along more consistently!
Sorry for my absence, have been focusing a great deal of my time working on the new RGManager but I wanted to take a moment and let anyone know who may not be in the Discord that updates for IonBC are currently on pause while the rewrite is in development.
There are a handful of currently known issues that you may run in to and, back in September/October time, I asked the community whether they'd like me to push back the rewrite to solve these issues or focus primarily on the release of the new version. It was more or less overwhelming weighted on the side of working on the new version as it will almost entirely replace the current one. With that being said, you may run in to issues that have been long overdue for a fix on this current iteration of IonBC and I apologize for that!
I target to have a stable build of the rewrite out and ready for the upcoming TLP come May, until then if you have any issues that you think may be related to user error feel free to reach out to me and I'd be happy to take a look at things!
Again, I'm sorry it's been quite a long time between releases here. Between life, work, some new projects & my own general issues with wanting to get everything as perfect as it can be, it's been taking an exorbitant amount of time. I will have some news in the coming months here about an upcoming release date but until then, I'll try to keep everyone posted as we move along more consistently!
nooneimportant
New member
any news ?
Over the next 3 weeks I am going to be crunching as much as I can on the new version, I'm hoping to have a stable QA build by the new prog server release but I'm not going to 100 % confirm that.
I hope to post some consistent updates showing off some new stuff as I'm crunching but it really depends if I have time as I'd like to dedicate at least 5-6 hours a day over the weekdays to IonBC (with the other 5-6 going to the new RGManager).
Starting simple, this week I figured I'd just show off the current UI optimizations:
A lot of flair, but the entire application has been consolidated in to a single window at runtime. Client & Host can be accessed from the same element as opposed to having two separate ones that you'd need to go back and fourth between.
Host still requires a sign-in, Client does not.
Events & Keymaps have been moved to their own respective page called "Control". The organizational structure of these pages has been designed to (hopefully) be more clear to the end user but also to cut down on the number of windows needed for certain functionality.
Instead of a window opening for things like keymapping, event lists etc. they've been categorically organized in to their own tab group(s).
Hopefully this alleviates some of the window juggling that the current IonBC contains. I've also streamlined adding, removing, importing & editing events to be consolidated in to controls within that tab. This way there isn't multiple windows you need to go through for each individual control, they're all isolated within that tab itself to be accessed dynamically based on the grids selected item.
Toggles (current Options) have been changed significantly as well:
Each option category has been organized in to it's own respective page, custom framework elements (like toggle buttons etc) have been created for more ease of access.
This should simplify recognizing what option does what and what part of the application they impact.
That's it for now, like I said I'd like to post some snippets here or there as we start to wrap up this version so I will share what I can when I can.
Looking forward to finally dropping this update, it's been a long time coming!
I hope to post some consistent updates showing off some new stuff as I'm crunching but it really depends if I have time as I'd like to dedicate at least 5-6 hours a day over the weekdays to IonBC (with the other 5-6 going to the new RGManager).
Starting simple, this week I figured I'd just show off the current UI optimizations:
A lot of flair, but the entire application has been consolidated in to a single window at runtime. Client & Host can be accessed from the same element as opposed to having two separate ones that you'd need to go back and fourth between.
Host still requires a sign-in, Client does not.
Events & Keymaps have been moved to their own respective page called "Control". The organizational structure of these pages has been designed to (hopefully) be more clear to the end user but also to cut down on the number of windows needed for certain functionality.
Instead of a window opening for things like keymapping, event lists etc. they've been categorically organized in to their own tab group(s).
Hopefully this alleviates some of the window juggling that the current IonBC contains. I've also streamlined adding, removing, importing & editing events to be consolidated in to controls within that tab. This way there isn't multiple windows you need to go through for each individual control, they're all isolated within that tab itself to be accessed dynamically based on the grids selected item.
Toggles (current Options) have been changed significantly as well:
Each option category has been organized in to it's own respective page, custom framework elements (like toggle buttons etc) have been created for more ease of access.
This should simplify recognizing what option does what and what part of the application they impact.
That's it for now, like I said I'd like to post some snippets here or there as we start to wrap up this version so I will share what I can when I can.
Looking forward to finally dropping this update, it's been a long time coming!
Looks like DPG has decided to war on keystroke broadcasters this time around.
I am looking in to what they could potentially be doing but I have some ideas.
As a side note, remember using any third-party program could result in a suspension but be wary of other keystroke broadcasters as well such as Multiplicity, AHK, Input Director so on and so fourth.
I am going to double down on obfuscation & security, not going to say exactly what to be on the safer side but I will do my best to circumvent current detection methods. Of course, this means the current upcoming version will have to be delayed, but I'd really like to hunker down on end-user security as much as possible.
I am deeply sorry for any inconvenience this may have caused folks, I know it's a bonus XP weekend and this fucking sucks. We lived in the grey area for a while, dancing on the edge, but it seems like DPG has taken their stance regarding input broadcasting.
Again, I will do my best to make IonBC as safe as possible again but there's a lot to tackle here, I'll keep everyone posted as always but, if you haven't already, please share suspension reports here:
I can keep better track of any patterns as well as see other contributing factors that way.
Thank you all again for the understanding, I will do my best to get us back on track.
Edit: I have removed the warning from the front page. After further investigation it looks like key broadcasters were more caught in the crossfire of other TPS flags and are unlikely to be the actual target. This does not mean that using IonBC is entirely safe though. Using any third party software to enhance or modify your game experience could potentially result in a suspension. Just be cautious, mindful of others and avoid any injection, memory manipulation or full automation.
I am looking in to what they could potentially be doing but I have some ideas.
As a side note, remember using any third-party program could result in a suspension but be wary of other keystroke broadcasters as well such as Multiplicity, AHK, Input Director so on and so fourth.
I am going to double down on obfuscation & security, not going to say exactly what to be on the safer side but I will do my best to circumvent current detection methods. Of course, this means the current upcoming version will have to be delayed, but I'd really like to hunker down on end-user security as much as possible.
I am deeply sorry for any inconvenience this may have caused folks, I know it's a bonus XP weekend and this fucking sucks. We lived in the grey area for a while, dancing on the edge, but it seems like DPG has taken their stance regarding input broadcasting.
Again, I will do my best to make IonBC as safe as possible again but there's a lot to tackle here, I'll keep everyone posted as always but, if you haven't already, please share suspension reports here:
I can keep better track of any patterns as well as see other contributing factors that way.
Thank you all again for the understanding, I will do my best to get us back on track.
Edit: I have removed the warning from the front page. After further investigation it looks like key broadcasters were more caught in the crossfire of other TPS flags and are unlikely to be the actual target. This does not mean that using IonBC is entirely safe though. Using any third party software to enhance or modify your game experience could potentially result in a suspension. Just be cautious, mindful of others and avoid any injection, memory manipulation or full automation.
Last edited:
You know what's really funny about all of this is that I used it a couple weeks ago to test it and it was fine. They waited until everyone spent their money on subscriptions for Teek and now all of a sudden people are being suspended. Daybreak is making sure they're making their money BEFORE they do any suspensions.
I was not.
Marketman21
New member
i was using a vpn on 2/3 machines. i put in an appeal but pretty sure they will tell me to do one. Shame was a nice QOL dont think it should be 7 day suspension when you got auto bots running 24/07 on tlps that dont get banned.
Has anyone else appealed their decision? I know it's unlikely that they unlock the accounts, but I was curious if anyone else was trying? I am trying, but I haven't heard anything from them yet. I'm sure it's super low priority for them. They'd rather be out there busting people for trying to enjoy a game.
I guess they don't want my $90 a month? Because if they don't offer me any relief I'm going to dispute all the charges and get my money back and walk away.
I guess they don't want my $90 a month? Because if they don't offer me any relief I'm going to dispute all the charges and get my money back and walk away.
AtomicBlaze
New member
I got a 7 day suspension on all 5 accounts, I had IonBC running as well as MoveMouse program to keep my EQ session active.
Slightly off Topic, but did DBG change the true box code? Last TLP, as long as I pressed different keys and never too quickly, on each box, I was fine. This TLP, I get DC'd much more. The last straw was. I mouse pressed a social Macro on each of my 5+ computers with-in a second of each other and it DC'd me. The social Macro had 1 line of /invite. Speculation, but before EQ was monitoring key presses. and now maybe now DGB is monitoring similar traffic from the same IP address, and using that to DC' people if its too similar? I was not using a VPN, VM, IonBC, MQ, MySEQ, or MQ. Mainly just Multiplicity. Oddly. I turned on my Multiplicity broadcast ability, and no mater now much I spammed /tar and /says and stuff. I even spammed /invite and it refused to DC.
Marketman21
New member
i heard back from the apeal, 7 days stands for using third party programs i wonder if myseq is safe to use atm. Not using anything but multiplicity at the moment just in case
Same bro. Same.
I would say, no, it is not safe. They can see it running. The server and client are well known processes. I am staying away from all EQ servers for a while. I created my own emulation server to play on while I monitor the current situation with Darkpaw.
Some news:
I have discussed some things and came to some solutions, there are a few more hoops to go through to really iron out where we stand but for now I plan to deepen obfuscation, user-end security & interval detection.
This means:
-Deeper level process obfuscation
-Deeper level assembly obfuscation
-Randomized command intervals (option can be toggled, will be on by default, not going to explain methodology behind it for obvious reasons)
These are the first steps I'm going to take to help combat suspensions and keep users safe. There's a lot more I could do, but I still want to, at the very least, try to stay within reason as far as what Daybreak finds acceptable. I will not inject, I will not handle proprietary data and I will avoid memory manipulation. As I said before, I have a couple more hoops to jump through to help solidify everything I could do to help folks coming up here in the future but I can't say much else on that.
I want to be clear that using any third-party software while playing EverQuest to modify your experience in any way is subject to suspension. It seems like a few folks have found a solution to the issue and that's fantastic, but please be wary. It is difficult, by design, to tell what exactly they were targeting with the suspension wave but after a couple meetings, talking to the community and investigating it seems we were mostly caught in the crossfire as opposed to the direct target. Regardless, I want everyone to have as enjoyable of an experience in-game as possible, you cannot do that if you're suspended so just be cautious.
In other news, I plan to have the current release candidate ready sometime towards late July.
With that being said, I wanted to show off the new toolbar widgets and see what everyone thinks!
I streamlined a lot of the buttons that shared logic in to one button as well as introduced a new Quick Reload button for individual hotbars. This should simplify navigating the toolbar as well as make the amount of controls less overwhelming for new users.
Create Button - Opens the Create Button window
Quick Reload - Reloads the current hotbar to it's last saved state, useful for quickly undoing a multitude of mistakes or correcting positionings without having to reset everything.
Load - Load a hotbar or GUI
Delete - Delete a hotbar or GUI
Button Manager - Opens the Button Manager window
Buttons on the right-hand side are functionally identical to how they currently work in IonBC. Squish such as side swapping hasn't been instantiated yet but will be in place prior to release.
I will keep everyone posted as we go, but that's all for now! If anyone has any questions, feel free to ask or reach out! Thanks guys, I appreciate all of the kind words & understanding over the course of this situation, it really means a lot to me. Let me know what you think of the new Toolbar & associated widgets!
I have discussed some things and came to some solutions, there are a few more hoops to go through to really iron out where we stand but for now I plan to deepen obfuscation, user-end security & interval detection.
This means:
-Deeper level process obfuscation
-Deeper level assembly obfuscation
-Randomized command intervals (option can be toggled, will be on by default, not going to explain methodology behind it for obvious reasons)
These are the first steps I'm going to take to help combat suspensions and keep users safe. There's a lot more I could do, but I still want to, at the very least, try to stay within reason as far as what Daybreak finds acceptable. I will not inject, I will not handle proprietary data and I will avoid memory manipulation. As I said before, I have a couple more hoops to jump through to help solidify everything I could do to help folks coming up here in the future but I can't say much else on that.
I want to be clear that using any third-party software while playing EverQuest to modify your experience in any way is subject to suspension. It seems like a few folks have found a solution to the issue and that's fantastic, but please be wary. It is difficult, by design, to tell what exactly they were targeting with the suspension wave but after a couple meetings, talking to the community and investigating it seems we were mostly caught in the crossfire as opposed to the direct target. Regardless, I want everyone to have as enjoyable of an experience in-game as possible, you cannot do that if you're suspended so just be cautious.
In other news, I plan to have the current release candidate ready sometime towards late July.
With that being said, I wanted to show off the new toolbar widgets and see what everyone thinks!
I streamlined a lot of the buttons that shared logic in to one button as well as introduced a new Quick Reload button for individual hotbars. This should simplify navigating the toolbar as well as make the amount of controls less overwhelming for new users.
Create Button - Opens the Create Button window
Quick Reload - Reloads the current hotbar to it's last saved state, useful for quickly undoing a multitude of mistakes or correcting positionings without having to reset everything.
Load - Load a hotbar or GUI
Delete - Delete a hotbar or GUI
Button Manager - Opens the Button Manager window
Buttons on the right-hand side are functionally identical to how they currently work in IonBC. Squish such as side swapping hasn't been instantiated yet but will be in place prior to release.
I will keep everyone posted as we go, but that's all for now! If anyone has any questions, feel free to ask or reach out! Thanks guys, I appreciate all of the kind words & understanding over the course of this situation, it really means a lot to me. Let me know what you think of the new Toolbar & associated widgets!
Last edited:
Just curious to see if anyone has tried this after their ban?
I was using MySEQ as well as IonBC and got a 7 day sus pretty much when everyone else did that posted here. I haven't had the nerve to try it again. I'm also debating subbing to a VPN but not sure if that will solve anything.
I was using MySEQ as well as IonBC and got a 7 day sus pretty much when everyone else did that posted here. I haven't had the nerve to try it again. I'm also debating subbing to a VPN but not sure if that will solve anything.
Sorry to hear that
Using VPNs or any form of virtualization by chance? Seems to be a common theme around the few suspension reports I've received thus far.
None of my current throwaways nor main accounts have been hit yet but I, mistakenly, hadn't setup a throwaway group using VPNs or any form of virtualization to see if there could be something funky there.
Next stage in testing here will be to setup another group running VPNs and a couple using forms of virtualization, using programs shared via users feedback (various VPNs, Parsec, Virtual Box(es), Multiplicity, Input Director, et. al.), to see if I can force a trigger that way while keeping the others running. See if I can track down some level of root common denominator here that could be attributing
I just got a 7 day suspension on my accounts as well. IonBC and Multiplicity were the only things I've been running. I do have ShowEQ but I'm using the linux version on its' own box on my network. No VPNs here, I do have VMWare Workstation installed on my PC, but it's for work stuff.
Oof... 2 of my accounts got 14 day suspensions, the rest 7 day. I'm not even doing anything like PLing in the game... I'm like level 15 on Teek.
Oof... 2 of my accounts got 14 day suspensions, the rest 7 day. I'm not even doing anything like PLing in the game... I'm like level 15 on Teek.
Just out of curiosity: What does a VPN do in this case? Isn't the issue that they're looking for local processes on the system?
@Ionis sorry for the delayed response: The only two thing I was using was IonBC and SEQ. That said, I had very type-heavy macros on my Shaman to handle buffs and whatnot. I think I just need to stick to keypress macros as I get the feeling they're looking for people typing commands manually that wouldn't normally be typed. Like a lot of
@Ionis sorry for the delayed response: The only two thing I was using was IonBC and SEQ. That said, I had very type-heavy macros on my Shaman to handle buffs and whatnot. I think I just need to stick to keypress macros as I get the feeling they're looking for people typing commands manually that wouldn't normally be typed. Like a lot of
/mem and /cast commands typed manually over and over.Been a little bit since I've given an update but I figured it was time to show off the brand new Button Designer (replaces Create Button win)!
As promised, here is the new Button Designer demo (replaces Create Button win):
Let's go over a couple things!
General
This tab is functionally identical to the current tab with a cleaner design and more expandable functionality for future features. Outside of that, everything that the Create Window's general tab could potentially do is housed here.
Settings
The new Settings (replaces Options) page, for the most part, is functionally identical to the current one excluding one key factor: you can no longer see nor modify the buttons →default← key interval
This is by design as a security measure to help mitigate suspensions due to certain detection methods. You can, however, still enable the ability to set a custom key interval (at your own risk) but you can never expose whatever default interval the button is using in-app or through any of the associated file structures and every button has their own unique default interval.
Design
Here's the big one, the new designer for buttons! This allows for more pinpoint precision when customizing buttons. There's also a new feature for customizing font size & stylization for those of you who don't appreciate the level of eye strain and squinting we had to do with the old static font size!
I've, also, consolidated all objects related to the button to be hosted dynamically within the base framework element that constructs the button's core. While this more than likely won't be a super noticeable change, it does, however, take some of the active load off of the main UI thread as well as removing the possibility for element association issues.
Defaults for this page can be edited in the Defaults tab of the Server page in the apps main window.
This is likely to change as I add/play with features coming up to initial release here but let me know what y'all think!
As promised, here is the new Button Designer demo (replaces Create Button win):
Let's go over a couple things!
General
This tab is functionally identical to the current tab with a cleaner design and more expandable functionality for future features. Outside of that, everything that the Create Window's general tab could potentially do is housed here.
Settings
The new Settings (replaces Options) page, for the most part, is functionally identical to the current one excluding one key factor: you can no longer see nor modify the buttons →default← key interval
This is by design as a security measure to help mitigate suspensions due to certain detection methods. You can, however, still enable the ability to set a custom key interval (at your own risk) but you can never expose whatever default interval the button is using in-app or through any of the associated file structures and every button has their own unique default interval.
Design
Here's the big one, the new designer for buttons! This allows for more pinpoint precision when customizing buttons. There's also a new feature for customizing font size & stylization for those of you who don't appreciate the level of eye strain and squinting we had to do with the old static font size!
I've, also, consolidated all objects related to the button to be hosted dynamically within the base framework element that constructs the button's core. While this more than likely won't be a super noticeable change, it does, however, take some of the active load off of the main UI thread as well as removing the possibility for element association issues.
Defaults for this page can be edited in the Defaults tab of the Server page in the apps main window.
This is likely to change as I add/play with features coming up to initial release here but let me know what y'all think!
Hey all!
Just wanted to show off the new auto interval system:
This will be included with the official release and is part of combating detection.
How does it work?
Each individual button will have an interval strength slider that can be modified by the end-user. This slider's value is then used as a determinant in an algorithm that uses multiple levels of randomization to decide a range for the key interval. This range will be different every single keystroke meaning the timing of each individual keystroke will be chosen from a different determinant range based on said algorithm with multiple levels of randomization nested in it's own unique seed influenced by the button's interval strength. This should ensure we can get as close as possible to each keystroke of each part of a command seeming as human-like as possible.
The key interval and associated algorithm(s) are never visible to the end-user. If you'd like to use a custom key interval you can still do so by enabling the Custom Key Interval toggle button and entering whatever you'd like! This functionality, of course, can still take a range so the end-user has the ability to customize randomization even in a static interval.
In other news, the QA version is now live! I'm going to be releasing batch functionality piece by piece for testing as I deem fit. I'm planning an early to mid-September launch for the release version!
If you have any questions feel free to ask, looking forward to getting this out to everyone!
Just wanted to show off the new auto interval system:
This will be included with the official release and is part of combating detection.
How does it work?
Each individual button will have an interval strength slider that can be modified by the end-user. This slider's value is then used as a determinant in an algorithm that uses multiple levels of randomization to decide a range for the key interval. This range will be different every single keystroke meaning the timing of each individual keystroke will be chosen from a different determinant range based on said algorithm with multiple levels of randomization nested in it's own unique seed influenced by the button's interval strength. This should ensure we can get as close as possible to each keystroke of each part of a command seeming as human-like as possible.
The key interval and associated algorithm(s) are never visible to the end-user. If you'd like to use a custom key interval you can still do so by enabling the Custom Key Interval toggle button and entering whatever you'd like! This functionality, of course, can still take a range so the end-user has the ability to customize randomization even in a static interval.
In other news, the QA version is now live! I'm going to be releasing batch functionality piece by piece for testing as I deem fit. I'm planning an early to mid-September launch for the release version!
If you have any questions feel free to ask, looking forward to getting this out to everyone!
How do we become a QA user?
Asking! Plain and simple!
On the next QA drop which should be coming up here next week I will need 1 or 2 more QA users but that should cover it until folks go inactive or drop out of the role.
If you're interested, feel free to PM me!
QA Wave 2 is here!
You can see the patch notes here if you're interested in seeing the absolutely massive amount of changes that this second wave brings compared to the current version.
I am expecting to do one more QA Wave before we enter the new versions beta so expect that over the next couple of weeks!
If anyone has any questions feel free to let me know! Excited to finally be pushing all this out!
You can see the patch notes here if you're interested in seeing the absolutely massive amount of changes that this second wave brings compared to the current version.
I am expecting to do one more QA Wave before we enter the new versions beta so expect that over the next couple of weeks!
If anyone has any questions feel free to let me know! Excited to finally be pushing all this out!
With QA Wave 2 finally being fully released (patch notes here) I wanted to go over how the next 3-4 weeks are going to break down as we get closer to full release!
We have 2 more waves to go through before we finally release the next beta version:
QA Wave 2.5
-Version detection
-Mouse hooking (specifically for cursor manipulation when in-game)
-Hiding Toolbar
-Hide Hotbar Tooltips
QA Wave 3
-Triggers
-Full Debug Suite
-Main Window controls keybind logic
-Defaults
-Updater
-Button Manager
-Button Importing
I plan to have QA Wave 2.5 released this week and QA Wave 3 released over the next couple of weeks. After QA Wave 3 we will, after 2 arduous years, finally reach the full release of the new IonBC!
With that in mind there's a couple things to note with the new release:
1. The new version will not auto-update from the previous, everyone will need a fresh install.
2. The deprecated hotbar/button structures will not be translated in to the new structure, apologies for the inconvenience there as well!
Lastly, while the functionality of IonBC remains the same, there are a wide array of improvements that have fundamentally changed how certain aspects work. I will be redoing the documentation to mirror those changes as to avoid any confusion for new and returning users!
If anyone has any questions or concerns please feel free to reach out to me anytime!
Thanks again for all the support over the years, we're finally almost to the finish line on this new version and then we can move back in to community suggestions for expansion!
We have 2 more waves to go through before we finally release the next beta version:
QA Wave 2.5
-Version detection
-Mouse hooking (specifically for cursor manipulation when in-game)
-Hiding Toolbar
-Hide Hotbar Tooltips
QA Wave 3
-Triggers
-Full Debug Suite
-Main Window controls keybind logic
-Defaults
-Updater
-Button Manager
-Button Importing
I plan to have QA Wave 2.5 released this week and QA Wave 3 released over the next couple of weeks. After QA Wave 3 we will, after 2 arduous years, finally reach the full release of the new IonBC!
With that in mind there's a couple things to note with the new release:
1. The new version will not auto-update from the previous, everyone will need a fresh install.
2. The deprecated hotbar/button structures will not be translated in to the new structure, apologies for the inconvenience there as well!
Lastly, while the functionality of IonBC remains the same, there are a wide array of improvements that have fundamentally changed how certain aspects work. I will be redoing the documentation to mirror those changes as to avoid any confusion for new and returning users!
If anyone has any questions or concerns please feel free to reach out to me anytime!
Thanks again for all the support over the years, we're finally almost to the finish line on this new version and then we can move back in to community suggestions for expansion!
Last edited:
As of QA Wave 2.5.7 development of QA Wave 2 has concluded outside of standard maintenance.
It took a bit longer than expected and I'm sorry about that (what else is new)!
We are moving in to QA Wave 3 and, upon the conclusion of QA testing, we will finally have the full release of the new IonBC!
I appreciate everyone's patience and the work the QA team has put in to testing, looking forward to finally be in application expansion mode via your feedback in the coming months here!
It took a bit longer than expected and I'm sorry about that (what else is new)!
We are moving in to QA Wave 3 and, upon the conclusion of QA testing, we will finally have the full release of the new IonBC!
I appreciate everyone's patience and the work the QA team has put in to testing, looking forward to finally be in application expansion mode via your feedback in the coming months here!
- Status