Skip to content

Commit

Permalink
chore: Deprecate gems for removal
Browse files Browse the repository at this point in the history
Looking up the amount of gems a player has will now always return 0 until such a time that we remove it. We've had a fair few complaints that it allows people to "spy" on when/how many purchases are being made for players and that's not something we want.

Also fixes a typo in the docs for chroma packs.
  • Loading branch information
kezz authored Dec 13, 2024
1 parent e1ac9f1 commit 5634c79
Showing 1 changed file with 2 additions and 1 deletion.
3 changes: 2 additions & 1 deletion schema.graphqls
Original file line number Diff line number Diff line change
Expand Up @@ -179,7 +179,7 @@ type CosmeticOwnershipState {

"The Chroma Packs that have applied to this cosmetic, if it is colorable."
chromaPacks: [String!]
@spectaql(options: { key: "example", value: "[\"oceanic\", \"natural\"" })
@spectaql(options: { key: "example", value: "[\"oceanic\", \"natural\"]" })

"The number of Royal Reputation donations that have been made of this cosmetic, if it can be donated."
donationsMade: Int
Expand All @@ -192,6 +192,7 @@ type Currency {

"The number of gems the player currently has."
gems: Int!
@deprecated(reason: "Deprecated for removal. Will always return 0 until removal.")

"The number of Royal Reputation the player currently has."
royalReputation: Int!
Expand Down

0 comments on commit 5634c79

Please sign in to comment.