userAttributes and appAttributes

Hey @YJack!

with regards to your questions:

• AppConfig is related to what's in ConfigManager.appConfig. But AppAttributes and UserAttributes are used by the conditions in remote config rules. They're for you to create, if you don't need them, in the newer packages, you should be able to pass in null.
• Any public serializable field you put in your attributes structs can be used in rules for segmentation.
• Each request can have one user and app attribute struct, you could pass different structs into each request. There currently isn't a limit on the number of attributes.
• There's no way to currently clear the cache result, other than looking through the package source and removing the file where we write the cached results to. Out of curiosity, what's your use case for wanting to clear the cache?

Hope those help, let me know if you have more questions!

 

Hi @YJack!
I am not 100% sure if I understand the clear cache use case so please correct me if I did not get it right,
but one way to ensure you got the remote data is to check for `ConfigOrigin.Remote` in configResponse after FetchConfigs(), and then apply your overwrites.
That would overwrite your cache file with new remote values, so there is no need to restart Unity or investigate the package source.
Of course, you can call FetchConfigs more than once within your session, if you have need for it.

From the docs:

Code (CSharp):

1. // Retrieve and apply the current key-value pairs from the service on Awake:
2. void Awake () {
3.  
4. // Add a listener to apply settings when successfully retrieved:
5. ConfigManager.FetchCompleted += ApplyRemoteSettings;
6.  
7. // Set the user’s unique ID:
8. ConfigManager.SetCustomUserID("some-user-id");
9.  
10. // Fetch configuration setting from the remote service:
11. ConfigManager.FetchConfigs(new userAttributes(), new appAttributes());
12.  
13. }
14.  
15.  
16. void ApplyRemoteSettings (ConfigResponse configResponse) {
17.  
18.     // Conditionally update settings, depending on the response's origin:
19.     switch (configResponse.requestOrigin) {
20.  
21.         case ConfigOrigin.Default:
22.             Debug.Log ("No settings loaded this session; using default values.");
23.             break;
24.  
25.         case ConfigOrigin.Cached:
26.             Debug.Log ("No settings loaded this session; using cached values from a previous session.");
27.             break;
28.  
29.         case ConfigOrigin.Remote:
30.             Debug.Log ("New settings loaded this session; update values accordingly.");
31.             enemyHealth = ConfigManager.appConfig.GetInt ("enemyHealth");
32.             assignmentId = ConfigManager.appConfig.assignmentID;
33.             break;
34.     }
35.  
36. }

 

As for this part, it's not something we support today, but if you could give me some more details on what you'd like to see and do with that, I can get it documented as a feature request on our end.

 

@YJack no worries!

I'm trying to better understand the use case you have above. Is that you want a key "XP" in Remote Config that you want to send down to players? Or do you want players to receive different values for keys based on how much XP they have?

 

Perfect, okay, so for that, here's what you'd probably want:

1. Add a variable to your userAttributes struct, like "totalXp" and set that before fetching your config.
2. In your config, set up whatever variables you'd want changed based on the XP of the player, and implement the runtime Remote Config code in your project.
3. You can create rules, where in the condition you can do things like "user.totalXp > 0 && user.totalXp <= 1000" let's say. This rule will now go into effect for users whose xp is between 0 and 1000. In the rule, you can specify your override values that you'd like this user group to receive.
4. Repeat the above steps with as many rules as you need for your user groups.

Hopefully this helps, but let me know if anything is unclear!