These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

EVE General Discussion

 
  • Topic is locked indefinitely.
 

Update regarding Multiboxing and input automation

First post First post First post
Author
Lucas Kell
Solitude Trading
S.N.O.T.
#2721 - 2014-12-21 21:49:21 UTC
Hallvardr wrote:
perhaps ... but video longer than 30 minutes ore it didn't happen. Cool (see what I did there)
Roll Eve noobs these days. Multiboxing mass fleets has been around a lot longer that ISBoxer has been popular kiddo.

Hallvardr wrote:
I hope you were saying this as a generalization and not to me specifically. I've already established my stance,
"I could care less about isboxer .. I'm not a user."
"if I did and it hampered my progress, I'd adapt."

So for me .. i don't care either way which is also why I'd held off my opinion as long as I had.
Strange, because it really does seem like you do care.

The Indecisive Noob - EVE fan blog.

Wholesale Trading - The new bulk trading mailing list.

Lucas Kell
Solitude Trading
S.N.O.T.
#2722 - 2014-12-21 21:56:35 UTC
Trakow wrote:
You do realize that the mouse is also an input device right? So one click to select an object either from the overview or from the screen for multiple clients is also considered input broadcasting. But if you're going to individually click on each window or overview one at a time then have at it. But I'm sure most people don't realize the mouse is also considered input. This will still get many ppl the 30-day ban, and will make ISBoxing that much less useful.

And also, round robin can still be considered automation because isboxer automatically changed the input focus after each button press without user input to do so.
It seems that like many many many others, you don't know how ISBoxer works or what round robin/ VideoFX entails. It's been explained probably hundreds of times in this very thread, so if you haven't figured it out yet, you probably never will. The only thing you really need to know is that it won't be banned as it's not input broadcasting and is near impossible to reliably separate from manual multiboxers, so is unlikely to be banned on it's own. Most multiboxers have already adapted the new methods they will be able to continue using beyond January.

The Indecisive Noob - EVE fan blog.

Wholesale Trading - The new bulk trading mailing list.

Trakow
Beta Switch
#2723 - 2014-12-21 22:23:18 UTC
Lucas Kell wrote:
Trakow wrote:
You do realize that the mouse is also an input device right? So one click to select an object either from the overview or from the screen for multiple clients is also considered input broadcasting. But if you're going to individually click on each window or overview one at a time then have at it. But I'm sure most people don't realize the mouse is also considered input. This will still get many ppl the 30-day ban, and will make ISBoxing that much less useful.

And also, round robin can still be considered automation because isboxer automatically changed the input focus after each button press without user input to do so.
It seems that like many many many others, you don't know how ISBoxer works or what round robin/ VideoFX entails. It's been explained probably hundreds of times in this very thread, so if you haven't figured it out yet, you probably never will. The only thing you really need to know is that it won't be banned as it's not input broadcasting and is near impossible to reliably separate from manual multiboxers, so is unlikely to be banned on it's own. Most multiboxers have already adapted the new methods they will be able to continue using beyond January.


So are you saying that when you click on an object to lock onto it, that you do it individually for each client? If so then that's fine. But if you click once and all your clients select/lock the same target, then this is still input broadcasting...
FunGu Arsten
Ascendance
Goonswarm Federation
#2724 - 2014-12-21 22:35:36 UTC
I cant believe this is still going on....
Nolak Ataru
Hedion University
Amarr Empire
#2725 - 2014-12-21 22:41:51 UTC
Trakow wrote:
So are you saying that when you click on an object to lock onto it, that you do it individually for each client? If so then that's fine. But if you click once and all your clients select/lock the same target, then this is still input broadcasting...


He must click once for each client to lock / target / activate button.
This was stated ages ago.
Please learn to read, or do some research before jumping on the bandwagon.
Lucas Kell
Solitude Trading
S.N.O.T.
#2726 - 2014-12-21 23:58:12 UTC
Trakow wrote:
Lucas Kell wrote:
Trakow wrote:
You do realize that the mouse is also an input device right? So one click to select an object either from the overview or from the screen for multiple clients is also considered input broadcasting. But if you're going to individually click on each window or overview one at a time then have at it. But I'm sure most people don't realize the mouse is also considered input. This will still get many ppl the 30-day ban, and will make ISBoxing that much less useful.

