Descriptive Problem Summary:
There seems to be some ussue when attempting to set game scores using world.hub_password or blank as the hub_password argument in procs such as SetScores() or GetScores().

Code Snippet (if applicable) to Reproduce Problem:
If you use this:


or:


Then the program will not be able to access the hub properly. But if I use this:


Then it works just fine. This of course, isn't ideal if you want to keep sensitive text strings out of the RSC.

Expected Results:
Any of the above code snippets should have been able to access the hub scores.

Actual Results:
Only the last value, where the hub password is actually entered in plain text format, allowed the program to access the hub scores. I'm making the assumption that the hub_password values might be getting sent to the hub in md5 format or something.

Does the problem occur:
Every time? Yes
In other games? I tested it a game working with its own hub entry and working with the hub entry of another game.
In other user accounts? Haven't tried.
On other computers? Haven't tried.

Workarounds:
You can generate the password dynamically using a proc as the hub_password argument instead. That will keep the hub password out of the RSC.