{"id":79183,"date":"2018-06-07T13:24:00","date_gmt":"2018-06-07T13:24:00","guid":{"rendered":"https:\/\/www.red-gate.com\/simple-talk\/?p=79183"},"modified":"2021-07-29T19:44:13","modified_gmt":"2021-07-29T19:44:13","slug":"using-unity-ui-and-c-to-create-a-tic-tac-toe-game","status":"publish","type":"post","link":"https:\/\/www.red-gate.com\/simple-talk\/development\/dotnet-development\/using-unity-ui-and-c-to-create-a-tic-tac-toe-game\/","title":{"rendered":"Using Unity UI and C# to Create a Tic-Tac-Toe Game"},"content":{"rendered":"

The series so far:<\/h4>\n
    \n
  1. Introduction to Game Development with Unity and C#<\/a><\/li>\n
  2. Using C# Functions in Your Animations<\/a><\/li>\n
  3. Procedural Generation with Unity and C#<\/a><\/li>\n
  4. Pathfinding with Unity and C#<\/a><\/li>\n
  5. Extending the Unity Editor with C#<\/a><\/li>\n
  6. Using Unity UI and C# to Create a Tic-Tac-Toe Game<\/a><\/li>\n<\/ol>\n\n

    Creating a user interface (UI) is undeniably important for your video game projects. The UI is responsible for displaying information to the player like health, ammo, and score. Without easy access to that information, games can fall apart very quickly. Just as important as displaying that info is updating it as the player plays. If the player earns ten points, then the UI needs to reflect that and update the score currently present on the screen.<\/p>\n

    Here, you’ll be using Unity’s UI in a different way. Rather than display health and score, you will instead utilize the UI to create a playable game of Tic-Tac-Toe (also sometimes called noughts and crosses or Xs and Os), and of course you will use C# code to do it. The aim of this project is to demonstrate how, through code, you can manipulate UI elements to do whatever you desire. A grid will be layed out for the game, and from there buttons will be added to the grid. These buttons will act as the playable spaces for the Tic-Tac-Toe game.<\/p>\n

    Setting Up<\/h2>\n

    As with all projects, the first thing you’ll have to do is create a new project. Click the New<\/em> button at the top of Unity’s project management window as shown in Figure 1.<\/p>\n

    <\/p>\n

    Figure 1: Creating a new project.<\/p>\n

    Name your project TicTacToe <\/em>and be sure to set it as a 2D project. This project can just as easily work as a 3D project, but this example will be in 2D for the entire duration. After you’ve done this, set a path for your project and click Create project<\/em> when you’re ready. Figure 2 shows the final project setup screen before clicking Create project<\/em>.<\/p>\n

    <\/p>\n

    Figure 2: Project setup screen.<\/p>\n

    Once Unity has created the project, the very first thing you need to do is go to the Hierarchy <\/em>window and select Create->UI->Panel <\/em>to create a new panel. While you’re at it, double click the new Panel <\/em>object to center the scene view on the panel. Figure 3 shows how to create a new panel.<\/p>\n

     <\/p>\n

    <\/p>\n

    Figure 3: Creating a new UI panel.<\/p>\n

    Go ahead and name this object line <\/em>then select the box to the far left of the Inspector <\/em>window as shown in Figure 4.<\/p>\n

    <\/p>\n

    Figure 4: Naming the object and selecting the anchor selection box.<\/p>\n

    This is the object’s ‘anchor,’ which is responsible for keeping the UI element at a certain point on the screen regardless of the size of the user’s screen. It’s useful whenever you need to make sure the UI will look the same from one screen to the next. In this case, the line <\/em>object is set to stretch both horizontally and vertically to the ends of the screen, but that’s not very useful for a game of Tic-Tac-Toe. Select the center anchor option to anchor the line <\/em>object to its relative center as seen in Figure 5.<\/p>\n

    <\/p>\n

    Figure 5: Setting an object’s anchor to center.<\/p>\n

    Next, the size of the line <\/em>object needs to be set. Under the Inspector <\/em>window in the Rect Transform <\/em>component set the object’s Pos Y <\/em>value to -5, its Width <\/em>to 18, and its Height <\/em>to 274. Figure 6 shows the different fields to change and their values.<\/p>\n

    <\/p>\n

    Figure 6: Setting the Pos Y, Width, and Height <\/em>of the line object.<\/p>\n

    Duplicate the object three times to bring you to a total of four line <\/em>objects. Once you have these objects created, you’ll need to adjust the position and sizes of each line <\/em>object using its Rect Transform <\/em>component to make a grid to play in. Table 1 shows each line <\/em>object’s properties to set and what value to set them to.<\/p>\n

    ObjectPos XPos YWidthHeight<\/p>\n\n\n\n\n\n\n
    \n

    line<\/p>\n<\/th>\n

    		\n

    0<\/p>\n<\/td>\n

    		\n

    -5<\/p>\n<\/td>\n

    		\n

    18<\/p>\n<\/td>\n

    		\n

    274<\/p>\n<\/td>\n<\/tr>\n

    \n

    line (1)<\/p>\n<\/th>\n

    		\n

    110<\/p>\n<\/td>\n

    		\n

    -5<\/p>\n<\/td>\n

    		\n

    18<\/p>\n<\/td>\n

    		\n

    274<\/p>\n<\/td>\n<\/tr>\n

    \n

    line (2)<\/p>\n<\/th>\n

    		\n

    56<\/p>\n<\/td>\n

    		\n

    52.5<\/p>\n<\/td>\n

    		\n

    296<\/p>\n<\/td>\n

    		\n

    19<\/p>\n<\/td>\n<\/tr>\n

    \n

    line (3)<\/p>\n<\/th>\n

    		\n

    56<\/p>\n<\/td>\n

    		\n

    -52.5<\/p>\n<\/td>\n

    		\n

    296<\/p>\n<\/td>\n

    		\n

    19<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

    Table 1: The line objects size and coordinates.<\/p>\n

    With the grid created, create a UI button by using the Create <\/em>menu from before, selecting UI <\/em>and then Button<\/em>. Figure 7 shows you where to find this option.<\/p>\n

    <\/p>\n

    Figure 7: Creating a new button.<\/p>\n

    Name this button Space<\/em> and then click the arrow next to the name of the object in the Hierarchy<\/em> like in Figure 8.<\/p>\n

    <\/p>\n

    Figure 8: Expanding the Space object to reveal its child Text object.<\/p>\n

    This will reveal the Text <\/em>object attached to the button. Select Text <\/em>and then find the Text <\/em>component under the Inspector <\/em>window. Once found, clear all text in the Text <\/em>field so that no text appears on the newly created button. Figure 9 shows where to find this.<\/p>\n

    <\/p>\n

    Figure 9: The Text <\/em>field.<\/p>\n

    From there set the font size to 36 and make sure its alignment is set exactly in the center of the button like in Figure 10.<\/p>\n

    <\/p>\n

    Figure 10: Setting different properties of the Text <\/em>component.<\/p>\n

    With the Text <\/em>object done, select the Space <\/em>object from the Hierarchy <\/em>and go to the Rect Transform <\/em>component. Set the Pos X<\/em> value to -50, Pos Y <\/em>to 100, Width <\/em>to 75, and Height <\/em>to 70. The object’s Rect Transform <\/em>should now look like the one shown in Figure 11.<\/p>\n

    <\/p>\n

    Figure 11: Space’s Rect Transform <\/em>properties.<\/p>\n

    And your button should now also be set in the upper left corner of your grid like in Figure 12.<\/p>\n

    <\/p>\n

    Figure 12: The scene so far.<\/p>\n

    Now is not quite the time to lay out the rest of the buttons, as there are things you’ll need to do first that will ultimately make development easier for you. You will come back to laying out the different spaces on the grid after the code is complete. For now, create a new panel using the same Create <\/em>menu as before. Name this panel GameOver Panel <\/em>and set its anchor to the center of the screen. Once that’s done, adjust its size and position according to Figure 13.<\/p>\n

    <\/p>\n

    Figure 13: GameOver Panel’s Rect Transform <\/em>properties.<\/p>\n

    After that’s done, you need to change its color a bit to help make it stand out from all the rest of the UI. Under the Image <\/em>component select Color <\/em>like in Figure 14.<\/p>\n

    <\/p>\n

    Figure 14: Setting a new color for the GameOver Panel<\/p>\n

    In Figure 15 a green color was chosen, but of course you may use whichever color you want. Keep in mind that if you use black as the color, you’ll need to later change the color of a text object you’ll be creating in a moment so that said text is actually visible.<\/p>\n

    <\/p>\n

    Figure 15: Picking a color.<\/p>\n

    Once your color is chosen, right click on the GameOver Panel <\/em>object and select UI->Text <\/em>to create a new Text <\/em>object. Since you created the Text <\/em>object in this way Unity will automatically assign the new object as a child of GameOver Panel<\/em>, which is exactly what is needed. Figure 16 shows where to find the option to create the Text <\/em>object.<\/p>\n

    <\/p>\n

    Figure 16: Creating a new Text <\/em>object as a child of GameOver Panel.<\/p>\n

    With the new Text <\/em>object selected, change the following values in the Rect Transform <\/em>and Text <\/em>components.<\/p>\n

      \n
    • Rect Transform->Pos Y: <\/em>-3<\/li>\n
    • Rect Transform->Width: <\/em>295.5<\/li>\n
    • Rect Transform->Height:<\/em> 68<\/li>\n
    • Text->Text:<\/em> Victory Text<\/li>\n
    • Text->Font Size:<\/em> 36<\/li>\n
    • Text->Alignment:<\/em> Center<\/li>\n<\/ul>\n

      When you’re done the Text <\/em>object should look like the one in Figure 17.<\/p>\n

      <\/p>\n

      Figure 17: The finished Text object.<\/p>\n

      Next another button will be made. This button will restart the game whenever it is clicked on, but you’ll set it up so it will only appear once the game is done, whether there’s a winner or if it ends in a tie. Using the same Create <\/em>menu as before, create a new button and call it RestartGame<\/em>. Then, set the following Rect Transform <\/em>values:<\/p>\n

        \n
      • Pos X: <\/em>-250<\/li>\n
      • Pos Y:<\/em> 70<\/li>\n
      • Width:<\/em> 200<\/li>\n
      • Height:<\/em> 70<\/li>\n<\/ul>\n

        After that, select RestartGame’s Text <\/em>object and set the following properties in the Text <\/em>component:<\/p>\n

          \n
        • Text: <\/em>Play again?<\/li>\n
        • Font Size:<\/em> 24<\/li>\n
        • Alignment:<\/em> Center<\/li>\n<\/ul>\n

          Finally, create a new empty object by going to Create->Create Empty<\/em> like in Figure 18.<\/p>\n

          <\/p>\n

          Figure 18: Creating the GameController object.<\/p>\n

          Name this object GameController<\/em>. This object will be the one that takes care of almost all the code for the game. Speaking of the code, it’s now time to create some scripts. In your Assets <\/em>window right click and select Create->C# Script <\/em>like in Figure 19.<\/p>\n

          <\/p>\n

          Figure 19: Creating a new C# script.<\/p>\n

          Name this script GameController<\/em>. Remember that you must give it the GameController <\/em>name immediately after creating the script. If you click away from the script without giving the script its name, the wrong class will be created in Visual Studio which can cause problems later. Immediately after creating that script, create another script and call it Space<\/em>. Once this is done, your Assets <\/em>window should look like the one in Figure 20.<\/p>\n

          <\/p>\n

          Figure 20: The current Assets <\/em>window.<\/p>\n

          It’s now time to write the code that will make this game run! Begin in the GameController <\/em>script by double clicking it in the Asset<\/em> window.<\/p>\n

          The Code<\/h2>\n

          The GameController <\/em>script will be responsible for the majority of the game’s logic. There’s a couple tasks that need to be done before creating this script. First, comment out or delete the Update<\/strong> function as it will be of no use to you in this project. Next, at the top of the script just underneath the line that says using UnityEngine<\/strong> add the following line:<\/p>\n

          using UnityEngine.UI;<\/pre>\n
          After you’ve added this line in, declare the following variables above the Start<\/strong> function:<\/p>\n
          public Text[] spaceList;\r\npublic GameObject gameOverPanel;\r\npublic Text gameOverText;\r\npublic GameObject restartButton;\r\nprivate string side;\r\nprivate int moves;<\/pre>\n
          How are these variables going to be used? The spaceList <\/em>array at the top will hold all of the text that will be on our buttons in the game. You may be wondering why you wouldn’t have an array of buttons instead of text. This is because you want to check the text on the button when looking for a winner. There’s no information that the button object itself can directly tell you about as far as whether there’s an X or an O on the space. Thus, we want the text instead so you can check that information more directly.<\/p>\n
          Also declared is the gameOverPanel<\/em> which will simply be activated whenever the game has ended. You will also have the gameOverText<\/em> to display whenever a game has been finished. The restartButton <\/em>will appear at the end of a game to simply ask if you wish to start a new game of Tic-tac-toe. After that are the private variables, which will simply keep track of whose turn it is and how many moves have been played so far. At this point, the GameController <\/em>script will look similar to the one in Figure 21.<\/p>\n
          <\/p>\n
          Figure 21: The GameController script so far.<\/p>\n
          Now it’s time to move on to the Start<\/strong> function, where you will set a few variables and deactivate certain objects. This is the code needed for Start<\/em>:<\/p>\n
          SetGameControllerReferenceForButtons();\r\nside = \"X\";\r\ngameOverPanel.SetActive(false);\r\nmoves = 0;\r\nrestartButton.SetActive(false);<\/pre>\n
          All you’re doing is setting the side to ‘X’, setting the number of moves to zero, and deactivating the gameOverPanel <\/em>and restartButton<\/em>. After all, you probably don’t want the GameOver Panel<\/em> object getting in the way of the game, and it would be all too easy for a sore loser to restart the game before it’s finished. So, you deactivate these objects from the start. There’s also one function being called here that you have not yet created, but are about to. Figure 22 shows the finished Start<\/strong> function.<\/p>\n
          <\/p>\n
          Figure 22: The complete Start <\/em>function for the GameController script.<\/p>\n
          Underneath the commented out Update<\/strong> function (or just underneath the Start<\/strong> function if you chose to delete Update<\/strong> completely), create the SetGameControllerReferenceForButtons<\/strong> function:<\/p>\n
          void SetGameControllerReferenceForButtons()\r\n{\r\n\tfor (int i = 0; i < spaceList.Length; i++)\r\n\t\tspaceList[i].GetComponentInParent<Space>().SetControllerReference(this);\r\n}<\/pre>\n
          Once this function is made, the compiler error in the Start<\/strong> function should go away. But you’ve created a new one instead! On the line that says spaceList[i].GetComponentInParent<Space>().SetControllerReference(this);<\/strong> there’s a new error. The compiler doesn’t know what SetControllerReference<\/strong> is. You’re trying to get a function from a different script that, like SetGameControllerReferenceForButtons<\/strong>, has not yet been created. Figure 23 shows the completed function in GameController<\/strong>. <\/em><\/p>\n
          <\/p>\n
          Figure 23: The SetGameControllerReferenceForButtons function.<\/p>\n
          This is now a good time to switch over to the Space <\/em>script. Odds are there will not be a tab at the top of Visual Studio that you can click to switch to the Space <\/em>script. So instead, save your work and go back to Unity. In the Assets <\/em>window double click the Space <\/em>script you created earlier. Alternatively, you can also find the script in the Solution Explorer. Inside the Space <\/em>script, you’ll need to begin similarly to the GameController <\/em>script. Comment out or delete both the Start<\/strong> and Update<\/strong> functions, and be sure to add using UnityEngine.UI;<\/strong> near the top of the script like you did in GameController<\/em>. Once you’ve done that, declare the following variables:<\/p>\n
          public Button button;\r\npublic Text buttonText;\r\nprivate GameController gameController;<\/pre>\n
          When you’re finished the Space <\/em>script should look like the one shown in Figure 24.<\/p>\n
          <\/p>\n
          Figure 24: The beginning of the Space script.<\/p>\n
          This is now the point where you create the aformentioned SetControllerReference<\/strong> function. At the bottom of the script, add the following code:<\/p>\n
          public void SetControllerReference(GameController control)\r\n{\r\n\tgameController = control;\r\n}<\/pre>\n
          That’s all there is to this function. All it’s doing is getting a reference to the GameController <\/em>script for later use. Note that it must <\/em><\/strong>be a public function for GameController <\/em>to use this function. There’s not much else left to do with the Space <\/em>script for the rest of the project, so you may as well finish it out since you’re here. Underneath SetControllerReference <\/strong>add another public function called SetSpace <\/strong>and give it the following code:<\/p>\n
          public void SetSpace()\r\n{\r\n\tbuttonText.text = gameController.GetSide();\r\n\tbutton.interactable = false;\r\n\tgameController.EndTurn();\r\n}<\/pre>\n
          The GameController <\/em>script will be putting this function to use. After the player makes a move, this function will be called to place an X or an O on the space and make sure the button object you click is no longer interactable. It will then call GameController’s <\/em>EndTurn<\/strong> function to change whose turn it is. With this function finished, the Space <\/em>script is finished. Figure 25 shows the finished script. Keep in mind that it’s okay for the errors in SetSpace<\/strong> to be there for now as you will be adding the needed functions momentarily to GameController<\/em>, which will in turn remove those errors.<\/p>\n
          <\/p>\n
          Figure 25: The finished Space script.<\/p>\n
          It’s now time to switch back over to the GameController <\/em>script. You can either go back to Unity and double click the GameController <\/em>script again or click the GameController<\/em> tab near the top of your Visual Studio window like in Figure 26. Remember to save your work!<\/p>\n
          <\/p>\n
          Figure 26: Switching to the GameController script.<\/p>\n
          Once you’ve returned to the GameController <\/em>script, go to the bottom of the script and add the following code:<\/p>\n
          public string GetSide()\r\n{\r\n\treturn side;\r\n}<\/pre>\n
          When the Space <\/em>script calls this string function, all it\u2019s effectively doing is getting the current player’s turn and setting an X or O on whichever space you clicked on. Next it’s time to create the ChangeSide <\/strong>function, which will control the changing of player turns. The code for this is as follows:<\/p>\n
          void ChangeSide()\r\n{\r\n\tif (side == \"X\")\r\n\t\tside = \"O\";\r\n\telse\r\n\t\tside = \"X\";\r\n}<\/pre>\n
          After this is complete, your GetSide <\/em>and ChangeSide<\/em> functions should look similar to what’s shown in Figure 27.<\/p>\n
          <\/p>\n
          Figure 27: The GetSide <\/em>and ChangeSide <\/em>functions of GameController.<\/p>\n
          Now it’s time to create perhaps one of the most important functions in the whole project. This function, called EndTurn<\/strong>, <\/em>will be handling the process of incrementing the moves<\/strong> variable as well as checking to see if any sort of game over state has been achieved. If a player has gained a victory, it will call a GameOver<\/strong> function which will be created momentarily. It will also check to see if the number of moves has reached a certain limit, and if it has, it will activate the gameOverPanel <\/em>and restartButton<\/em>. Here’s the code for the EndTurn<\/strong> function:<\/p>\n
          public void EndTurn()\r\n{\r\n        moves++;\r\n        if (spaceList[0].text == side && spaceList[1].text == side && spaceList[2].text == side)\r\n            GameOver();\r\n        else if (spaceList[3].text == side && spaceList[4].text == side && spaceList[5].text == side)\r\n            GameOver();\r\n        else if (spaceList[6].text == side && spaceList[7].text == side && spaceList[8].text == side)\r\n            GameOver();\r\n        else if (spaceList[0].text == side && spaceList[3].text == side && spaceList[6].text == side)\r\n            GameOver();\r\n        else if (spaceList[1].text == side && spaceList[4].text == side && spaceList[7].text == side)\r\n            GameOver();\r\n        else if (spaceList[2].text == side && spaceList[5].text == side && spaceList[8].text == side)\r\n            GameOver();\r\n        else if (spaceList[0].text == side && spaceList[4].text == side && spaceList[8].text == side)\r\n            GameOver();\r\n        else if (spaceList[2].text == side && spaceList[4].text == side && spaceList[6].text == side)\r\n            GameOver();\r\n        if (moves >= 9)\r\n        {\r\n            gameOverPanel.SetActive(true);\r\n            gameOverText.text = \"Tie!\";\r\n            restartButton.SetActive(true);\r\n        }\r\n        ChangeSide();\r\n}<\/pre>\n
          The way the EndTurn<\/strong> function checks for a victory is, admittedly, a little reliant on brute force. If, for example, you wanted to expand the board for any reason, then this solution would simply be no good and you’d have to either recode it to accomodate the different victory conditions or come up with an entirely different solution. For this project, the code above will work fine. All it’s doing is checking the text of each item in the spaceList<\/em> array and seeing if there’s a three in a row combination. If there is, it calls GameOver <\/strong>and ends the game. In addition, if the number of moves played is equal to or greater than nine, it will also end the game.<\/p>\n
          You’re not calling the GameOver function<\/strong> here, and you may be wondering why. It’s primarily because of the gameOverText.text = ‘Tie!’;<\/strong> line. In the GameOver<\/strong> function you’ll soon make, the game is just getting the current player’s side (X or O) and concatinating wins!<\/strong> to the text. In a draw, that wouldn’t make very much sense, and thus the process is handled a little differently. Finally, if none of the above game over conditions are met, then the game simply changes the side to the next player. Figure 28 shows the full EndTurn<\/strong> function.<\/p>\n
          <\/p>\n
          Figure 28: The EndTurn <\/em>function in the GameController script.<\/p>\n
          With EndTurn <\/strong>complete you will now need to create the GameOver<\/strong> function as follows:<\/p>\n
          void GameOver()\r\n{\r\n        gameOverPanel.SetActive(true);\r\n        gameOverText.text = side + \" wins!\";\r\n        restartButton.SetActive(true);\r\n        for (int i = 0; i < spaceList.Length; i++)\r\n            SetInteractable(false);\r\n}<\/pre>\n
          This is similar to when you checked for how many moves had been played in the EndTurn<\/strong> function, but with a few extra steps. Immediately after this, create the SetInteractable <\/strong>function to remove the error in the GameOver<\/strong> function. Then, enter the following code:<\/p>\n
          void SetInteractable(bool setting)\r\n{\r\n        for (int i = 0; i < spaceList.Length; i++)\r\n            spaceList[i].GetComponentInParent<Button>().interactable = setting;\r\n}<\/pre>\n
          All this code is doing is gathering all the Button<\/strong> components in the parent object of each text object in spaceList<\/strong> and setting interactable to whatever you assign in the setting<\/strong> boolean. Once this is finished, your GameOver<\/strong> and SetInteractable<\/strong> code should look similar to Figure 29.<\/p>\n
          <\/p>\n
          Figure 29: The GameOver <\/em>and SetInteractable <\/em>functions in GameController.<\/p>\n
          At this point, you may think the coding part of this project is done, but there is actually one last function that needs to be made. After a game over state is achieved, the user will need some way to restart the game. To that end, you will need to make the Restart<\/strong> function. It’s very similar to the GameOver<\/strong> function, but in reverse:<\/p>\n
          public void Restart()\r\n{\r\n        side = \"X\";\r\n        moves = 0;\r\n        gameOverPanel.SetActive(false);\r\n        SetInteractable(true);\r\n        restartButton.SetActive(false);\r\n        for (int i = 0; i < spaceList.Length; i++)\r\n            spaceList[i].text = \"\";\r\n}<\/pre>\n
          Once completed, the Restart <\/em>function should look like the one in Figure 30.<\/p>\n
          <\/p>\n
          Figure 30: The Restart <\/em>function.<\/p>\n
          Now that both the GameController <\/em>and Space <\/em>scripts are complete, make sure you’ve saved them both and return to the Unity editor.<\/p>\n
          Finishing the Project<\/h2>\n
          First, before assigning scripts to any objects, you need to make a prefab of the Space <\/em>object. You’ll use the prefab to edit the Space <\/em>object’s settings and then you’ll make duplicates of the Space <\/em>object. The duplicates will share all the properties of the prefab you create, thus saving time. With that said, drag the Space <\/em>object into your Assets <\/em>window as seen in Figure 31.<\/p>\n
          <\/p>\n
          Figure 31: Creating a new prefab.<\/p>\n
          Select the Space <\/em>prefab you just created and then move to the Inspector <\/em>window. Scroll down until you see the Add Component <\/em>button. Click the button and search for the Space <\/em>script. Once found, click on the script to add it as a component to the prefab like in Figure 32.<\/p>\n
          <\/p>\n
          Figure 32: Attaching the Space <\/em>script to the Space <\/em>prefab.<\/p>\n
          You’ll need to assign the Space <\/em>prefab itself as the value of the Button <\/em>field as well as its child Text <\/em>object to the Button Text <\/em>field below like in Figure 33.<\/p>\n
          <\/p>\n
          Figure 33: Setting the values of Button <\/em>and Button Text<\/em>.<\/p>\n
          Next, in the button component, set a new On Click <\/em>event by clicking the + plus button near the bottom of the component, as seen in Figure 34.<\/p>\n
          <\/p>\n
          Figure 34: Creating a new On Click <\/em>event.<\/p>\n
          The On Click <\/em>events exist for executing code whenever a button is clicked. In this case, you’ll be assign the Space <\/em>script’s SetSpace<\/strong> function as the code to execute whenever a Space <\/em>button is clicked on. After clicking the + button, select the object picker by clicking the small circle next to the field that should currently say None (Object)<\/em> like in Figure 35.<\/p>\n
          <\/p>\n
          Figure 35: Picking a new object for the On Click <\/em>event.<\/p>\n
          In the window that appears, search for Space<\/em>. Remember that you’ll want the prefab and not the script here. Search for the Space <\/em>object with the blue cube next to it like in Figure 36.<\/p>\n
          <\/p>\n
          Figure 36: Selecting the Space <\/em>prefab.<\/p>\n
          After you’ve selected the object, click on the field that says No Function<\/em>. A menu will appear showing the different components currently attached to Space<\/em>. Go to Space->SetSpace <\/em>to set the SetSpace <\/em>function as the code to execute whenever a Space<\/em> button is clicked. Figure 37 shows where to find everything you need for this step.<\/p>\n
          <\/p>\n
          Figure 37: Setting SetSpace <\/em>as the code to execute.<\/p>\n
          Your Space <\/em>prefab is finally complete, which means you should now be able to select the Space <\/em>object in the Hierarchy <\/em>window and see the changes you just made applied to it. The prefab can come in handy in the future if you wanted to make additional boards or have the buttons used in different scenes. In this case, you’ve made it so that all buttons on this board will behave exactly the same way. With Space <\/em>selected in the Hierarchy <\/em>window, press Ctrl + D eight times to make a total of nine Space <\/em>objects. Once you’ve done this, your Hierarchy<\/em> will look similar to the one in Figure 38.<\/p>\n
          <\/p>\n
          Figure 38: The Hierarchy <\/em>with all the Space <\/em>duplicates.<\/p>\n
          Of course, the buttons can’t all stay in one place. You’ll need to move them around the board using the Rect Transform <\/em>component to have a proper Tic-Tac-Toe game board. Table 2 shows the needed coordinates for each object. It’s important to note that the right Space <\/em>object is in its correct place. For example, you wouldn’t want the intended bottom right space to be in the position that upper middle space will be in.<\/p>\n
          Object Name<\/strong><\/p>\n
          Position X<\/strong><\/p>\n
          Position Y<\/strong><\/p>\n\n\n\n\n\n\n\n\n\n\n\n
          \n
          Space<\/p>\n<\/th>\n
          		\n
          -50<\/p>\n<\/td>\n
          		\n
          100<\/p>\n<\/td>\n<\/tr>\n
          \n
          Space (1)<\/p>\n<\/th>\n
          		\n
          55<\/p>\n<\/td>\n
          		\n
          100<\/p>\n<\/td>\n<\/tr>\n
          \n
          Space (2)<\/p>\n<\/th>\n
          		\n
          160<\/p>\n<\/td>\n
          		\n
          100<\/p>\n<\/td>\n<\/tr>\n
          \n
          Space (3)<\/p>\n<\/th>\n
          		\n
          -50<\/p>\n<\/td>\n
          		\n
          0<\/p>\n<\/td>\n<\/tr>\n
          \n
          Space (4)<\/p>\n<\/th>\n
          		\n
          55<\/p>\n<\/td>\n
          		\n
          0<\/p>\n<\/td>\n<\/tr>\n
          \n
          Space (5)<\/p>\n<\/th>\n
          		\n
          160<\/p>\n<\/td>\n
          		\n
          0<\/p>\n<\/td>\n<\/tr>\n
          \n
          Space (6)<\/p>\n<\/th>\n
          		\n
          -50<\/p>\n<\/td>\n
          		\n
          -100<\/p>\n<\/td>\n<\/tr>\n
          \n
          Space (7)<\/p>\n<\/th>\n
          		\n
          55<\/p>\n<\/td>\n
          		\n
          -100<\/p>\n<\/td>\n<\/tr>\n
          \n
          Space (8)<\/p>\n<\/th>\n
          		\n
          160<\/p>\n<\/td>\n
          		\n
          -100<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
          Table 2: All Space objects and their coordinates.<\/p>\n
          If the new space button positions will not stick, be sure that you are running the latest version of Unity. It’s possible that your GameOver Panel <\/em>object is sitting underneath the Space <\/em>objects in the middle row. To fix this, you simply need to rearrange the order of the GameOver Panel <\/em>in the Hierarchy <\/em>like in Figure 39.<\/p>\n
          <\/p>\n
          Figure 39: Rearranging the placement of the GameOver Panel in the Hierarchy<\/em>.<\/p>\n
          Next you’ll need to select the GameController <\/em>object in the Hierarchy <\/em>and then attach the GameController <\/em>script to it like you did with the Space <\/em>prefab with the Add Component<\/em> button. Once you’ve done that, you’ll need to fill in the list of text objects for the Space List <\/em>array. Lock the Inspector <\/em>window so it shows the GameController <\/em>script by clicking the lock icon in the top right corner like in Figure 40.<\/p>\n
          <\/p>\n
          Figure 40: Locking the inspector.<\/p>\n
          Next, expand each Space <\/em>object by clicking the arrow next to each Space <\/em>object. This will reveal the child Text <\/em>object. Make sure they’re all selected using Ctrl + Left Mouse Click, then drag them onto the Space List <\/em>field in the GameController <\/em>component. Figure 41 shows how this is done.<\/p>\n
          <\/p>\n
          Figure 41: Setting up the Space List <\/em>array.<\/p>\n
          At this point, you’ll want to make absolutely sure that the Text <\/em>objects are in the right order in the Space List <\/em>array. You can check this by simply clicking on an element field and seeing where the corresponding object lights up in the Hierarchy.<\/em> Each object should be in order of its appearance in the Hierarchy<\/em>.<\/p>\n
          Now, assign the GameOver Panel <\/em>object to the Game Over Panel <\/em>field. Expand the GameOver Panel <\/em>object to reveal its Text <\/em>object. Drag that object into the Game Over Text <\/em>field in the GameController <\/em>component. Finally, click and drag the RestartGame <\/em>object into the Restart Button <\/em>field. When you’re done, the Game Controller <\/em>script should look like the one in Figure 42.<\/p>\n
          <\/p>\n
          Figure 42: The finished GameController <\/em>script.<\/p>\n
          Finally, unlock the Inspector <\/em>window and select the RestartGame <\/em>object. Scroll down until you see the On Click <\/em>event like with the Space <\/em>prefab earlier. This time, click and drag the GameController <\/em>object from the Hierarchy <\/em>into the Object <\/em>field in the On <\/em>Click event. After you’ve set the object you will then click the field that says No Function <\/em>and navigate to GameController->Restart <\/em>to set the Restart <\/em>function as the code to execute when the RestartGame <\/em>button is clicked. After you’re finished, save everything and give your game a try!<\/p>\n
          <\/p>\n
          Figure 43: Tic-Tac-Toe in action!<\/p>\n
          Conclusion<\/h2>\n
          Using only UI elements, you’ve made an entire game! The idea was to show you just a few things you can do with Unity’s built in UI systems. Typically, when creating any UI objects they are used to help inform the player of information like the current score or where they are on a map. However, UI can be used for almost any purpose you desire. The possibilities really are as endless as you can imagine.<\/p>\n","protected":false},"excerpt":{"rendered":"
          The user interface, such as buttons and messages, in a game is very important. In this article, Lance Talbert shows how to create a working Tic-Tac-Toe game using Unity and C# consisting of user interface elements. …<\/p>\n","protected":false},"author":317499,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[143538],"tags":[],"coauthors":[52549],"class_list":["post-79183","post","type-post","status-publish","format-standard","hentry","category-dotnet-development"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/posts\/79183","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/users\/317499"}],"replies":[{"embeddable":true,"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/comments?post=79183"}],"version-history":[{"count":16,"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/posts\/79183\/revisions"}],"predecessor-version":[{"id":79244,"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/posts\/79183\/revisions\/79244"}],"wp:attachment":[{"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/media?parent=79183"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/categories?post=79183"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/tags?post=79183"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/coauthors?post=79183"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}