And also, round robin can still be considered automation because isboxer automatically changed the input focus after each button press without user input to do so.
It seems that like many many many others, you don't know how ISBoxer works or what round robin/ VideoFX entails. It's been explained probably hundreds of times in this very thread, so if you haven't figured it out yet, you probably never will. The only thing you really need to know is that it won't be banned as it's not input broadcasting and is near impossible to reliably separate from manual multiboxers, so is unlikely to be banned on it's own. Most multiboxers have already adapted the new methods they will be able to continue using beyond January.


So are you saying that when you click on an object to lock onto it, that you do it individually for each client? If so then that's fine. But if you click once and all your clients select/lock the same target, then this is still input broadcasting...
Yes, however you are able to spam press 1 key without alt tabbing, rather than switching and key pressing, or in the case of VFX make merge multiple clients controls into a single window. The result of which is that this change doesn't prevent mass multiboxing in any way, it simply removes one of the many methods of control. This change is a pointless waste of time which avoids the real issue which is crappy gameplay mechanics.

The Indecisive Noob - EVE fan blog.

Wholesale Trading - The new bulk trading mailing list.

ESN Seeker
The Scope
Gallente Federation
#2727 - 2014-12-22 02:45:52 UTC
I don't use software that provides "round robin" service, so I don't know what any such software, that exists currently, does.

Suppose, though, that "round robin" means that there is an automatically generated alt-tab after the first keystroke, then two auto-alt-tabs after the second keystroke, etc., so that successive keystrokes go to different EVE-sessions.

Although this might not fall afoul of the Prohibition Against Broadcasting, might it not violate the Prohibition Against Generating Keystroke Sequences?

But how about an intermediate case? What if one had a foot-pedal that generated alt-tab for every pump of the pedal? One could pump once after the first keystroke, twice after the second, etc., to switch round-robin amongst multiple sessions.

Would using such a foot-pedal violate the Prohibition Against Generating Keystroke Sequences?

Argument in the Affirmative: Yes, because alt-tab is a two-keystroke sequence.

Argument in the Negative: No, because alt is just a shift that modifies other keys; only the tab-keystroke is a keystroke.

I tried to file a Support Ticket asking this question, but it has been several hours since I submitted it and the ticket not -- or at least not yet -- appeared under "My Tickets". Since I have not filed a support ticket since 2006, I don't remember how long it's supposed to take for a ticket to appear after filing.
ShadowandLight
Trigger Happy Capsuleers
#2728 - 2014-12-22 02:47:23 UTC
As far as I know there has been no response from CCP to answer numerous questions we've had about this new policy. A rumored sit down meeting has also not happened and app

I'm really disappointed in this decision to not have an open discussion about this with CCP, I hope they change their mind and talk to "advanced" multiboxing community.
Proddy Scun
Doomheim
#2729 - 2014-12-22 03:02:05 UTC
ShadowandLight wrote:
As far as I know there has been no response from CCP to answer numerous questions we've had about this new policy. A rumored sit down meeting has also not happened and app

I'm really disappointed in this decision to not have an open discussion about this with CCP, I hope they change their mind and talk to "advanced" multiboxing community.



Its pretty clear to me that this CCP policy is not subject to negotiation.
Here CCP did some research using player input first. But I don't think CCP ever said players had a vote on this issue.

CCP does a very good job of working letting players in on deciding many issues.-- maybe most. But CCP has to claim exclusive ownership of a few decisions to keep the game wide open to all players....rather than letting the loudest or strongest cliche drive everyone else out through rule management.
Proddy Scun
Doomheim
#2730 - 2014-12-22 03:25:09 UTC
The input multiplexing issue is also very simple.

Do the inputs get acted on by the desktop OS (including the start up EVE client)? Allowed
(Round robin window switching therefore allowed. No EVE server involvement.)


Or does the input get acted upon by the EVE server via the client? this is an in game effect

If a single user input action (keystroke or click) produces multiple player commands on the server -- not allowed.

A single input movement producing multiple commands in 1 client or 1 command in multiple clients - either way CCP is gonna slap you.

