If you use overwolf.games.events.setRequiredFeatures, you never get success: true in the response. However, overwolf.games.events.onNewEvents and overwolf.games.events.onInfoUpdates2 always work even though setting required features fails.
killFeed is always fired twice.
You can easily reproduce both issues using the sample app.
@surgeon regarding the first issue - is that a problem for you, or are you wondering why it’s working although setRequiredFeatures returns with success: false?
Regarding the second issue - it looks like a bug. But we are still checking it.
regarding the first issue - is that a problem for you, or are you wondering why it’s working although setRequiredFeatures returns with success: false?
Yes, it is currently a problem. We are using a wrapper with extended logic for all Overwolf APIs in more than 6 apps now and we expect the same behavior in all supported games. If setRequiredFeatures always returns false in Splitgate, the wrapper will work in all games except Splitgate.
If possible, we would like it to return true in Splitgate to keep things consistent. If not, we will try to remove setRequiredFeatures for Splitgate specifically to avoid the issue.