692 of the 805 Adopt Me pets on the wiki's Pets page carry the limited tag. That is not a small exception list. It means any value table that gives limited pets a bonus is mostly a table of bonuses, not a table of pets.

When I rebuilt the value list for PetTradeCalc, the rarity scale was easy: Common 1, Uncommon 2, Rare 4, Ultra-Rare 8, Legendary 16, powers of two so that a Neon (×4) and a Mega Neon (×16) stay whole numbers. Adding a limited step of ×1.5, rounded, looked equally harmless. 16 becomes 24, 8 becomes 12, 6 for Rare, 3 for Uncommon, 2 for Common.

Three things broke, and all three are visible on the page today.

Rounding up invents an equality

A limited Common pet scores 2. So does a permanent Uncommon. That is not a judgment about the two pets being worth the same. It is 1 × 1.5 = 1.5 rounded up to the nearest whole number.

The table has a "Same RI" column that pairs each pet with another pet at the same score. It is a shortcut, not advice. On the Common and Uncommon tiers it will pair pets across the limited line, and a reader who takes the pairing literally is reading a rounding artifact as a market statement.

I left the collision in place. The alternative was fractions, which turns the table into decimals and makes the calculator's output harder to check by hand. Trading is done in whole pets and players compare whole numbers. What I changed instead is the wording: the column says the scale treats these two as equal, not that they are worth the same.

A 10% band against integer values puts the edge in an odd place

The calculator calls a trade fair when both sides are within 10% of the larger side. The band is relative on purpose; an absolute point tolerance fails at both ends of the table, where 1 against 2 is a 100% difference and 100 against 110 is 10%.

Relative still has to survive integers. Take a limited Legendary at 24. A trade of 24 for 22 is 8.3% apart and scores fair. A trade of 24 for 21 is 12.5% apart and scores a loss. The boundary sits between two adjacent integers, so one point of RI flips the verdict. If I had used 12.5% as the tolerance instead of 10%, 21 would pass too, and the entire band would sit one point looser without anyone noticing.

The visible consequence is that at the top of the scale a single pet is a meaningful step, while at the bottom the same relative band spans several pets. That is arithmetic, not a bug. The page prints the rule under the table so a reader can see why 21 and 22 land on different sides.

The smallest tier absorbs the rounding error

Compounding is where a half point grows. Neon multiplies by 4, Mega by 16, and those multipliers apply after the limited step, so a limited Legendary Neon is 96 and a Mega is 384, both exactly 1.5× the permanent version at 64 and 256.

The Common tier is the exception. A permanent Common is 1, so its Neon is 4 and its Mega is 16. A limited Common is 2, so its Neon is 8 and its Mega is 32. Had the limited step been applied without rounding, those would be 6 and 24. The rounding adds 33% to the smallest pets and nothing to the largest, because 1.5 hits a whole number at every tier above Common except Uncommon (1.5 × 2 = 3, exact).

I do not have a fix that keeps whole numbers and removes the distortion. What I can do is show it: the table has RI, Neon and Mega columns for every pet, so the reader sees all three at once instead of a single number that hides the tier it came from.

One data file, two consumers

The table and the calculator read the same JSON. The list page renders 805 rows from it and the calculator scores trades from it. That sounds like an implementation detail until the two drift. Earlier versions of this project had a numbers file for the calculator and a hand-built table for the list, and the day the limited step changed, one of them kept the old rule for a few hours.

The dataset also carries the source revision: Adopt Me Wiki Pets page, revision 475127 dated 2026-10-23, 66 Common, 104 Uncommon, 158 Rare, 230 Ultra-Rare, 247 Legendary. If the wiki changes, the next build changes one file and both pages move together. The date sits in the page copy, not in a footer, because a values list without a revision date is a claim without a timestamp.

What the number still cannot see

Two limited Legendaries both show 24. A Shadow Dragon and a Golden Griffin are not the same trade, and no multiplier on rarity will fix that. Demand, how long a pet has been out of the game's eggs, whether it is rideable or flyable, and how easy it is to resell sit outside the formula. The limited step only reads availability.

So the list answers a narrower question than people expect: given two sides of a trade, is the arithmetic close, and what would make it closer. It does not answer what a specific trader will accept. The page says that above the table, and the FAQ repeats it, because the failure mode here is not a wrong number. It is a right number read as a price.

If you want to check the work: the full Adopt Me pet values list is sortable, marks limited pets inline, and prints the scale and the rounding rule under the table. Individual pages for the most traded pets, starting with Cryptid, show the same numbers with the combos that score fair against them. The trade calculator takes any two sides and shows the percentage instead of a verdict alone.