Excuse the canned response, but I answer this quite a bit!
We don't inject in to the client so we can't create a TLO directly in-game, which really sucks.
So, essentially, what we do is we overlay a hotbar directly over every application that holds all of our logic. This is the big reason why EQ needs to be in Windowed Mode on the host-side, or else we can't overlay.
So, you'll notice, clickthrough actually doesn't happen on normal applications like a web browser, notepad, games that don't use DirectX, etc. This is, once again, because of the DirectInput wrapper.
DirectInput wraps over your native input and checks whether or not you've sent input and then sends that input directly to the client. It doesn't matter if you're clicking in another window or not, if EQ is your foreground window it will send the input to EQ regardless.
I'm not going to go over all the reasons why we can't inject or modify memory data to explain why I can't modify this in any way to avoid redundancy, but you can imagine why this is an issue.
This makes blocking calls very, very tricky. Unfortunately, there isn't much we can do in the ways of preventing this without injection or memory manipulation.
But there is a solution!
Open up a new chatbar in EQ and size it to a little bigger than your window, turn the opacity almost all the way down and lock the chat window. You'll want to make sure that the windows X button and bar you'd type into aren't under any buttons.
At the end it should look something like this (My hotbar as an example):
This will block any clickthrough functionality you may run in to as the TLO under the hotbar will block anything passing.
Sorry I searched and didn't see. I goofed thanks for the response.
No need to apologize man!
If you ever have any questions, don't hesitate to contact me!Yeah! This is actually planned for an upcoming update here where you can set the default dimensions (and other information) for buttons as well as define their sizes dynamically within the Create Button window!
First I've heard of this, but if you can figure out how to reproduce it just let me know!
I'll take a look at this but the process controller really needs to be revamped overall, I feel like it could be done a lot better than it is and a lot of the controls are pretty confusing. Have you tried adding a Add Win Kb and then using that to set the windows on reset for tabbing to as opposed to going in and resetting all the processes every time? Just make sure they're the foreground window when hitting the Add Win Kb to set the process. That would probably alleviate some of the issues you're having. As far as Toggle GUI on Window Change, it should automatically detect EQ assuming the proper EQ client was selected through the processes window and it should automatically reselect EverQuest when it's closed and re-opened but if this isn't happening let me know. I plan to revamp the process controller coming up here, since it desperately needs some code maintenance.
There is! You can use the /click command over the buttons ID which can be found right under the button preview in the Create/Edit button window!
I'm not sure if you're referring to the in-game command /memspellset or if you're referring to the button ID of an IonBC button, so let's go over both!
Thanks man! I appreciate the kind words, they mean a lot to me.
If you ever have any questions or concerns, just let me know!Fantastic, just the info. I need. Thanks againI'm not sure if you're referring to the in-game command /memspellset or if you're referring to the button ID of an IonBC button, so let's go over both!
/memspellset:
First, make spell set and name it anything, let's take my spellset Battle for example:
View attachment 41285
After you've done that, you can just type /memspellset SpellSetNameHere and it will automatically load up that spellset! So, for my spellset Battle, I would type /memspellset Battle!
For IonBC Button ID:
1. Create a button!
2. Right click that button to open the edit button window!
After you've done that, you can find the button ID below the Button Preview, as indicated here by the red square:
View attachment 41286
From there, all you have to do is make a button for /click ButtonIDHere! You can also use button name within quotations, so the syntax for my SHM Buff button would be:
/click 710458
OR
/click "SHM Buff"
As an added side-note, DayBreak recently added a new command called /memspellslot which allows you to designate a specific spell to be memmed in a specific slot! This is really useful for loading one time spells like gate or invis.
Syntax is:
/memspellslot # spellname
So, if you wanted to load gate, you could do something like:
/memspellslot 7 Gate
And it will load Gate dynamically in to spellslot 7!
Let me know if you have any questions!
Hey!
If you ever have any questions or anything just let me know!This is definitely possible, but depending on the scenario may require a few things, but first and foremost I see that you're using comma as a delimiter for a lot of the commands! The commands only take a semi-colon as a delimiter, so change this:
Yea was just using the above line as a possible example of easy way to parse and write it for the peoples and cake way of doing the deserialization of object's on featureThis is definitely possible, but depending on the scenario may require a few things, but first and foremost I see that you're using comma as a delimiter for a lot of the commands! The commands only take a semi-colon as a delimiter, so change this:
/click 634638; /ibt cleric /cast1, /pause50, /cast 2, /pause 80, /cast 3, /pause 35, /sit; /ibt Druid /cast 1, /pause 30, /cast 2, /pause 60, /sit;
To this:
/click 634638 ; /ibt cleric /cast 1 ; /pause 50 ; /cast 2 ; /pause 80 ; /cast 3 ; /pause 35 ; /sit ; /ibt Druid /cast 1 ; /pause 30 ; /cast 2 ; /pause 60 ; /sit
As far as throwing a click and then continuing, this really depends on how long the 634638 command takes to process and what it's targets are.
For instance, if the targets of 634638 are not cleric, Druid or included in the target field of this button, then it wouldn't matter if you throw the click over 634638 as the command wouldn't be rejected and/or stacking with those designated clients.
If 634638 DOES share a target field with cleric, Druid or the targets of the button calling the /click command, then you'd want to throw a pause for the time it takes 634638 to complete it's processing for most cases unless you have command stacking enabled.
With command stacking enabled, it will just stack the commands sent to the cleric, Druid or target field clients behind the /click 634638 command as it's sent post-click. But if command stacking is NOT enabled, then you'll want to throw a pause in there for the determinant time it takes for the 634638 command to finish processing.
For example, say 634638 takes 30 seconds to process, the button would then look like this:
/click 634638 ; /pause 300 ; /ibt cleric /cast1 ; /pause 50 ; /cast 2 ; /pause 80 ; /cast 3 ; /pause 35 ; /sit ; /ibt Druid /cast 1 ; /pause 30 ; /cast 2 ; /pause 60 ; /sit
If you plan on using command stacking, you can find it in the options tab of the Server Window!
Let me know if you have any questions!
Durango's solution should work, but you can also use the name!
Thanks .... works like a charm!Durango's solution should work, but you can also use the name!
[CODE title="Usage"]/useitem Drunkard's Stein[/CODE]
Should work for what you're looking to do, I use /useitem with item name in a few of my buttons commands.
Let me know if you run in to any issues!
