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

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

💾Software IonBC Legacy READ OVERVIEW 0.29.5

No permission to download
Join us with Level 2 access RedCents
Overview Instructions F.A.Q. Updates (63) Reviews (9) History Discussion
There's an issue with stripping the price from the resource I'm running in to atm, Red's been notified, changed the price to an egregious amount so folks can't purchase it until it's resolved to avoid me having to throw refunds around. :)

Will be fixed soon, sorry about that folks!
 
1656241719807.png

i hope you dont think me a cheap cake .. but 10k appear a little over board :D

Edit: didnt see your post above before i put this up hrhr
 
Last edited:
Ionis said:
There's an issue with stripping the price from the resource I'm running in to atm, Red's been notified, changed the price to an egregious amount so folks can't purchase it until it's resolved to avoid me having to throw refunds around. :)

Will be fixed soon, sorry about that folks!
Click to expand...

But i got the time to set up such things only on Sundays. Gimme :(
 
Ionis said:
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!
Click to expand...
If you ask me. Set at least up a donation possibility.

I may feel as bad for using already well functioned beta software for free as you feel for charging for a beta version.
 
Redbot said:
Price removed per request by @Ionis. You're freeeee
Click to expand...
Huzzah! If anyone has any issues, don't hesitate to contact me!

Robahn said:
If you ask me. Set at least up a donation possibility.

I may feel as bad for using already well functioned beta software for free as you feel for charging for a beta version.
Click to expand...
No need to feel bad! It may be a little selfish, but I chose to do this to get the IonBC end-user experience as clean as it possibly can be! Just using the program and letting me know if you have any problems or suggestions is payment enough. :)
 
Ionis updated IonBC (TrueBox) with a new update entry:

0.28.6: Y interpolation, hotbar focus changes, bugfixes & more!

Changes:
-The 1 in the version number has been changed to 0, to reflect the beta status.
-Toolbar now auto-interpolates on the Y axis when it's outside of the screen's bounds.
-You can no longer send commands if a hotbar is in focus, a message will be relayed to the server window upon attempting to do so.

Bug Fixes:
-Fixed a bug where, when the EverQuest window handle would occasionally change, hotbars would stop working if Toggle GUI on...
Click to expand...

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

0.28.7: Corrupt Profile Checking & Bugfixes

**Note: You should only have to update your host-side.

New Stuff:
-Created a full routine for checking over, validating and repairing every existing profile upon server window startup. This should automatically check, repair and save all issues that could be corrupting a profile but if you notice you can't load or there's something going on that's a bit funky, don't hesitate to contact me.

Bug...
Click to expand...

Read the rest of this update entry...
 
I would like to be able to create a hotkey to deal with movement and levitation. I figured I could do this by doing a /keypress pgdn or /keypress pgup , but it does not last long enough for the game to actually look down. I tried adjusting the key interval but that didn't seem to help. Any advice on how I can do this? or any advice on how to create a key that will make my characters look up or down to deal with levitation issues? also would be nice to have a stop follow command, perhaps done the same way but with the /keypress S
 
Ionis updated IonBC (TrueBox) with a new update entry:

0.28.7.2: Live-key BC disabled & bugfixes

**Note: You should only have to update your host-side. Unless you have yet to update to 0.28.6, then you need to replace both host AND client-side.

Changes:
-Disabled Live-Key broadcasting temporarily so it is no longer usable. There is an issue with client stream being disposed when the stream load reaches a certain amount so I'm reworking this functionality. To avoid getting slammed with error...
Click to expand...

Read the rest of this update entry...
 
aikidokun said:
I would like to be able to create a hotkey to deal with movement and levitation. I figured I could do this by doing a /keypress pgdn or /keypress pgup , but it does not last long enough for the game to actually look down. I tried adjusting the key interval but that didn't seem to help. Any advice on how I can do this? or any advice on how to create a key that will make my characters look up or down to deal with levitation issues? also would be nice to have a stop follow command, perhaps done the same way but with the /keypress S
Click to expand...
This is accomplishable with the live-key broadcasting feature, but it has been temporarily disabled due to some issues that were causing unwarranted client stream disposals. Once it's re-released, it will solve this issue for you, but it may be beneficial for us to also add a /keyhold command.

Something like:
/keyhold keyshere|timeheldhere

That way you could do something like:
/keyhold s|3
Click to expand...

Which would hold the S key for 3 seconds. This would also solve the issue and honestly isn't a terrible idea for a command. I'll throw it on the docket for 0.29!
 
@Ionis you're cranking out functions, features, and updates! Nice job dude
 
