In the Rubicon 1.3 point release, CCP instituted a 50 drone limit for drone assist. That is, one single pilot could only control 50 drones at one time. Before the point release, a single pilot could control as many drones as a fleet could launch. Needless to say, a Dominix or carrier fleet can launch a lot of powerful drones. In a dev blog, CCP Rise explained the reasoning behind the change:
"We have two big motivations for making a change to drone assist: improving gameplay and improving performance. As drone assist grew in popularity, it quickly became apparent that while it’s a very powerful tactic, it isn’t much fun, especially at large scales. Having hundreds of ships' worth of drones assigned on one trigger pilot relieved an enormous amount of people from almost any responsibility in fleet.CCP actually wanted to do away with drone assist entirely, but CSM 8 convinced the game developers that enough legitimate use cases existed that a 50 drone limit was justified. But a drone bunny using ISBoxer can get around the design limit of one pilot controlling 50 drones. An ISBoxer users running a small gang of 5 fast-locking ships can, with one keystroke, simultaneously attack a target with 250 sentry drones.
"Now, EVE may not have the twitchiest gameplay around, but drone assist goes too far and testimony from frustrated pilots has been pouring in for a while now from all over. We feel that by limiting drone assist we significantly improve the chance of pilots feeling invested and responsible during fleet engagements (even if it means they don’t get to watch quite as much TV).
"The second big incentive to make a change is that drones are relatively taxing for our hardware when compared to other weapon systems. That means the recent surge in popularity of drone assist has had a tangible, negative impact on server performance in some of the battles of late. While the balance between design goals and performance goals can be tricky, this is one of those nice opportunities where we can have a positive impact on performance without any design cost at all."
In the past, CCP has come down hard on those who used software to circumvent game mechanics. In April 2013, Team Security banned 2,350 accounts guilty of using an autopilot warp to zero hack. That hack did violate the EULA in other ways than just circumventing the game mechanics, though. Of course, ISBoxer also violates the EULA, but CCP has stated that, "the multiboxing application is not something we plan to actively police at this time."
CCP, however, did put in this caveat:
"However, if any third party application or other software is used to gain any unfair advantage, or for purposes beyond its intended use, or if the application or other software violates other parts of the EULA, we may fully enforce our rights to prohibit such use, including player bans. Please use such third party applications or other software at your own risk."Given CCP Rise's explanation of why the drone assist cap was put in place, using ISBoxer to get around the cap would seem to violate the section about intentionally placing additional load on the servers (section 6A1 of the EULA). I don't know how widespread the practice is, but if anyone is using ISBoxer to circumvent the cap, I'd suggest they stop. Who knows when a spy might turn up and start turning people in to CCP.