Replies: 3 comments 1 reply
-
Here is my response: The logic for synthetic events is that some event tracking is a LOT more efficient if done on the client side. The best example is Conflict Zones. Uploading all related events and having them processed server side is a lot of overhead and introduces many more possible points of failure while the client has local access to the journal and can send out a single event rather than multiple journal entries. I suggest the prefix
In my opinion, I agree about different Events for Space and Ground since those are not that much related and have different effects. -- -- |
Beta Was this translation helpful? Give feedback.
-
I agree the prefix should be non client specific, and Not so sure about combining the main event and objectives. At the moment we track a CZ once a) the user has dropped into one and b) they have made a first kill. There is a separate proposal to change this to include kill counting, but that also comes with downsides as outlined in that proposal. Either way, objectives are completed at a different time to the main CZ. I would argue that as So for manual user entry, if you would be happy with the concept of decrementing via a “negative count” mechanism, we could achieve that with a separate event (bit clumsy and introduces event bloat) or with a |
Beta Was this translation helpful? Give feedback.
-
I got a proposal in the API definition. Didn't make the Synthetic_CZObjective or Synthetic_Scenario yet but I'd stick with roughly the same format. Those types Could include an optional type. |
Beta Was this translation helpful? Give feedback.
-
BGS-Tally, through its internal logic, infers and tracks various activities that are missing direct game journal entries. All tallied activity is included as a snapshot via the
/activities
API but some of these activities could also be useful via the/events
API to systems that consume the journal events stream.This proposal is to introduce the concept of synthetic events - i.e. events delivered to the
/events
API that do not directly correspond with game journal entries.BGST_
? - so as to:BGST_SpaceConflictZone
- Detail TBDBGST_SpaceConflictZoneObjective
- Detail TBDBGST_GroundConflictZone
- Detail TBDBGST_Scenario
- Detail TBDNote that BGS-Tally's CZ tracking is still not perfect as the game does not log CZ wins, so various journal events are used to determine whether you have fought at a CZ.
Open question: Do we send a synthetic event when the user manually tallies a CZ via the UI? What happens if the user 'untallies' (decrements) the CZs count?
Beta Was this translation helpful? Give feedback.
All reactions