adding campaign_id on result for get-drops API-call
add campaignid to the drops result on the get drops Entitlements API-call - so we don't need the EventSub call anymore (which only contains the campaignid for an entitlement)
with that, we have a good fallback-solution (if EventSub isn't fired) and we can re-use rewards from the manager.
The next step, to allow using the same rewarduniqueid multiple times in the campaign would be to add a "task-identifier" to eventsub and also to this api get-call.
dschi_ shared this idea