# FAQs **How does ScoutX determine the end-of-season price of a Player Token?** We use an [**Oracle**](broken://pages/KyJZKypklAl9nexwnEfE) to determine the end-of-season price of a player token. Therefore, even if the price is higher or lower than the **actual** earnings, the end price will be the outcome of the prediction and will benefit whoever was on the winning side (long or short) **What happens if a player is injured or retires?** Nothing you need to worry about - the prices will adjust accordingly. Essentially the price for this player’s token should stabilize at their earnings to date, with little or no trading happening beyond that point. Traders may simply sell all tokens for these players back to the AMM. **What happens if a tournament gets canceled?** Player tokens may automatically trade at a lower price - it’s the same as no player getting any winning in a given tournament, therefore you can either choose to do nothing or to sell your tokens back to the AMM. **What happens if a new player is introduced mid-season?** A player introduced mid season has all the same mechanics and behavior as a player introduced earlier. Their long/short token prices can be traded from when they are introduced till the last trading time, and redeemed at the prices determined at end of the season based on their earnings/score. **Why do Long and Short tokens have different prices?** The long token price is proportional to the player's final score/earnings. The short token is a complementary pair, its price is the max token price minus the price of the long token (ignoring transaction fees/spread). **Why is my final transaction price different from the price I initially bought/sold a token at?** This typically happens due to slippage that may occur when buying/selling tokens that are either volatile or have less liquidity. To understand more about slippage, please visit this [**guide here**](https://www.nasdaq.com/articles/dealing-with-slippage-in-cryptocurrency) --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://litepaper.scoutx.io/how-it-works/faqs.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.