> For the complete documentation index, see [llms.txt](https://docs.flatredball.com/flatredball/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flatredball.com/flatredball/tutorials/beefball/scoring-hud.md).

# Scoring Hud

### Introduction

This tutorial covers creating a HUD object which displays the scores of each player.

### Creating a ScoreHud Entity

First we'll create an Entity to store all of our scoring information. We could place all of our HUD objects directly in the Screen, but this approach can result in a large number of objects in the GameScreen, making it difficult to maintain. We'll create a "Hud" entity to keep all HUD objects organized. To do this:

1. Select the **Quick Actions** tab
2. Click the **Add Entity** button
3. Enter the name **ScoreHud**
4. Click **OK**

![](https://951240982-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M_fye9Ufg3vzJxwX5Hk%2Fuploads%2Fgit-blob-5edc961834fa47eb8c7fdf02536aec1fc3b78857%2F2021-07-img_60fdd1776370c.png?alt=media)

### Creating the ScoreHud Text objects

For the ScoreHud we'll define the Text objects in Glue (just like we defined the body of the Puck in Glue). To do this:

1. Select **ScoreHud**
2. Select the **Quick Actions** tab
3. Click the **Add Object to ScoreHud**
4. Select **Text** as the type
5. Enter the name **Team1Score**
6. Click **OK**

   ![](https://951240982-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M_fye9Ufg3vzJxwX5Hk%2Fuploads%2Fgit-blob-5350412449fa8b5ab88dd35bc815dc26dc037fb2%2F2021-07-img_60fdd21643893.png?alt=media)
7. Repeat the steps above to create another Text object called **Team2Score**
8. Repeat the steps above to create another Text object called **Team1ScoreLabel**
9. Repeat the steps above to create another Text object called **Team2ScoreLabel**

You should now have 4 Text objects:

![](https://951240982-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M_fye9Ufg3vzJxwX5Hk%2Fuploads%2Fgit-blob-7dfe00dee52455afee5bc9c0b811ea6b2efeb13a%2F2021-07-img_60fdd24f94751.png?alt=media)

Now we'll change the following variables on the Text objects in Glue. Select the following Text objects and set the variables as defined below:

**Team1Score**

* DisplayText = "99"
* X = -150
* Y = 270

**Team2Score**

* DisplayText = "99"
* X = 180
* Y = 270

**Team1ScoreLabel**

* DisplayText = "Team 1:"
* X = -205
* Y = 270

**Team2ScoreLabel**

* DisplayText = "Team 2:"
* X = 124
* Y = 270

To add the ScoreHud to the GameScreen:

1. Select the **ScoreHud**
2. Select the **Quick Actions** tab
3. Click the **Add ScoreHud Instance to GameScreen** button

![](https://951240982-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M_fye9Ufg3vzJxwX5Hk%2Fuploads%2Fgit-blob-b1e867cf089395e7017493cdee38a3d7b23d0354%2F2021-07-img_60fdd305ee7ac.png?alt=media)

You should now see everything showing up correctly in your game

![Screenshot of in-progress BeefBall game showing player one and player two score HUD at the top.](https://951240982-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M_fye9Ufg3vzJxwX5Hk%2Fuploads%2Fgit-blob-0723c34a4ff42877993c26f3c0501a7d8513ce46%2F2021-05-img_609de61e7870f.png?alt=media)

### Conclusion

Now we have a score HUD that shows up when the game plays, but it doesn't react to scored goals. The next tutorial adds the necessary logic to have it react to scored goals.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.flatredball.com/flatredball/tutorials/beefball/scoring-hud.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.