You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Following conversations on the Discord I have decided to start this RFC about adding pull rates to differents endpoints in the API :
The main goal is to allow developers use publically available card drop rates for multiple tools/games like a booster opening simulator.
Set definition
in /api/v2/{lang}/sets/{setId} :
the definition of the field would be the following
a record with the key being normal or godpack (there also seems to be semigodpack for physical sets)
in each elements the slots is an array with the index being the position of the card from the first to last to appear in a normal opening (not reversed)
each slots then contain a simple object that indicate that each chances has a certain probability to appear (in percent)
for the rate it will be the rate of appearance of the specific booster pack (ex: godpack is 0.5%)
like the set each cards would have a pullRates key that contains a Record of pack type with the following
rate: the rate of appearance of the pack slots: the rate of appearance of this specific card in the booster pack total_slots: the same as slot but with a pre calculation based on the rate (not sure to keep as it's easy to repeat from the developper code by just multiplying the slot rate by the rate slots[number] * rate = totalSlots[number])
interfaceCard{
...
pullRates?: Record<string,{rate: number/** * raw rate ignoring the type rate */slots: Array<number>/** * rate including the base rate */totalSlots: Array<number>}>}
Pull rates
Following conversations on the Discord I have decided to start this RFC about adding pull rates to differents endpoints in the API :
The main goal is to allow developers use publically available card drop rates for multiple tools/games like a booster opening simulator.
Set definition
in
/api/v2/{lang}/sets/{setId}
:the definition of the field would be the following
a record with the key being
normal
orgodpack
(there also seems to besemigodpack
for physical sets)in each elements the
slots
is an array with the index being the position of the card from the first to last to appear in a normal opening (not reversed)each
slots
then contain a simple object that indicate that each chances has a certain probability to appear (in percent)for the
rate
it will be the rate of appearance of the specific booster pack (ex: godpack is0.5
%)JSON of the set
see the field
pullRates
Card definition
like the set each cards would have a
pullRates
key that contains a Record ofpack type
with the followingrate
: the rate of appearance of the packslots
: the rate of appearance of this specific card in the booster packtotal_slots
: the same as slot but with a pre calculation based on therate
(not sure to keep as it's easy to repeat from the developper code by just multiplying the slot rate by the rateslots[number] * rate = totalSlots[number]
)and in `/v2/{lang}/cards/{cardId}
json of the endpoint
See the field
pullRates
The text was updated successfully, but these errors were encountered: