I can report that the problem is exacerbated when starting the second wrobot instance
during this I've discovered that wrobot is launching an additional executable at windows startup - can you explain what this is for ? hopefully nothing nefarious
Can confirm this is working for 1.12 - initially the behavior is that it won't attack until you manually set focus, after that the bot goes into it's rotation but a couple of things you need to configure, check to make sure the player is added to the ignore list in advanced settings for security and then in the advanced settings tick the option to allow the bot to "attack units in combat already" - after that it started working fine