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
Currently we have two proposals for how the slots in a pack are decided.
Slots are explicitly defined in the template
This is how it has been described in the design document
The template defines each slot in a pack explicitly
In the template a slot is given buckets (lists or ranges of IDs) to pull from
Slots are deduced from the template
This is how it has been currently (initially) implemented
In the template there is no notion of a pack slot
The template describes buckets (lists or ranges of IDs) and how many items to pick from each (forming the slots)
Pros/cons
Way 1
Pros
Simple mapping of the concept of rarity to buckets (each bucket can be a self contained rarity tier)
Cons
If there is a need for large packs (for example packs with 100 slots), the template will have to reflect this and become quite large as well (as each slot needs to be defined in the template)
Way 2
Pros
Pack size does not affect the size of the template
Cons
The concept of rarity is mingled as rarity tiers need to be mixed in buckets
So it kind of boils down the whether or not there will be a need for large packs and how the concept of rarity is handled.
The text was updated successfully, but these errors were encountered:
Currently we have two proposals for how the slots in a pack are decided.
Slots are explicitly defined in the template
Slots are deduced from the template
Pros/cons
Way 1
Pros
Cons
Way 2
Pros
Cons
So it kind of boils down the whether or not there will be a need for large packs and how the concept of rarity is handled.
The text was updated successfully, but these errors were encountered: