Right on! Glad to hear you're enjoying it, if you have any issues don't hesitate to contact me!I ended up buying a license, spent about 30 mins replicating my hotkeynet setup and already works much better, will have a proper look into it when I'm not working, the /ibt thing is awesome and looking forward to checking out the event trigger bit too
-
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
craggyisland
Unwise Decision Designator
- Joined
- Apr 7, 2020
- RedCents
- 569¢
- Button to invite everyone and then have them press button to join.
- Button to set grouproles for everyone via /grouproles set NAME 1 (etc)
- Button to auto inventory stuff on cursor. It opens the inventory window, does a mouse click in the auto inventory box.
- this pairs nicely with my vex thal food/water clickies
- Button to have cleric or whatever class can, assist the driver character and cast Pacify whatever to make splitting easier for puller
- Of coarse the basic heal and nuke buttons
- Button to MoK my target
- Either buff buttons or do a Event Trigger where if you send a tell to a buff class they buff as see fits
- Sit/Stand button; this is just /sit because /sit is a toggle it sits or stands depending on how they currently are.
- You CAN click items inside bags without opening them. Using the /useitem 30 6 command. This targets the 8th bag and first spot in bag to trigger jboots in my case. You can target any bag/slot with this.
- See https://jaburt.com/eq/useitem.htm for examples. It works on gear to!
Ionis updated IonBC (TrueBox) with a new update entry:
GUI as Active Window bugfix
Read the rest of this update entry...
GUI as Active Window bugfix
Read the rest of this update entry...
Yep! It isn't tied to EverQuest and can be used outside of it. Just note that functionality outside of EverQuest hasn't been tested. So while it will work outside of EQ, I can't guarantee it will work in every and any application you try it for as I haven't tested it outside of EverQuest. But it has no dependencies, so you can use it without needing EQ running.
Ionis updated IonBC (TrueBox) with a new update entry:
Hide GUI on Window Change, VM/RDC/Parsec changes & Bug Fixes
Read the rest of this update entry...
Hide GUI on Window Change, VM/RDC/Parsec changes & Bug Fixes
Read the rest of this update entry...
Documentation update is coming, I am very ill right now and don't want to have to edit around my deep breathing and coughing all over the video. Once I'm well enough to not sound like death, the documentation update will continue!
I am still working on the overall maintenance and health of the program. In the meantime, if you run in to any issues, don't hesitate to contact me!
I am still working on the overall maintenance and health of the program. In the meantime, if you run in to any issues, don't hesitate to contact me!
Last edited:
The starter profile has been updated: https://www.redguides.com/community/resources/ionisprofile-for-ionbc-a-place-to-start.2548/
This is the profile that I, personally, use. I go a lot more in-depth about what each button does and it uses a lot more of the functionality that IonBC is capable of. As I continue to expand my own profile, this will be updated. Keep in mind I play on Mischief in GoD era, so you may need to fiddle with some things to get it exactly how you want it for your own server/era.
Let me know if you run in to any issues with the profile!
This is the profile that I, personally, use. I go a lot more in-depth about what each button does and it uses a lot more of the functionality that IonBC is capable of. As I continue to expand my own profile, this will be updated. Keep in mind I play on Mischief in GoD era, so you may need to fiddle with some things to get it exactly how you want it for your own server/era.
Let me know if you run in to any issues with the profile!
This was already posted in the official discord but reposting it here for all to see:
1.27 has entered development, figured I'd get this done before documentation so it's not missing anything.
1.27 will include:
-The ability for button clicks to interrupt any processing command. With this you can make sure that a button forces itself to go through instead of being ignored due to a processing command. This is important for when you need to react quickly and surely, like an emergency heal situation or raid event.
-Both triggers and buttons will now take a field for a stop casting keybind while interrupting is enabled. If enabled, this will interrupt all spell casting before starting the next processed command that way there's no overlap in commands when interrupting.
-I have changed how button clicks are handled in the backend. You can no longer press buttons with an action-type hardware input. User-generated buttons can now only be pressed by mouse clicks and user-set keybinds. In testing, this has fixed all Parsec/VM/RDC related issues but if you still run in to these problems please let me know.
-Input streams for live-key broadcasting and user-generated broadcasting have been separated. This means they can no longer happen concurrently. This was necessary to avoid overlaps while writing/reading so all messages can be processed appropriately and prevent hanging. This is also to prepare for the upcoming mouse broadcasting.
-Cast type handling for older operating systems, this won't be a visible change but it will stop a lot of random exceptions that older operating systems run in to due to deprecated .NET versions. These may not all be fixed, if you run in to any issues let me know.
-Removal of a bunch of unnecessary debug messages.
Among other things, if you have any suggestions of things you'd like added to 1.27 feel free to let me know. As always, if you run in to any issues don't hesitate to contact me. Thanks dudes!
1.27 has entered development, figured I'd get this done before documentation so it's not missing anything.
1.27 will include:
-The ability for button clicks to interrupt any processing command. With this you can make sure that a button forces itself to go through instead of being ignored due to a processing command. This is important for when you need to react quickly and surely, like an emergency heal situation or raid event.
-Both triggers and buttons will now take a field for a stop casting keybind while interrupting is enabled. If enabled, this will interrupt all spell casting before starting the next processed command that way there's no overlap in commands when interrupting.
-I have changed how button clicks are handled in the backend. You can no longer press buttons with an action-type hardware input. User-generated buttons can now only be pressed by mouse clicks and user-set keybinds. In testing, this has fixed all Parsec/VM/RDC related issues but if you still run in to these problems please let me know.
-Input streams for live-key broadcasting and user-generated broadcasting have been separated. This means they can no longer happen concurrently. This was necessary to avoid overlaps while writing/reading so all messages can be processed appropriately and prevent hanging. This is also to prepare for the upcoming mouse broadcasting.
-Cast type handling for older operating systems, this won't be a visible change but it will stop a lot of random exceptions that older operating systems run in to due to deprecated .NET versions. These may not all be fixed, if you run in to any issues let me know.
-Removal of a bunch of unnecessary debug messages.
Among other things, if you have any suggestions of things you'd like added to 1.27 feel free to let me know. As always, if you run in to any issues don't hesitate to contact me. Thanks dudes!
Last edited:
1.27 is well underway, experimental will be coming to the Discord here soon! Sorry it took me a little longer than usual, I've been working on a local version as well as an unstable version with some experimental functionality simultaneously.
Expect an official release sometime in the next few days!
Expect an official release sometime in the next few days!
1.27 has entered experimental and is available on our Discord to license holders only!
Here's a peek at the patch notes:
[CODE title="1.27 Patch Notes"]New Stuff:
-Buttons now have the option to interrupt, if a button is set to interrupt it will stop all currently processing commands and immediately process the command of the associated button.
-Buttons now have a wait field associated with the new interrupt functionality. If greater than 0, the server will wait that amount of milliseconds before executing the command AFTER interrupting.
-You can now set triggers/buttons to stop casting when interrupting is enabled! There's a new associated checkbox as well as a keybind textbox for your stop cast keybind (default is lshift+s in-game).
-You can now freely edit the repeater & cooldown overlays. By clicking the CD button in the Create/Edit button window, you can fully customize the opacity, color, etc of the overlay.
Changes:
-Changed how we handle button clicks, we now preview the key iterating over the button and, if it's not by keybind or mouse click, it is ignored. This should solve all issues relating to Parsec, VMs and other RDC-type software. If these issues persist, please contact me.
-Separated the listener for live-key and normal message broadcasting. Now, while broadcasting, normal message passes will be ignored. This change was necessary for preventing some unintended functionality causing issues with some users.
-You can now preview repeater & cooldown functionality by clicking on the preview button while repeater or cooldown is enabled.
-Removed a lot of debug message spam that was deprecated.
-The speed of seeking for triggers has been GREATLY increased from 5000 lines a second (5/ms) to 100000 lines a second (100/ms). This is due to some reports of missing triggers on raids where line spam is exceptionally high. This may need to be increased even greater still, if you run in to read issues please contact me.
-The seek method for triggers has been separated to it's own background thread to avoid performance hits.
-Import and Export menus now include the new interrupt, wait and stop casting data.
-Changed all overlay, trigger & button data to have the new associated data structures, this should append automatically but if you have trouble loading your profile please contact me.
Bug Fixes:
-Fixed a bug that caused some older operating systems (Win 7 and before) to throw an error when casting to visual children of the client/server window.
-Fixed a bug where broadcasting would sometimes get out of sync if the user flip-flopped connectivity without a proper disconnect.
-Fixed a bug where, when quick duplicating a button, the cooldown option would always be set to true.
-Fixed a bug where the activated hotbar would sometimes become unresponsive and rapidly flash if a GUI was loaded while Hide GUI on Window Change was enabled.
-Fixed a bug where, when pressing a generic button with no in-line targeting that targeted "all", the host wouldn't process the command.
-Fixed a bug where, when attempting to set a keybind to LCTRL/RCTRL + V, it would paste the clipboard data to the textbox resulting in unwanted assignment results.[/CODE]
If all goes well with testing, expect a go-live build sometime soon.
Here's a peek at the patch notes:
[CODE title="1.27 Patch Notes"]New Stuff:
-Buttons now have the option to interrupt, if a button is set to interrupt it will stop all currently processing commands and immediately process the command of the associated button.
-Buttons now have a wait field associated with the new interrupt functionality. If greater than 0, the server will wait that amount of milliseconds before executing the command AFTER interrupting.
-You can now set triggers/buttons to stop casting when interrupting is enabled! There's a new associated checkbox as well as a keybind textbox for your stop cast keybind (default is lshift+s in-game).
-You can now freely edit the repeater & cooldown overlays. By clicking the CD button in the Create/Edit button window, you can fully customize the opacity, color, etc of the overlay.
Changes:
-Changed how we handle button clicks, we now preview the key iterating over the button and, if it's not by keybind or mouse click, it is ignored. This should solve all issues relating to Parsec, VMs and other RDC-type software. If these issues persist, please contact me.
-Separated the listener for live-key and normal message broadcasting. Now, while broadcasting, normal message passes will be ignored. This change was necessary for preventing some unintended functionality causing issues with some users.
-You can now preview repeater & cooldown functionality by clicking on the preview button while repeater or cooldown is enabled.
-Removed a lot of debug message spam that was deprecated.
-The speed of seeking for triggers has been GREATLY increased from 5000 lines a second (5/ms) to 100000 lines a second (100/ms). This is due to some reports of missing triggers on raids where line spam is exceptionally high. This may need to be increased even greater still, if you run in to read issues please contact me.
-The seek method for triggers has been separated to it's own background thread to avoid performance hits.
-Import and Export menus now include the new interrupt, wait and stop casting data.
-Changed all overlay, trigger & button data to have the new associated data structures, this should append automatically but if you have trouble loading your profile please contact me.
Bug Fixes:
-Fixed a bug that caused some older operating systems (Win 7 and before) to throw an error when casting to visual children of the client/server window.
-Fixed a bug where broadcasting would sometimes get out of sync if the user flip-flopped connectivity without a proper disconnect.
-Fixed a bug where, when quick duplicating a button, the cooldown option would always be set to true.
-Fixed a bug where the activated hotbar would sometimes become unresponsive and rapidly flash if a GUI was loaded while Hide GUI on Window Change was enabled.
-Fixed a bug where, when pressing a generic button with no in-line targeting that targeted "all", the host wouldn't process the command.
-Fixed a bug where, when attempting to set a keybind to LCTRL/RCTRL + V, it would paste the clipboard data to the textbox resulting in unwanted assignment results.[/CODE]
If all goes well with testing, expect a go-live build sometime soon.
Last edited:
This usually means that the token used for validation has expired and you need to grab a new token, this would make sense if it's been 2 weeks since the last use.
Clicking Yes will start the validation process over and should fix the issue, if it doesn't, let me know.
Ionis updated IonBC (TrueBox) with a new update entry:
IonBC 1.27: Overlay Customization, Button Interrupts, Trigger/Button stop casting, Bug Fixes & more!
Read the rest of this update entry...
IonBC 1.27: Overlay Customization, Button Interrupts, Trigger/Button stop casting, Bug Fixes & more!
Read the rest of this update entry...
1.27 is available for download!
Thanks to everyone in the Discord for helping me bugfix some of the issues that were happening with the new update.
Next is the documentation, it's coming I promise. If you run in to any issues with this build don't hesitate to contact me!
Thanks to everyone in the Discord for helping me bugfix some of the issues that were happening with the new update.
Next is the documentation, it's coming I promise. If you run in to any issues with this build don't hesitate to contact me!
Ionis updated IonBC (TrueBox) with a new update entry:
/Click on Triggers Bugfix
Read the rest of this update entry...
/Click on Triggers Bugfix
Read the rest of this update entry...
Ionis updated IonBC (TrueBox) with a new update entry:
Trigger case change, version display & trigger interval bugfix
Read the rest of this update entry...
Trigger case change, version display & trigger interval bugfix
Read the rest of this update entry...
Ionis updated IonBC (TrueBox) with a new update entry:
Live-key Broadcasting bugfix
Read the rest of this update entry...
Live-key Broadcasting bugfix
Read the rest of this update entry...
Just a quick update here, the documentation is moving along! I'm really taking my time with it just to make sure we cover not only everything the program has inherently but every single question I've ever been asked.
Expect a new showcase/tutorial video sometime within the next 2 weeks with the text documentation following.
With that being said, I am opening the floor (yet again) to any suggestions folks have for new functionality!
Any suggestions will be added in a 1.28 update AFTER the documentation update. I have a few already, but not nearly enough to make up a full update. So feel free to PM me whatever you feel is missing from the experience while using IonBC!
I appreciate all of the support over the past couple months, the community has been absolutely fantastic with reporting bugs and helping with debugging as development moves forward. If you run in to any issues with IonBC, please don't hesitate to contact me and I will get back to you right away so we can sort out the issue and fix it!
Thanks again folks, it has been a blast developing this for everyone and I look forward to it's continued progression.
Expect a new showcase/tutorial video sometime within the next 2 weeks with the text documentation following.
With that being said, I am opening the floor (yet again) to any suggestions folks have for new functionality!
Any suggestions will be added in a 1.28 update AFTER the documentation update. I have a few already, but not nearly enough to make up a full update. So feel free to PM me whatever you feel is missing from the experience while using IonBC!
I appreciate all of the support over the past couple months, the community has been absolutely fantastic with reporting bugs and helping with debugging as development moves forward. If you run in to any issues with IonBC, please don't hesitate to contact me and I will get back to you right away so we can sort out the issue and fix it!
Thanks again folks, it has been a blast developing this for everyone and I look forward to it's continued progression.
I am aware of the issue where seeking for triggers is not nearly as fast as originally intended.
This has been solved but is currently being tested in multiple different raid environments to be entirely certain we have a fully working solution.
I appreciate the patience on this, expect an update somewhere in the next week assuming all tests come back green!
If you'd like a copy of the experimental version, feel free to contact me.
This has been solved but is currently being tested in multiple different raid environments to be entirely certain we have a fully working solution.
I appreciate the patience on this, expect an update somewhere in the next week assuming all tests come back green!
If you'd like a copy of the experimental version, feel free to contact me.
1.28 enters development this week, I got a huge influx of suggestions so I'd like to get this out before documentation. I have the documentation about half done, so I'm going to put it on hold until 1.28 is done just so we can get all functionality in there. Expect a 1.28 experimental here in the following weeks.
1.28 will include:
-New clients tab on the server window for managing connected clients.
-New import button for triggers (client and host side) for importing triggers from host to client or vice versa.
-Toolbar automatically corrects itself based on it's location on your screen so it's never off screen.
-Changes to the algorithm used for triggers to make them much, much quicker and more accurate. (This is already in testing and may come out for 1.27.5)
as well as more.
I'll keep everyone posted as development continues!
1.28 will include:
-New clients tab on the server window for managing connected clients.
-New import button for triggers (client and host side) for importing triggers from host to client or vice versa.
-Toolbar automatically corrects itself based on it's location on your screen so it's never off screen.
-Changes to the algorithm used for triggers to make them much, much quicker and more accurate. (This is already in testing and may come out for 1.27.5)
as well as more.
I'll keep everyone posted as development continues!
Last edited:
1.28 has entered experimental!
Here's a peek at the patch notes:
[CODE title="1.28"]New Stuff:
-You can now manage your connected clients via the Clients tab in the server window! This allows you to see your clients ping, connection quality and last successfully processed message!
-New import button for triggers (client and host side) for importing triggers from host to client or vice versa.
Changes:
-Toolbar automatically corrects itself based on it's location on your screen so it's never off screen.
-Seeking for triggers has been entirely reworked, we now seek 600-800x faster and read 380x more lines per second. This may change even more as testing continues.
-New detection for Multiplicity and Input Director specifically, the user is now notified each time they launch that these do not play well with IonBC. This is attached to the same DSTA as VMs/Parsec.
Bug Fixes:
-Fixed a bug where the DSTA for deleting buttons wasn't properly assigning.
-Fixed a bug where the program wasn't properly detecting VirtualBox, Parsec, Multiplicity or Input Director for the warning relating to these applications.
-Fixed a bug that allowed for the trigger section of triggers to be empty.
-Fixed a bug that could occasionally cause buttons to simulate presses based off of certain keystrokes.
-Fixed a bug from a reverted change that caused interrupts on button presses to not be processed by clients appropriately.[/CODE]
If testing goes well, expect a live version sometime post-Thursday!
Here's a peek at the patch notes:
[CODE title="1.28"]New Stuff:
-You can now manage your connected clients via the Clients tab in the server window! This allows you to see your clients ping, connection quality and last successfully processed message!
-New import button for triggers (client and host side) for importing triggers from host to client or vice versa.
Changes:
-Toolbar automatically corrects itself based on it's location on your screen so it's never off screen.
-Seeking for triggers has been entirely reworked, we now seek 600-800x faster and read 380x more lines per second. This may change even more as testing continues.
-New detection for Multiplicity and Input Director specifically, the user is now notified each time they launch that these do not play well with IonBC. This is attached to the same DSTA as VMs/Parsec.
Bug Fixes:
-Fixed a bug where the DSTA for deleting buttons wasn't properly assigning.
-Fixed a bug where the program wasn't properly detecting VirtualBox, Parsec, Multiplicity or Input Director for the warning relating to these applications.
-Fixed a bug that allowed for the trigger section of triggers to be empty.
-Fixed a bug that could occasionally cause buttons to simulate presses based off of certain keystrokes.
-Fixed a bug from a reverted change that caused interrupts on button presses to not be processed by clients appropriately.[/CODE]
If testing goes well, expect a live version sometime post-Thursday!
Ionis updated IonBC (TrueBox) with a new update entry:
IonBC 1.28: Client Handler, Trigger Importing, Trigger Seek Rework, Bug Fixes & more!
Read the rest of this update entry...
IonBC 1.28: Client Handler, Trigger Importing, Trigger Seek Rework, Bug Fixes & more!
Read the rest of this update entry...
1.28 is live!
Really quite proud of how IonBC is starting to shape up with this and upcoming updates. I am very grateful for the communities feedback that continues to see this application grow and become better!
Moving forward, we have a build coming up here that will fix certificate issues causing Window's Defender to raise false flags and the documentation update. I am still taking suggestions and fixing bugs as they come, but there will not be another full update until the documentation is completed. Only bug fixes and minor tweaks here and there as needed.
As always, If you ever have an issue, concern or suggestion, please don't hesitate to contact me.
Really quite proud of how IonBC is starting to shape up with this and upcoming updates. I am very grateful for the communities feedback that continues to see this application grow and become better!
Moving forward, we have a build coming up here that will fix certificate issues causing Window's Defender to raise false flags and the documentation update. I am still taking suggestions and fixing bugs as they come, but there will not be another full update until the documentation is completed. Only bug fixes and minor tweaks here and there as needed.
As always, If you ever have an issue, concern or suggestion, please don't hesitate to contact me.
Last edited:
You can indeed! When you create a button, in the options tab, you can assign a keybind to the generated button!
I am in the middle of redoing the documentation, if you have any questions feel free to ask.
Goose_Herder
Active member
- Joined
- May 7, 2020
- RedCents
- 499¢
Would it be possible to get an auto-updater? Would be pretty sweet!
I was thinking of doing something like this, I'll work on it for 1.29 alongside some of the other stuff I have been suggested that didn't fit in 1.28.
It's definitely possible!
Ionis updated IonBC (TrueBox) with a new update entry:
Topmost, trigger, pause changes and bugfixes
Read the rest of this update entry...
Topmost, trigger, pause changes and bugfixes
Read the rest of this update entry...
Ionis updated IonBC (TrueBox) with a new update entry:
Broadcasting toggle changes & bugfixes
Read the rest of this update entry...
Broadcasting toggle changes & bugfixes
Read the rest of this update entry...
Ionis updated IonBC (TrueBox) with a new update entry:
IonBC 1.28.4: Huge CPU Usage Fix
Read the rest of this update entry...
IonBC 1.28.4: Huge CPU Usage Fix
Read the rest of this update entry...
Sorry about the three back-to-back updates today folks, busy day!
For those of you who aren't apart of the discord here's a little peek in to what's upcoming:
[CODE title="Discord Update"]Just a quick update, the documentation is moving along but I also have some plans for 1.29!
For 1.29 I plan to include:
-Multi-service support (running servers off of multiple IP/Ports)
-Auto-updater
-Begin testing the waters with logic surrounding resource based responses (think heal when low HP, med when low Mana)
As well as some usual tweaks and changes based on feedback. 1.29 won't see a release until the conclusion of documentation but folks involved will get test builds and, if all goes well, there will be an experimental to follow.
As always, if anyone has any suggestions, problems or concerns don't hesitate to contact me![/CODE]
If you run in to any issues, please don't hesitate to contact me!
For those of you who aren't apart of the discord here's a little peek in to what's upcoming:
[CODE title="Discord Update"]Just a quick update, the documentation is moving along but I also have some plans for 1.29!
For 1.29 I plan to include:
-Multi-service support (running servers off of multiple IP/Ports)
-Auto-updater
-Begin testing the waters with logic surrounding resource based responses (think heal when low HP, med when low Mana)
As well as some usual tweaks and changes based on feedback. 1.29 won't see a release until the conclusion of documentation but folks involved will get test builds and, if all goes well, there will be an experimental to follow.
As always, if anyone has any suggestions, problems or concerns don't hesitate to contact me![/CODE]
If you run in to any issues, please don't hesitate to contact me!
Goose_Herder
Active member
- Joined
- May 7, 2020
- RedCents
- 499¢
auto updater gonna be awesome
I should really test this out on my steamdeck box, maybe once I've gotten my dudes to 50 on Vaniki
I should really test this out on my steamdeck box, maybe once I've gotten my dudes to 50 on Vaniki
Ionis updated IonBC (TrueBox) with a new update entry:
1.28.5: BC changes and more bugfixes
Read the rest of this update entry...
1.28.5: BC changes and more bugfixes
Read the rest of this update entry...
Could you throw me a PM with the profile and what exactly is going on? Can you not enter text in to the Content textbox in the Edit/Create Button window?
If this didn't resolve itself, throw me a PM with what's happening so I can check it out as I can't seem to recreate this on my end!
This is going to be a bit of a long post, so stay with me if ya can! 
When I started IonBC I really wanted to create a easy to use, top-level option for folks that could work as an alternative to programs like AHK, HKN and log readers.
Since then, it has turned in to something so much more than I originally envisioned. The community feedback over the past half a year has been stellar and we wouldn't have come as far as we did with this application without everyone's help.
With that being said, I am refunding every single license holder and releasing IonBC for free for a determinant amount of time, let's get in to why:
I really feel like, when I originally released IonBC, it would be a quick one-off that a niche amount of folks would use and I'd be done with it. I didn't expect the community to be so driven and happy with the application.
This is what drove me to continue the community updates for everyone, to give folks what they wanted out of IonBC and help alleviate the stress of boxing on Truebox servers.
With that being said, with a lot of functionality comes a lot of problems. The level of IonBC's interactivity is so high that there's a whole mess of issues that tend to weed there way in to normal functionality. I don't feel comfortable taking money from folks on an application that I would still consider to be in it's beta phase at this current time.
So I'm releasing it for free until I feel it is sufficiently developed enough that everyone can get what they want out of it while running in to minimal, if any, issues!
On top of this, releasing for free will bring a whole slew of new users around to help with debugging and bug catching so we can ever increase the quality of IonBC!
Refunds will be issued through my paypal account, whatever payment method you used to pay for IonBC is what it will be charged back to. If you don't receive your refund within the week, contact me with the information you paid with in-case I missed you!
Just to make sure it's understood, this isn't the end of development nor is it the end of the licensing service. The licensing logic will remain in place and development will continue as always so if you have any issues please don't hesitate to contact me.
This is for two reasons:
1. I want to really up the quality of experience before charging anyone.
2. Outreach to a wider audience for a broader spectrum of testing and community.
I know a lot of folks have reported that they have no issues with the application, but with us adding so much logic to it I feel it's still more of a beta that should be open rather than a finished application that should be behind a subscription service. At this current time, anyways!
I am still here working away as always, if there's any problems, just holler.
When I started IonBC I really wanted to create a easy to use, top-level option for folks that could work as an alternative to programs like AHK, HKN and log readers.
Since then, it has turned in to something so much more than I originally envisioned. The community feedback over the past half a year has been stellar and we wouldn't have come as far as we did with this application without everyone's help.
With that being said, I am refunding every single license holder and releasing IonBC for free for a determinant amount of time, let's get in to why:
I really feel like, when I originally released IonBC, it would be a quick one-off that a niche amount of folks would use and I'd be done with it. I didn't expect the community to be so driven and happy with the application.
This is what drove me to continue the community updates for everyone, to give folks what they wanted out of IonBC and help alleviate the stress of boxing on Truebox servers.
With that being said, with a lot of functionality comes a lot of problems. The level of IonBC's interactivity is so high that there's a whole mess of issues that tend to weed there way in to normal functionality. I don't feel comfortable taking money from folks on an application that I would still consider to be in it's beta phase at this current time.
So I'm releasing it for free until I feel it is sufficiently developed enough that everyone can get what they want out of it while running in to minimal, if any, issues!
On top of this, releasing for free will bring a whole slew of new users around to help with debugging and bug catching so we can ever increase the quality of IonBC!
Refunds will be issued through my paypal account, whatever payment method you used to pay for IonBC is what it will be charged back to. If you don't receive your refund within the week, contact me with the information you paid with in-case I missed you!
Just to make sure it's understood, this isn't the end of development nor is it the end of the licensing service. The licensing logic will remain in place and development will continue as always so if you have any issues please don't hesitate to contact me.
This is for two reasons:
1. I want to really up the quality of experience before charging anyone.
2. Outreach to a wider audience for a broader spectrum of testing and community.
I know a lot of folks have reported that they have no issues with the application, but with us adding so much logic to it I feel it's still more of a beta that should be open rather than a finished application that should be behind a subscription service. At this current time, anyways!
I am still here working away as always, if there's any problems, just holler.
I am ok if you keep the payment already made as an appreciation of the great work you already done, and suspend subscription fee from now on as you wish until you see fit to start charging again. It really helps in true boxing and not violating EQ's playing rules.
One suggestion: future subscription $10-$30 per year ?
Thanks. Keep on the great work.
One suggestion: future subscription $10-$30 per year ?
Thanks. Keep on the great work.
I definitely considered suspending the licenses then just starting them up again, but it just didn't sit right with me. Maybe I am just being silly, but it's what I decided felt most right to me.
We can definitely review something like a yearly subscription once the application is released! I may even leave the price point up to the community with a poll or something once I'm comfortable with where it's at.
Not a problem, if you ever run in to any issues don't hesitate to contact me!
