Yes. Defense Ranges is the most obvious, since it gives players pixel-perfect ranges of static defenses.Are there widgets which give a large advantage to players with them, over players that don't have them?
The Custom Formations Widget allows for movement patterns that simply aren't available manually.
There are Widgets that will auto-track Commander sightings, auto-mark certain types of enemy structures to make information sorting easier, etc.
And I have thought up a few that aren't even real Widgets yet, but could certainly exist, like showing players the valid movement locations of a given Unit as an overlay to the actual map. Voila- you now know, instantly, which paths are valid for setting up a sneak attack / ambush, with any unit on any map.
All of these things add up to fairly significant advantages, frankly. People who don't get that are fooling themselves. The people who write these things know very well that they're providing information that isn't obvious or readily available, and even an expert player can't know all of the things that computer automation makes it fairly easy to present. It'd be nice in Starcraft, for example, to know where you last saw enemy units leave your Fog of War, but Blizzard rightly chose not to reveal that information. In Spring, these choices have been taken away from game designers, which causes a lot of frustration, hence the posts about this.
People say, "we don't have any Widgets that auto-play our game for us, therefore there is no problem".
That's stupid, frankly. RTS games are largely about information. When people have information that they couldn't normally have (or instantly get information that usually costs either game counters or huge numbers of hours of playing time), they have a major advantage. You don't need something to perfectly aim your D-Gun to have a fairly serious edge over opponents who aren't using the same things. Just knowing that you've successfully scouted the enemy Commander, instantly and with perfect accuracy, may be enough, in a serious game.
I suspect that the main reason that this isn't a bigger issue is that frankly most newbies are so boggled by Spring's UI that they simply don't know what's available to them. Otherwise we'd hear more about this issue, and how it's distorting serious play.
The problem that we face is that it's impossible to put a real limit on this stuff without being totally draconian about it atm. I'd like a more flexible response.
I like Smoth's idea, where people pick "safe" and "unsafe" modes, and that combined with a Widget-sharing software would probably be about as ideal as it gets. Since it's apparent that we're not going to have a secure executable in any meaningful sense in the immediate future, then it's best to simply try and level the playing field as much as possible.