Sic said:
@Ionis you're cranking out functions, features, and updates! Nice job dude
Click to expand...
Thanks man, I really appreciate it. :) Wouldn't be nearly as fleshed out if it weren't for the community! A lot of great folks that have been very responsive with feedback and features, I've been pretty blown away by everyone's love of the program and have been stoked that I've been able to continue expanding it so much.
 
Ionis updated IonBC (TrueBox) with a new update entry:

0.28.7.3: Changes to foreground handling & bugfixes

**Note: You should only have to update your host-side. Unless you have yet to update to 0.28.6, then you need to replace both host AND client-side.

Changes:
-Changed the foreground window check to only check for commands being processed on the host-side, it will no longer reject commands being sent to any clients.

Bug Fixes:
-Fixed a bug that caused the hotbar to sometimes gain...
Click to expand...

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

0.28.7.4: Pause changes & Relay bugfix

**Note: This is a FULL update, you'll need to replace both client AND host-side versions.

Changes:
-Changed how we determine the variable for pausing, it will now take any numerical level of determinant in any format.

Bug Fixes:
-Fixed a bug that was causing an incorrect string to be thrown to the relay when pausing on both host and client-side.

Thanks to...
Click to expand...

Read the rest of this update entry...
 
I am confused,

is this something that is used with MQ2 or its a separate entity on its own ?

or can it be used on its own ?
 
I've been working away at some fancy obfuscation stuff and fixing issues as they come, but in other news, a small batch feature update will be coming soon, 0.28.8!

Here's a quick peek at the patch notes:
[CODE title="0.28.8"]New Stuff:
(Done)-You can now host up to 3 services at once from a single host machine! Clicking the + button located to the right of the port textbox creates new IP and port fields for more services!
-You can now enable command stacking in the Options tab of the server window! This changes how we handle our command processing logic, instead of ignoring overlapping commands the target will receive the command, store it and process them in a first in first out priority!

Changes:
-Interval 0 now immediately processes the command without typing each individual key.

Bug Fixes:
(Done)-Fixed a bug that caused triggers to ignore processing commands regardless of if they were set to interrupt or not.[/CODE]

I'm sure there will be more bug fixes as we go, but this is where we're at for now! I'd expect this sometime in the next week or two as I'm reworking a good portion of how we handle client/server communication to get this working cleanly.

As always, if you find yourself running in to any trouble don't hesitate to contact me!
 
What is the benefit of hosting up to 3 services from a single host? is there a limitation on clients from a single host service? e.g. 12 box max, 3 services would enable 36 boxes
 
ssydmonk said:
What is the benefit of hosting up to 3 services from a single host? is there a limitation on clients from a single host service? e.g. 12 box max, 3 services would enable 36 boxes
Click to expand...
There is no limitation in place, you can run as many clients from one service as you would like.

There was a user who requested multi-service handling due to their team being hosted across multiple networks via cloud machines. A portion of their toons were connected to their local network, but the cloud machines were on an entirely different network and needed to connect through a non-local IP due to the use of VPNs and other software.

This is a pretty niche feature that won't be utilized outside of these unlikely clauses, but it is a feature that was requested of me none-the-less. :)
 
Ionis said:
This is accomplishable with the live-key broadcasting feature, but it has been temporarily disabled due to some issues that were causing unwarranted client stream disposals. Once it's re-released, it will solve this issue for you, but it may be beneficial for us to also add a /keyhold command.

Something like:
/keyhold keyshere|timeheldhere

That way you could do something like:


Which would hold the S key for 3 seconds. This would also solve the issue and honestly isn't a terrible idea for a command. I'll throw it on the docket for 0.29!
Click to expand...
Yes exactly, I tried to accomplish this with the key-interval but it did not work. Would love to see a hold for X amount of time as you suggested.
 
aikidokun said:
Yes exactly, I tried to accomplish this with the key-interval but it did not work. Would love to see a hold for X amount of time as you suggested.
Click to expand...
It has been added to the docket for 0.29 but it seems like it's something folks really want, I'll see if I can implement it for the upcoming 0.28.8 patch. :)
 
0.28.8 has finished being developed and has now been passed to designated end-users for testing! If all goes well, expect a release within the next week sometime.

Here's a peek at the current patch notes:

[CODE title="0.28.8"]New Stuff:
(Done)-You can now host up to 3 services at once from a single host machine! Clicking the + button located to the right of the port textbox creates new IP and port fields for more services!
(In Testing)-You can now enable command stacking in the Options tab of the server window! This changes how we handle our command processing logic, instead of ignoring overlapping commands the target will receive the command, store it and process them in a first in first out priority!
(In Testing)-You can now use the /keyhold command (syntax: /keyhold key|milliseconds) to broadcast a held key across machines!

