Sorry - but the FRC DriverStation Connectivity script is not something we're interested in including due to its political nature.

Photon Vision isn't something that really fits this tool - as it's something you need extremely specific setup in addition to the images; whereas the Limelight images work out of the box/are required for debugging.

For 2025's update this kind of tooling would be more team-focused - which I'm happy to include (whenever I finish the avalonia UI rewrite...)

Thanks.

I was unaware that the FRC DriverStation Connectivity script had a political nature. I haven't used it, but it's something I see recommended on CD, so was thinking of giving it a try next time that's an issue. Should I remove it from my toolkit?

Photon Vision works surprisingly well out of the box, and the recent update is important because it purportedly resolves certain reliability/freezing issues.

What about Elastic Dashboard? Teams often find themselves struggling with ShuffleBoard crashes at competition.

I was unaware that the FRC DriverStation Connectivity script had a political nature. I haven't used it, but it's something I see recommended on CD, so was thinking of giving it a try next time that's an issue. Should I remove it from my toolkit?

It it were widespread, it would be classified by AV tools as a virus because it acts automatically and disables a whole bunch of security tools.

It is convenient, but should always have the revert script used if it's ever used on anything that connects to the internet. My personal concern is that it gets used indiscriminately and not reverted and cause problems later that gets blamed on the CSA/FTAA/FTA that used it without understanding or explaining what it does and the consequences. Wider distribution makes it more likely that happens.

I was unaware that the FRC DriverStation Connectivity script had a political nature. I haven't used it, but it's something I see recommended on CD, so was thinking of giving it a try next time that's an issue. Should I remove it from my toolkit?

It it were widespread, it would be classified by AV tools as a virus because it acts automatically and disables a whole bunch of security tools.

It is convenient, but should always have the revert script used if it's ever used on anything that connects to the internet. My personal concern is that it gets used indiscriminately and not reverted and cause problems later that gets blamed on the CSA/FTAA/FTA that used it without understanding or explaining what it does and the consequences. Wider distribution makes it more likely that happens.

100% agree.

What about Elastic Dashboard?

wpilibsuite/WPILibInstaller-Avalonia#423

It it were widespread, it would be classified by AV tools as a virus because it acts automatically and disables a whole bunch of security tools.

The script does not disable any security tools. It does disable the Windows Firewall, but unless disabled by a GPO Windows will display a warning in the lower right hand corner at every login that the firewall is disabled and a big button to re enable it.
As for being classified as a virus, The script is interactive by design and does not "act automatically" it must be interactivity executed. All the commands used are officially supported Windows administrative commands that follow Microsoft's documentation for use.

It is convenient, but should always have the revert script used if it's ever used on anything that connects to the internet. My personal concern is that it gets used indiscriminately and not reverted and cause problems later that gets blamed on the CSA/FTAA/FTA that used it without understanding or explaining what it does and the consequences. Wider distribution makes it more likely that happens.

That's why the revert script exists correct, but in general with the default firewall warning to re enable, the rule's being restricted to a private /8, how good Windows Defender is now (which is NOT disabled), and that almost all modern networks have some kind of network level firewall, I would consider the risk very low if the revert script is not used.

In addition, all the actions the script executes are actions from the official FTAA/CSA troubleshooting documentation, just scripted to speed up the troubleshooting process.