> For the complete documentation index, see [llms.txt](https://docs.speedstar.io/en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.speedstar.io/en/gameplay/lands/ranch/ranch-popularity-and-goodwill.md).

# Ranch Popularity and Goodwill

The concept of ‘popularity’ is an important one within the game, and this can be improved. Within the game it needs to be thought of as similar to the business term ‘goodwill’. If your horse wins races, then more people will visit your ranch and the more successful and popular your ranch will become. As its reputation enhances, so will your ranch’s goodwill. There are **NFT** facilities available in the game that also improve your ranch’s popularity and goodwill when they are staked. These can be gained by winning races or by undertaking tasks etc. Please note that **NFTs** are not all the same, and their rarity varies. Consequently, please think of ‘popularity’ and ‘goodwill’ as a statistic that can be increased, similar to a level of experience, and one that has a proportional relationship to your passive token gains. In effect, ranch goodwill x ranch popularity = an increase in your yield multiplier and therefore more passive income.

{% content-ref url="/pages/jt5xSwzuMMnbwtD0lK5e" %}
[SPEED Tokens](/en/speed-star/tokenomics/speed-tokens.md)
{% endcontent-ref %}

### Ranch popularity

Your passive $SPEED income on the Ranch is closely tied to your popularity value, you can increase your popularity by placing various buildings on your ranch. You could also join special events that will increase your popularity multiplier for a certain amount of time.

<table><thead><tr><th>Ranch score</th><th width="200">Multiplier</th></tr></thead><tbody><tr><td>0 - 1,000</td><td>1x</td></tr><tr><td>1,001 - 5,000</td><td>1.1x</td></tr><tr><td>5,001 - 10,000</td><td>1.2x</td></tr><tr><td>10,001 - 20,000</td><td>1.3x</td></tr><tr><td>20,001 - 30,000</td><td>1.4x</td></tr><tr><td>30,001 - 40,000</td><td>1.5x</td></tr><tr><td>40,001 - 50,000</td><td>1.6x</td></tr><tr><td>50,001 - 60,000</td><td>1.7x</td></tr><tr><td>60,001 - 70,000</td><td>1.8x</td></tr><tr><td>70,001 - 80,000</td><td>1.9x</td></tr><tr><td>80,001 - 99,999</td><td>2.0x</td></tr><tr><td>100,000+</td><td>2.5x</td></tr></tbody></table>

The amount of reward $SPEED per Ranch Score for everyone is the same as the pool.\
If players want to get more rewards, this can be done by increasing the farm's goodwill \
to get more Bonus Multiplier. This will be multiplied by the Ranch Score for example:

* The displayed Ranch Score is 8,855.
* The Multiplier is 1.2x, which means the Ranch Score is 1.2 \* 8,855 = 10,626.

Therefore, the rewards received will increase as the Ranch Score is increased with the Bonus Multiplier.\
It means getting more Ranch Score = getting more Bonus Multiplier as well.

### Visitor

When people come to visit the ranch, you will receive increased popularity for a certain amount of time.  

| Visitor      | Effect time     | Cooldown time   |
| ------------ | --------------- | --------------- |
| +10 / Player | 12 hrs / Player | 24 hrs / Player |

\*100 players total, can visit your ranch per day.  


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.speedstar.io/en/gameplay/lands/ranch/ranch-popularity-and-goodwill.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