Nope it does not sound like CCP wants to debate the game lawyers or complicate their tasks by allowing you to send commands to change overview settings on multiple clients. From a practical point it makes CCP's job easier to treat all commands to the EVE server the same - and that is how they are gonna do it. In this case the convenience of CCP enforcement overrides your personal convenience for something 99% of EVE does manually.


Nolak Ataru
Hedion University
Amarr Empire
#2731 - 2014-12-22 03:59:16 UTC
Proddy Scun wrote:
The input multiplexing issue is also very simple.
Do the inputs get acted on by the desktop OS (including the start up EVE client)? Allowed
(Round robin window switching therefore allowed. No EVE server involvement.)
Or does the input get acted upon by the EVE server via the client? this is an in game effect
If a single user input action (keystroke or click) produces multiple player commands on the server -- not allowed.
A single input movement producing multiple commands in 1 client or 1 command in multiple clients - either way CCP is gonna slap you.
Nope it does not sound like CCP wants to debate the game lawyers or complicate their tasks by allowing you to send commands to change overview settings on multiple clients. From a practical point it makes CCP's job easier to treat all commands to the EVE server the same - and that is how they are gonna do it. In this case the convenience of CCP enforcement overrides your personal convenience for something 99% of EVE does manually.


Jesus christ the irony is burning. You claim that the game should be wide open to all players and not let "the loudest or strongest cliche drive everyone out" yet you don't see that this change was brought about by a loud minority of players who's arguments consist of "I don't do it so he shouldn't", "hurrdurr it's a bot even though I know nothing about the software", and, my favorite, "he's cheating because he has multiple accounts open" which is similar to "I know nothing about 6A3 and how it works, so I'll claim he's gaining an unfair advantage because I'm under the impression that he doesn't have to pay for his accounts." CCP did the exact same research that Target did after presented with the Change.org petition that was so full of lies, the North Korean propaganda team stood in awe of it. Listening to the whiners in the minority may change something in the short term, and may indeed cause a short-term improvement, but in the long term will cause more harm as players remember that they bent to the will of the equivalent of SJWs, or if they continue to bend over for said lunatic few.

Round Robin sends 1 command to 1 client per input. It then sends 1 command to the next client on the next input. It uses similar concepts on window focusing that VideoFX does.

If any issue warranted, no, NEEDED player input and discussion before a go-ahead, it would be this. Instead, we're treated like third-class citizens thanks to, in part, the public's lack of knowledge as to what ISBoxer lets a player do, the unwillingness to differentiate between an ISBoxer with a human behind the keyboard that stops doing things when the player goes for a smoke break, and a botter that continues to operate while the person went down to the corner store for a pack of smokes and a 40. Not to mention that CCP absolutely refused to sit down with multiple ISBoxer reps until after Jan 1, after lying to EVERYONE at Fanfest and EVE Vegas, where CCP Seagull and other CCP devs were seen by dozens if not hundreds of witnesses going around telling people "Multiboxers have nothing to fear" and "Nothing's changing regarding multiboxing."
Eli Apol
Definitely a nullsec alt
#2732 - 2014-12-22 04:45:39 UTC
Round robin sends one command to the focus window and one command to your window management software (to change to the next focus window) per click.

Macro.

