Hello Stefano,
I’m getting back to a topic we mentioned earlier because as I continued testing the program I realized that the subject deserves a bit more depth, especially now that you’ve implemented the fantastic feature for massively updating the Elo of registered players from the FIDE lists (Standard, Rapid and Blitz). By the way, great job—this is such a convenient feature!
For individual tournaments, the fact that an unrated player is recorded with Elo “0” or “1399” is practically irrelevant for the board’s purposes, but in team events it can create confusion.
I’ll give you a numerical example to explain myself better. If a team has a 2000‑Elo player and an unrated (NC) player, is it more correct to consider the team’s average Elo as 1000 or 1700?
You can see there’s a huge difference. If an organizer must accept teams or calculate brackets based on a balanced average, a team with an average of 1000 (actually composed of a 2000 and a beginner) completely distorts the field values and skews the balancing criteria. An unrated player will likely play with a strength estimated between 1000 and 1300 points, not zero. Another practical case: in our tournament we have a player who has Blitz Elo but no Rapid. When we switch the event from Blitz to Rapid, the Elo adjustment function leaves him with his Blitz Elo; there are three options: keep the Blitz Elo, set it to 0, or set it to 1399. Each of these possibilities has pros and cons, but I honestly prefer 1399.
You’re absolutely right when you say that the worldwide FIDE standard for unrated players is “zero” (or rather, no rating) and that below 1400 they simply appear as unrated on the international list. However, for tournaments played under the FSI umbrella, 1399 is the golden rule for unclassified players. Moreover, leaving the Elo field open in online registration carries a real risk of having non‑uniform data (some register with 0, others with 1399 depending on what comes to mind).
Since the new FIDE list update function “reads” and corrects ratings based on the type (Standard/Rapid/Blitz), do you think it would be feasible to integrate a special handling for these cases?
I’m throwing in a couple of ideas on how this could be structured at the program logic level, keeping the software’s international footprint while preserving local specifics:
- Fictitious calculation value (Default Rating for Unrated): Allow the program to keep the “Unrated” flag in the database (or retain the official 0 FIDE), but add an option in the tournament settings such as: “Assign fictitious Elo to Unrated players for average calculations.” If the organizer sets 1399, the program will use that value to compute team averages or sorting, without contaminating the player’s real data.
- During list updates: When the function queries the FIDE list and doesn’t find the player (or finds them with a missing/zero rating), it could act based on a tournament configuration parameter (e.g., If not present in FIDE list → Set Elo to X or Keep Unrated).
What do you think? I’d like to know if, in your view, the topic deserves further exploration, or if you have an alternative approach in mind to avoid the problem of skewed averages in team events (which could also be extended to individual ones).
Thanks and goodbye,
Claudio



