Set n Forgets have existed since 1997,
It's in the architecture/logic/scripting and a program to run the script.

Today they call it BOT or DROIDS or whatever else the flavor of the month is,
I won't say it's wrong, but refuse to use those terminologies as illustrations, personal choice.

Most programmers usually know ZILCH about the logic, they want to have proof of the end result first, and you cannot get an end result until the programming is sorted to prove the POT, catch 22.

The "logic" comes from the punter, who has to base an architecture, based on what experience the punter has prior to deciding to go down the Set n Forget path based on actual POT hard data.
Would you give your hard earn't experience and information away ?

It's one gigantic Loop but one must have a selection method/s and results management process sorted before coding can actually begin.

The other problem that's been encountered is this;
Let's say the S n F side of things is all sorted tested and working;
There is no guarantee the TAB or receiver of bets will have their ********es sorted when the bytes travel from program to TAB sever/s.

There is a way around this though, a "sure fire" way the bets/data bytes will usually always be accepted out of your respective PC/Program,
98% ~ of the time.

The "winner" in all this is, who has a feasible architecture.