Elements of the ULTIMATE Chess GUI?

[hgm]

I'm still looking for a low-latency GUI (Arena is an example of the opposite) that would have the same flexibility that Arena has regarding tournaments, that is that you can save them in a file that would contain all the info, so you can load it whenever you want, you can play some games, then stop, load another tournament, play some games, stop, power off the pc, turn it on again, resume the 1st tournament, edit the list of participants and it would automatically adjust the schedule, etc etc. So far all the GUIs that I've found will just have the option of running 1 tournament, but when you want to create another, the previous one will disappear and you'll lose everything.

So you apparently never 'found' WinBoard / XBoard.

Not sure what you expect from editing the list of participants of an ongoing tournament, though. WinBoard allows you to replace a participant, either with or without replay of all games it already did.

Another thing that would be great, is having an option to automatically re-run (replay) games that finish in an abnormal way (be it time forfeits, illegal moves, engine crashes, etc) with some sort of sub-option to save the games that finished in an abnormal way in a different pgn (or even discard them), so the main tournament pgn only contains "good" games.
I don't mind editing .txt files, I do it with Arena all the time.

This is an interesting idea. And it should not be very difficult to implement. But it would expose you to the risk of a tournament getting stuck because of a broken engine that will forfeit all its games. So that the first game it plays will be replayed forever.

[CMCanavessi]

This is an interesting idea. And it should not be very difficult to implement. But it would expose you to the risk of a tournament getting stuck because of a broken engine that will forfeit all its games. So that the first game it plays will be replayed forever.

That's easily fixed with another option of "max number of replays" and then it continues.

[hgm]

Perhaps this could be the only option: /replays=N , with default N=0. The rejected games could be saved on a file with a name derived from the file where the successful games are saved, by appending "_rejects" to that filename. The option would be persistent, and saved in the tournament file, so that tournaments that run simultaneously can use different settings for this option.