Inviting multiple characters w/one key

[Fippy]

Config: http://www.privatepaste.com/abc9f67dfb

I'm not sure if this is an EQ restriction, an ISBoxer restriction, or I'm just doing something wrong. I put multiple actions into a step for my Invite hotkey, and only the last seems to occur. (Invite is in Always On, at the bottom).

Do I need to split these into multiple steps and use one keypress per invite? Even EQ isn't that restrictive, as I could create an in-game hotkey which invites up to 5. So I assume I'm doing something wrong. Clarification would be appreciated.

If I had to use one keypress per invite, how would I know how many times to press the key?

[bob]

I'm not sure if this is an EQ restriction, an ISBoxer restriction, or I'm just doing something wrong. I put multiple actions into a step for my Invite hotkey, and only the last seems to occur. (Invite is in Always On, at the bottom).

Do I need to split these into multiple steps and use one keypress per invite? Even EQ isn't that restrictive, as I could create an in-game hotkey which invites up to 5. So I assume I'm doing something wrong. Clarification would be appreciated.

You may be coming across how ISBoxer deals with the action processing more than anything. All the actions in a single step are essentially passed to the game in one hit, so the way you have it setup it is like doing "CTRL+C , \, CTRL+V, ENTER" three times, all within the same 10ms (this is an arbitrary time I made up assuming you are getting 60FPS, don't read anything into it about how fast ISBoxer does stuff). The game may decide to drop some of the keystrokes because it a) can't process them that fast, b) has a method to prevent double input, c) is dealing with the first CTRL+V while the others come in and it's keyboard read loop hasn't made it back around yet d) some other reason.

Simply, I think you are filling the clipboard and sending the commands so fast, that by the time the game gets around to reading from the clipboard to paste, the last character invite is the only one in there.

If I had to use one keypress per invite, how would I know how many times to press the key?

Several methods.
a) 1 less than the number of characters loaded.
b) Put a popup as the final step and set the Do Not advance on that last step for a couple of seconds (for good measure you can always set the mapped key to reset to Step 1 xx seconds after the last hotkey press)
c) Use some funky virtualisation and timers to disable toons from being invited again (well for a while anyway).

And probably others I've missed

[Fippy]

That's too bad. This is easy to do in Innerspace.

For now, I'll just define an in-game macro and bind it to a keypress. I can send the invites, and clear the targets on the down stroke, and then accept on the up stroke.

It's not like I'm going to be doing a lot of inviting. But I'm not really using ISBoxer much in this scenario.

Thanks for getting back to me. I'll see if I can hook up something else.

[bob]

It's quite easy to do in ISBoxer too.

That's too bad. This is easy to do in Innerspace.

You have to remember, ISBoxer is a configuration tool and an accompanying set of Inner Space scripts which have specific functionality in order to adhere to game EULAs.

You can develop pretty much software to do anything you please when the limits are removed, but if you are trying to [legally] run a business, and make a living from it, then it is not good practice to go around developing things that are likely to get your customer based excluded from the reason for the use of your software. If people take your core and use it in their own way, there is not much you can do about that.

[Fippy]

Of course. And I'm happy to have these tools still available, which they probably wouldn't be without these restrictions.
Plus I don't want to get into trouble for using ISBoxer.

I'm trying to be careful to ask only for things that can be done in-game. There are in-game delays in EQ:
/pause 30, /cast 4
/pause 60, /cast 2
/pause 5, /invite XXXXXX

These only affect one client, but this function is provided with the game and complies with the EULA.

But I'm not following your comment that this is easy to do in ISBoxer.
* delays between strings are not permitted
* multiple keypresses are needed

[bob]

Yes EQ and some other games are nice in that they have in game macros, scripting, exposure of methods for extensions, custom UI capabilities, or variations of. Most don't allow in built delays. Yes any function/feature that the game client provides is expected to comply with the EULA, except where it doesn't, e.g. exploits, or using the exposed functions for purposes not allowed (and usually not defined until you use them).

But I'm not following your comment that this is easy to do in ISBoxer.
* delays between strings are not permitted
* multiple keypresses are needed

I was referring that setting up an invite process was easy (ok, it's not the most simple thing out there, but it's not too tricky in the scheme of things).
Yes it will probably end up requiring multiple steps, and probably multiple presses of a key depending on the group size. In my config, I have a multi step keypress which I press 6 times (and sometimes more). At the end of the process a popup flashes up and it halts cycling for 10 seconds. Makes it fairly easy to work with. I load up, hammer on the key until I see the popup, team is all invited and accepted, job done. No need to do this again unless I disband, disconnect, or load a new team. If I had RSI, or a really old keyboard with limited life left in the springs I might be more concerned about having to press it 6 times rather than once.

Delays are not available in ISBoxer in keystrokes, keystrings or button presses as this is venturing into macros and automation from external programs, which is pretty much against every EULA/TOS/Code of Conduct out there. EQ is the first I've come across where macros and automation are not specifically called out, but then they do prohibit all third party programs, like most, so you may not be strictly complying even with ISBoxer, but that particular one is usually ignored as it cuts out using mouse drivers, and Vent, Excel, and other stuff that they have no business policing.
If delay functionality was provided through ISBoxer for EQ, you'd find others hacking about and using it for other games, and then they'd get banned, and the chatter would start, and the income would go down, etc. It is a minor thing to not provide considering the features you do get. Yes you could do all the same things directly via Inner Space scripts, but that really limits the potential customer base. ISBoxer is for those who don't have the ability, inclination or time to learn ISS (or other software) in order to multibox.

[Fippy]

FYI: The devs have repeatedly said that ISBoxer is compliant. Holly repeated this on the last livestream. We are not even in questionable territory. Well unless automation is used.

Thanks for the update. I'll burn an in-game hotkey to invite my team And I'm not going to worry about that. I still need to figure out how those virtual keys are filled in. I can't find one example that goes end-to-end.

[bob]

This covers the beginnings of applying virtualization. http://www.isboxer.com/wiki/Style:MMO_-_Pro

[Fippy]

Thanks! Even more to read, which is nice.