Changes:
(In Testing)-Interval 0 now immediately processes the command without typing each individual key.
(Done)-Reworked our exception catching to utilize new symbols and export more information to associated debug files.
(Done)-Updated our debugging symbols to cover more issues and be more tailored towards exactly what we're looking for in relation to exceptions.
(Done)-Changed our heartbeat method to contain a disposal for clients that are forcibly disconnected.
(Done)-Changed IBT commands so they can now handle delimiters that aren't associated with the initial data structure.

Bug Fixes:
(Done)-Fixed a bug that caused triggers to ignore processing commands regardless of if they were set to interrupt or not.
(Done)-Fixed a bug that would cause IonBC to crash when tabbing to the clients tab after disconnecting and reconnecting a client that had a pre-existing handle.
(Done)-Fixed a bug that was preventing specific General Server settings from being written properly when launching a client that didn't have those settings appended to the general settings file.
(Done)-Fixed a bug that was causing IBT commands to sometimes be ignored due to the stream not being able to keep up with the write speed.
(Done)-Fixed a bug that would sometimes cause delimiters to be ignored due to an over-split.
(Done)-Fixed a bug where the data structure for keybinding wouldn't save properly if the server had hit an exception causing any keybind to become every keybind.[/CODE]

Excited to release this one, a lot of great stuff in here! :) As always, let me know if you run in to any issues!
 
Last edited:
Just a quick update:

0.28.8 testing is going well but there has been a couple of exposed issues that we've been tracking down so it's taking a little longer than expected. Depending on how Iong it takes I may just group this together with what I have planned for 0.29 but I'll keep everyone posted!

Thanks for the patience folks!
 
It's been a few days since we've run in to any outstanding issues with 0.28.8, giving it a couple more days and if nothing goes wrong with the experimental it will be pushed to live by Sunday/Monday!

Here's the current "finalized" patch notes, these could change depending on current tests:
[CODE title="0.28.8"]New Stuff:
(Done)-You can now host up to 3 services at once from a single host machine! Clicking the + button located to the right of the port textbox creates new IP and port fields for more services!
(Done)-You can now enable command stacking in the Options tab of the server window! This changes how we handle our command processing logic, instead of ignoring overlapping commands the target will receive the command, store it and process them in a first in first out priority!
(Done)-You can now use the /keyhold command (syntax: /keyhold key|milliseconds) to broadcast a held key across machines!

Changes:
(Done)-Interval 0 now immediately processes the command without typing each individual key.
(Done)-Reworked our exception catching to utilize new symbols and export more information to associated debug files.
(Done)-Updated our debugging symbols to cover more issues and be more tailored towards exactly what we're looking for in relation to exceptions.
(Done)-Changed our heartbeat method to contain a disposal for clients that are forcibly disconnected.
(Done)-Changed IBT commands so they can now handle delimiters that aren't associated with the initial data structure.
(Done)-Removed the requirement of setting a process for saving a new process data structure in the process controller.

Bug Fixes:
(Done)-Fixed a bug that caused triggers to ignore processing commands regardless of if they were set to interrupt or not.
(Done)-Fixed a bug that would cause IonBC to crash when tabbing to the clients tab after disconnecting and reconnecting a client that had a pre-existing handle.
(Done)-Fixed a bug that was preventing specific General Server settings from being written properly when launching a client that didn't have those settings appended to the general settings file.
(Done)-Fixed a bug that was causing IBT commands to sometimes be ignored due to the stream not being able to keep up with the write speed.
(Done)-Fixed a bug that would sometimes cause delimiters to be ignored due to an over-split.
(Done)-Fixed a bug where the data structure for keybinding wouldn't save properly if the server had hit an exception causing any keybind to become every keybind.
(Done)-Fixed a bug where the timer that iterates over our triggers was disposing of it itself in an unintended way.
(Done)-Fixed a bug that caused clients to not receive messages when clicking a button that was using a cooldown and a comma delimiter.
(Done)-Fixed a bug causing the tab to keybind to fire over the associated processes every key up call if the original key composition equaled an existing keybind.[/CODE]

I know it's been a long one, but there was a whole slew of logic changes here and I really wanted to make sure that everything came up as clean as I could possibly get it! Thanks for the patience everyone, if all goes well we will see a release in the next couple days here!
 
Last edited:
Ionis updated IonBC (TrueBox) with a new update entry:

0.28.8: Keyhold, multi-service handling, command stacking, bugfixes & more!

**Note: This is a FULL update, you'll need to replace both client AND host-side versions.

New Stuff:
-You can now host up to 3 services at once from a single host machine! Clicking the + button located to the right of the port textbox creates new IP and port fields for more services!
-You can now enable command stacking in the Options tab of the server window! This changes how we handle our command...
Click to expand...

Read the rest of this update entry...
 
0.28.8 is out!

