1: Classic RPG Save System
The first and most obvious application is the ability to store character stats/info in between plays of an RPG map. We can finally say goodbye to generating save codes that players have to remember. This new method does not have improved security though, as it is possible to manually edit local save data. (This might not be an issue if the file is encrypted or thoroughly hidden)
2: Advanced Player Ranking System
You can also now use DC's to store detailed player data (Games played, wins, total kills, total deaths, tier-based ranking, etc). Info like this could be useful to compare players in a competitve/MOBA environment. The possibility of save hacking means this wouldn't be a very secure system.
3: Map Admins
When privately testing a map, you could set a DC for yourself that is impossible to acquire through normal play. Thus, the you (the maker) will be the only person to posses this hardcoded DC (i.e. remove the trigger that made it). You can then program the map to identify a player with this DC and make them the "admin", allowing them to use special functions. The security on this one is better because a save hacker would need to know both the unit and the count of the admin DC.
4: Blacklist
If a player is being very rude or constantly trolling, you can now take higher action than a simple in-game ban. Assign a unique DC to these players, then have the map recognize them and drop them right at the start. The admin won't even need to be present to prevent blacklisted people from playing. Security is questionable since bypassing the blacklist only requires a file deletion, but this is better than nothing, I guess.
There are probably even more mechanics now possible thanks to SCDB. Share your thoughts with me.