This whitepaper aims to provide an in-depth understanding of the alpha drop rate and card distribution for the ‘Near Monsters’ game. This information is particularly pertinent for the initial release of 25,000 packs, each containing 5 cards.


Table of Contents

  1. Number of Distinct Cards
  2. Drop Rate Mechanics
  3. Expected Distribution
  4. Per Card Distribution
  5. Testnet

Number of Distinct Cards

The game features a variety of unique cards within each category. The number of distinct cards for each type is:

  • Land: 9 distinct cards
  • Rare: 51 distinct cards
  • Uncommon: 47 distinct cards
  • Common: 82 distinct cards

You can view all of the cards in your inventory or at the card list

Drop Rate Mechanics

The drop rate for cards in ‘Near Monsters’ is governed by a pseudo-random number generator that produces a ‘roll’ between 0 and 255, inclusive. Based on the value of this roll, a card from one of four categories—Land, Rare, Uncommon, or Common—is selected. The mechanics can be summarized as follows:

  • Land: Roll < 8

  • Rare: 8 <= Roll < 35

  • Uncommon: 35 <= Roll < 96

  • Common: 96 <= Roll <= 255

  • Land: 3.125%

  • Rare: 10.547%

  • Uncommon: 23.828%

  • Common: 62.5%

Expected Distribution

Given that each pack contains 5 cards and there will be a total of 25,000 packs, the overall distribution for each category at 100% open rate is expected to be:

  • Land NFT cards: Approximately 3,906
  • Rare NFT cards: Approximately 13,184
  • Uncommon NFT cards: Approximately 29,785
  • Common NFT cards: Approximately 78,125

True drop rates are random, this is only an approximation.

Per Card Distribution

Assuming uniform distribution within each category, each type of card is expected to appear as follows(100% open rate):

  • Each Land NFT card: Approximately 434
  • Each Rare NFT card: Approximately 259
  • Each Uncommon NFT card: Approximately 634
  • Each Common NFT card: Approximately 953


Land staking and gameplay is planned but not implemented.

The card stats are subject to balance updates.


You can test this on NEAR testnet at "(testnet)↗"