March 25, 2024

scry pricing guide

Today’s guide that no one asked for: Pricing scries for other people

When recommending scries to other people, you should be aware of their budget. Sometimes the person will specify their budget (e.g. “no gem genes please”), but even if they don’t, you can make a strong educated guess.

  • Factors indicating high budget:
  • Dragon has personal/sentimental importance (e.g., progen, progen firstborn, special date dragon. alternately, maybe the person mentions their importance, e.g.: “this was one of my first dragons and I really don’t want to exalt them but I don’t like them any more”)
  • Dragon is objectively valuable (e.g., 2L, low-digit ID, Roundsey, g2 imp, valuable lineage dragon (situational; for instance, g3 Naomis are $$$$, whereas I punt g3 Razaneis out the door for pennies))
  • Dragon is on a scatter journey or is being considered for one (indicates the player is willing to spend thousands of gems on them)
  • Player is wealthy (indicators: g1 gem breeds, UMAs, outfits have the vibe of “this person spends too much time on this site” (affectionate))
  • Factors indicating low budget:
  • Player is new
  • Even if player has an older join date, player’s lair looks new (e.g., all dragons are in a single tab called “Main,” often with ungened progens as the first two dragons; lair has no apparent organization; outfits have the vibe of “I have exactly three pieces of apparel and I might as well put them on someone” (also affectionate))
  • Player shows lack of familiarity with FR slang (e.g., referring to their progen as “my starting dragon”)
  • Player is uncertain about whether to keep the dragon in question. Common situations:
  • Primal/multigaze in fodder nest
  • Cute fodder generally
  • Mass hatch (this overrides “special date dragon” because if you have a couple dozen special date dragons, you probably aren’t going to heroic lengths to save any particular one)
  • Lair cleanout/”who should I keep?”

Written by Achaius

141 Views
Log in to Like
Log In to Favorite
Share on Facebook
Share on Twitter
Comments

You must be signed in to post a comment!