![GI Team Colors](https://i.imgur.com/St7FKkA.gif)
Manike, you're a smart guy, and I really respect you, but I think you're making some assumptions about what I'm proposing that are not accurate.manike said:Do you really believe this?
Who's going to write the code for all the different guns, and make sure the settings work for all the different guns? No 'one series' of settings will run every gun. No 'one series' of debounce values will work with all mechanical trigger geometries or gun operating systems.
And find me someone with that ability that wouldn't be influenced/corrupted or that isn't linked to a manufacturer or team.
If you can name me anyone who makes electronic chips that isn't linked to a team or manufacturer or similar to the point he would be biased, and that has the skills required, you'll match the one name in my head. And he's busy and expensive, and probably would be hard to get to do it.
And then tell me why it won't make any difference whatsoever because it is so easily circumnavigated by any of the other board manufacturers who already produce cheater equipment.
If you don't take apart every gun running such a chip to inspect it for other electronics, your chip is absolutely useless. Want to know how easy it would be to hid another small chip, purely designed to get around your 'safe' chip? Now that's the trivial part...
Want to inspect every gun? Every time there is a 'concern' on what it is doing?
Heck most events never even find the cheater switches hidden on many guns.
Most events never even check to see that the guns are in tournament locked mode. And you expect them to be sure that only this 'safe' chip is running the gun?
Sorry, but I don't see this idea ever making it. It just doesn't have any basis in reality, even if the idea 'looks good on paper'.
And anyway, what you REALLY need to do is to catch the cheats, and penalise them so it stops it being done at all levels. Some one big needs to get caught and penalised big.
They key problem is that when we go to test markers, we do not know if the electronics are acting the same way during the test as they were when the marker was in use during the game, because the rules allow the software that runs the marker to be secret.
The principle change I am advocating is banning secret software in tournament markers. Contrary to popular belief, turning trigger events into solenoid movements is not hard. The league, or someone hired by the league, provides a standard software program. This program has various settings so that manufacturers can control how trigger events translate into solenoid movements for their markers. WHAT the settings are is NOT IMPORTANT - having adjustable settings in a software program isn't any different than having adjustable settings in the gun mechanics for gun velocity. What IS important is that:
- You can determine what the settings are
- The program does not allow the settings to be changed between gametime and testing
- You can read the chip to determine that the software on the chip is indeed actual certified software.
Now, you seem to be implying that you won't be able to find anyone you can trust to create this software. Trust is not important, as everybody can look at the source to the software. You don't need to trust the writer because you can look at what they have written and look at what is on the chip.
Now, on the off chance that the standard program can not accomodate a particular marker design, you can allow manufacturers to modify the standard program or create their own program, as long as they make the source available to the league and it meets the requirements of not allowing the settings to be changed on the fly. The only important part is that to be used in a tournament, a gun must use a standard chip, that is readable, that has known, certified software on it.
Once you have software where you KNOW the behavior, you can just test guns the same way we did before the introduction of electronics - if the settings on the gun allow the gun to be fired illegally, you'll be able to test the gun and determine that, because UNLIKE what we have now, where the settings of the software can change without anyone knowing, the KNOWN, READABLE software will behave the same way under test as it did during the game.
I think the 'problems' you're highlighting are based on just having someone write a different secret program that the league then certifies. And you're right, that wouldn't work at all.