I have a lot of great stuff lined up for 0.29 given community feedback, but I'm going to give time for folks to find any kinks with 0.28 before development will move forward on 0.29.

I'll keep everyone posted! Let me know if you have any issues with the patch!
 
Can you explain command stacking more?
Example? What was old behavior? What is new behavior?

Interval=0?
So the command is just pasted basically not typed out key by key?
 
LamahHerder said:
Can you explain command stacking more?
Example? What was old behavior? What is new behavior?
Click to expand...
Old behavior remains the same, new behavior handles multiple messages at once (without ignoring) but handles them in the order of arrival. Old behavior is default, new behavior is togglable via the options tab of the Server Window.

Stack looks like this: 1st In -> 2nd In -> 3rd In -> 1st Out -> 2nd Out -> 3rd Out etc.

So instead of ignoring duplicate or overlapping messages, they are queued and processed in order of arrival.
LamahHerder said:
Interval=0?
So the command is just pasted basically not typed out key by key?
Click to expand...
Correct, assuming there isn't an application holding exclusive control over clipboard properties. If there is an issue with clipboard exclusivity and you've downloaded all of the tweaks I've pushed today, it will just process the message as if it has a 05-10 interval as opposed to utilizing the clipboard (error message is still relayed).
 
Last edited:
Ionis said:
Old behavior remains the same, new behavior handles multiple messages at once (without ignoring) but handles them in the order of arrival. Old behavior is default, new behavior is togglable via the options tab of the Server Window.

Stack looks like this: 1st In -> 2nd In -> 3rd In -> 1st Out -> 2nd Out -> 3rd Out etc.

So instead of ignoring duplicate or overlapping messages, they are queued and processed in order of arrival.
Click to expand...
I thought old behavior was FIFO, which is why im confused.
What is old behavior if new behavior is FIFO
 
LamahHerder said:
I thought old behavior was FIFO, which is why im confused.
What is old behavior if new behavior is FIFO
Click to expand...
They're both first in first out, the first message received is the first message processed regardless of settings. The receiver (host OR client) always processes the oldest message first, all command stacking does is flip a bool that allows for simultaneous commands to be queued receiver-side instead of ignored by switching the function that data is passed to on read, it is quite simply:

[CODE lang="csharp" title="Receiver Side Command Handling"]if (cmdStcking)
{
StandardStackPass(cStream, msgRcv, ignoreAllFlags, isGetMPos); //If command stacking enabled, pass the command to the stack for handling.
}
else
{
StandardPass(cStream, msgRcv, ignoreAllFlags, isGetMPos); //If command stacking is not enabled, pass the command normally without stacking.
}[/CODE]

Without command stacking, the receiver is still always accepting and processing commands on a FIFO basis but the function independent of our listener that receives the passed data ignores (with feedback to the relay) any commands it receives while it is currently executing a prior command, this is essentially FIFO packet handling that passes to a dynamic circular queue with no rear cap that dequeue's front while executing a command. With command stacking, the command is, instead, passed to a stack by the function independent of our listener to be executed upon completion of the previously received command, this is essentially FIFO packet handling that passes to a dynamic circular queue with no rear cap that doesn't dequeue front while executing a command. The reason we use a circular queue WITHOUT a rear cap is strictly because a cap hasn't been necessary as of yet. In the case that it is (possibly with live-key broadcasting), the logic is already established and all that needs to be done is fine tuning a rear cap. The only logic that changes here is whether or not we're dequeueing data handed to the pass function, packet and network handling are executed on a FIFO basis and are fundamentally exactly the same regardless of whether or not you are using command stacking.
 
Last edited:
Ionis updated IonBC (TrueBox) with a new update entry:

0.28.8.1: /Click bugfix

**Note: You should only have to replace your host-side unless you haven't updated to 0.28.8 yet, then you'll need to replace both host AND client-side.

Bug Fixes:
-Fixed a bug that was causing host-side triggers to hang when throwing a /click command due to new processing logic accessing a dispatcher that was already in use.

Thanks to @tehfeer for tracking this down and reporting it...
Click to expand...

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

0.28.8.2: /Pause fix

**Note: You should only have to replace your host-side unless you haven't updated to 0.28.8 yet, then you'll need to replace both host AND client-side.

Bug Fixes:
-Fixed a bug that caused the /pause command to throw a incorrect data type exception host-side due to us not splitting it from the interval first.

Shoutout to @LamahHerder for reporting this issue to me! Let me know if you...
Click to expand...

Read the rest of this update entry...
 
You must log in or register to reply here.
💾Software IonBC Legacy READ OVERVIEW
Next unread thread 🦁

Users who are viewing this thread

Total: 1 (members: 0, guests: 1)
Back
Top
Cart

Cart

Total -