Fixed duplicate check on game id sync

GBM/Managers/mgrMonitorList.vb

@@ -899,10 +899,10 @@ Public Class mgrMonitorList
             If Not hshCompareTo.Contains(oFromItem.ID) Then
                 For Each oToItem In hshCompareTo.Values
                     'Strip all special characters and compare names
-                    If Regex.Replace(oToItem.Name, "[^\w]+", "") = Regex.Replace(oFromItem.Name, "[^\w]+", "") Then
+                    If Regex.Replace(oToItem.Name, "[^\w]+", "").ToLower = Regex.Replace(oFromItem.Name, "[^\w]+", "").ToLower Then
                         'Ignore games with duplicate names
                         If Not hshSyncIDs.Contains(oFromItem.ID) Then
-                            hshSyncIDs.Add(oToItem.ID, oFromItem.ID)
+                            hshSyncIDs.Add(oFromItem.ID, oToItem.ID)
                         End If
                     End If
                 Next
@@ -911,8 +911,8 @@ Public Class mgrMonitorList
 
         For Each de As DictionaryEntry In hshSyncIDs
             hshParams = New Hashtable
-            hshParams.Add("MonitorID", CStr(de.Value))
-            hshParams.Add("QueryID", CStr(de.Key))
+            hshParams.Add("MonitorID", CStr(de.Key))
+            hshParams.Add("QueryID", CStr(de.Value))
             oParamList.Add(hshParams)
         Next
 

GBM/readme.txt

@@ -20,6 +20,7 @@ All Platforms:
 	- Game ID is now used to name game backup files and folders.
 	- Game Name can now contain any character.
 	- When a game is deleted via Game Manager (or sync), all backup manifest entries for that particular game are now deleted. The backup files themselves are not.
+	- The Game Manager now syncs changes to the remote database immediately, instead of only when closed.
 - Core Design Changes (Features)
 	- The "Enable Sync" feature is now mandatory and the option been removed from Settings.
 	- The "Clean Local Manifest" feature has been removed.  It is no longer required because manfiest entries can no longer be orphaned.  Existing orphaned entries will be removed during the v1.1.0 database upgrade.