(Also to preempt your next attempt at having alternate presses do the same dirty, you're then sending each click to the mouse software to control the switching of functions, so still a macro.)

but what would I know, I'm just a salvager

Nolak Ataru
Hedion University
Amarr Empire
#2733 - 2014-12-22 06:12:00 UTC
Eli Apol wrote:
Round robin sends one command to the focus window and one command to your window management software (to change to the next focus window) per click.

Macro.

(Also to preempt your next attempt at having alternate presses do the same dirty, you're then sending each click to the mouse software to control the switching of functions, so still a macro.)


Technically no. It sends command A to window 1 on button press #1. It then sends command A to window 2 without changing windows on button press #2. If it sent the command and then alt-tabbed, or something similar, then yes, it would be a macro.
Since it doesn't, it isn't, and you don't know what you're talking about.
Orchid Fury
University of Caille
Gallente Federation
#2734 - 2014-12-22 07:16:44 UTC  |  Edited by: Orchid Fury
Nolak Ataru wrote:
Eli Apol wrote:
Round robin sends one command to the focus window and one command to your window management software (to change to the next focus window) per click.

Macro.

(Also to preempt your next attempt at having alternate presses do the same dirty, you're then sending each click to the mouse software to control the switching of functions, so still a macro.)


Technically no. It sends command A to window 1 on button press #1. It then sends command A to window 2 without changing windows on button press #2. If it sent the command and then alt-tabbed, or something similar, then yes, it would be a macro.
Since it doesn't, it isn't, and you don't know what you're talking about.


since only one window can have focus to accept keyboard input, it has to fall under the policy. even if it doesn't send an alt+tab, it sends your command + a switch of window focus. as here is even logic included as to which window to switch next, it clearly is a macro.
Nolak Ataru
Hedion University
Amarr Empire
#2735 - 2014-12-22 07:59:31 UTC
Orchid Fury wrote:
Nolak Ataru wrote:
Eli Apol wrote:
Round robin sends one command to the focus window and one command to your window management software (to change to the next focus window) per click.

Macro.

(Also to preempt your next attempt at having alternate presses do the same dirty, you're then sending each click to the mouse software to control the switching of functions, so still a macro.)


Technically no. It sends command A to window 1 on button press #1. It then sends command A to window 2 without changing windows on button press #2. If it sent the command and then alt-tabbed, or something similar, then yes, it would be a macro.
Since it doesn't, it isn't, and you don't know what you're talking about.


since only one window can have focus to accept keyboard input, it has to fall under the policy. even if it doesn't send an alt+tab, it sends your command + a switch of window focus. as here is even logic included as to which window to switch next, it clearly is a macro.


VideoFX allows a player to have multiple window's focus on a single screen. Doesn't break EULA. Neither does RR no matter how loud you cry.
Lucas Kell
Solitude Trading
S.N.O.T.
#2736 - 2014-12-22 08:05:15 UTC
ESN Seeker wrote:
Suppose, though, that "round robin" means that there is an automatically generated alt-tab after the first keystroke, then two auto-alt-tabs after the second keystroke, etc., so that successive keystrokes go to different EVE-sessions.

Although this might not fall afoul of the Prohibition Against Broadcasting, might it not violate the Prohibition Against Generating Keystroke Sequences?
No, because keyboard sequences cover game actions. If you want to set up a key that presses F1, then opens 6 web browsers, 4 notepads and a calculator, that's within the rules. As long as it performs only 1 game action.

Proddy Scun wrote:
Its pretty clear to me that this CCP policy is not subject to negotiation.
Here CCP did some research using player input first. But I don't think CCP ever said players had a vote on this issue.

CCP does a very good job of working letting players in on deciding many issues.-- maybe most. But CCP has to claim exclusive ownership of a few decisions to keep the game wide open to all players....rather than letting the loudest or strongest cliche drive everyone else out through rule management.
It's not about negotiation, it's about clarification. At the moment there's so many edge cases left unanswered. It's a common CCP thing to start up a "discussion" then completely ignore it, leave things as clear as mud and wait until it explodes around them before trying to deal with it.

The Indecisive Noob - EVE fan blog.

Wholesale Trading - The new bulk trading mailing list.

Orchid Fury
University of Caille
Gallente Federation
#2737 - 2014-12-22 10:49:23 UTC  |  Edited by: Orchid Fury
Nolak Ataru wrote:

VideoFX allows a player to have multiple window's focus on a single screen. Doesn't break EULA. Neither does RR no matter how loud you cry.


it does break the eula. you may look in the eula under conduct, section 3. it always did.
ccp only stated that, come januar, they will activly enforce this rule against the current overusage of input broadcasting. which was against the eula as well, stop claiming it wasn't. wether you can get away with your "workaround" remains to be seen, but you clearly can not see the writing on the wall.
the only one crying is you at all. "whawhaa why don't ccp listen to isboxers. we're humans to. :(("
Eli Apol
Definitely a nullsec alt
#2738 - 2014-12-22 11:06:16 UTC  |  Edited by: Eli Apol
Nolak Ataru wrote:
Technically no. It sends command A to window 1 on button press #1. It then sends command A to window 2 without changing windows on button press #2. If it sent the command and then alt-tabbed, or something similar, then yes, it would be a macro.
Since it doesn't, it isn't, and you don't know what you're talking about.

So ISboxer *knows* to change the window focus to the next window in line without seeing the input to the first window? Wow you have a prescient bit of software there. I'm afraid it's a macro - cry "No, it can't be" all you like. But it's a macro. One might even say 'Technically so.'


Lucas Kell wrote:
No, because keyboard sequences cover game actions. If you want to set up a key that presses F1, then opens 6 web browsers, 4 notepads and a calculator, that's within the rules. As long as it performs only 1 game action.

I believe you're falling into the mistake of only referring to the new ruling from the Multiplexing post. The quote from Team Security's devblog says "Any use of macros to interact with the game world is prohibited by EULA now, and has always been"

That, to me at least, implies that any external macro that interacts with the game in even one place, is breaking the EULA.

SO yeah, I'd definitely petition that before you start giving suggestions on how this will be enforced.

As I said many pages ago - they won't let people idly sidestep their intended rulings on multiplexing with a simple implementation like round robin. (And as you mostly successfully argued, I agree they'll probably struggle to differentiate from *some* legitimate 120 APM players who should be playing Starcraft or something.)

Given enough time to monitor someone though, I suspect that it'll become fairly clear who's using macros and who's spamming the F-keys nice and fast - although people who *want* to bend the rules (or break them rather) could decide to code in delays etc to make themselves less catchable - at that stage you've pretty much stepped over the line and are just trying to evade detection, so I would no longer call those actions 'legal'

but what would I know, I'm just a salvager

Lucas Kell
Solitude Trading
S.N.O.T.
#2739 - 2014-12-22 11:48:41 UTC
Eli Apol wrote:
I believe you're falling into the mistake of only referring to the new ruling from the Multiplexing post. The quote from Team Security's devblog says "Any use of macros to interact with the game world is prohibited by EULA now, and has always been"

That, to me at least, implies that any external macro that interacts with the game in even one place, is breaking the EULA.

SO yeah, I'd definitely petition that before you start giving suggestions on how this will be enforced.
Aside from the fact that the negative press they would receive if they banned this would be unbelievable (many gaming keyboards and mice perform other tasks directly while you are interacting with your game) it would be impossible to detect without a massive amount of false positives. So there's no way they'll enforce it beyond multiple simultaneous game affecting actions (multiplexing). CCP are pretty dumb, but not that dumb.

Eli Apol wrote:
As I said many pages ago - they won't let people idly sidestep their intended rulings on multiplexing with a simple implementation like round robin. (And as you mostly successfully argued, I agree they'll probably struggle to differentiate from *some* legitimate 120 APM players who should be playing Starcraft or something.)

Given enough time to monitor someone though, I suspect that it'll become fairly clear who's using macros and who's spamming the F-keys nice and fast - although people who *want* to bend the rules (or break them rather) could decide to code in delays etc to make themselves less catchable - at that stage you've pretty much stepped over the line and are just trying to evade detection, so I would no longer call those actions 'legal'
Their ruling is pretty clear. 1 press = 1 action on 1 client. What else it does outside that is irrelevant. Using round robin or VFX isn't side stepping that, it's simply not included in that ruling. I'm sure people using static timed delays will get caught, as that's actually macroing and turning 1 press into multiple actions, but someone sitting there manually pressing one button for a round robin bind isn't. I'm sure if they could find a reliable way to differentiate between that and a legit multiboxer that they would ban it but they won't, so...

The Indecisive Noob - EVE fan blog.

Wholesale Trading - The new bulk trading mailing list.

Mister Holder
Faceless Men
#2740 - 2014-12-22 12:15:16 UTC
Mierin Arthie wrote:
CCP Falcon wrote:
We would like to clarify that it does not matter how Input Broadcasting and Input Multiplexing are being done, whether through use of software or modified hardware. Our only concern is regarding how it is being used in the EVE universe.

How does this policy update regard the usage of KVM switches to control multiple computers from one mouse/keyboard?

for those that dont know what a kvm switch is: http://en.wikipedia.org/wiki/KVM_switch



I think CCP is specifically targeting the use of ISBox and people who run 20 accounts to do various tasks. I.e. the guy who uses 20 ishtar accounts to run WH sites, people who run a ton of mining accounts with it, etc, etc.

Seems like it boils down to if you have one computer you shouldn't be running an excessive amount of client at the same time to do mind numbing tasks.