Wearable Learning

A game instance is a single occurrence of a game. Starting a game on the game manager starts a single game instance. Players can then join the game instance to play the game on their mobile device. Ending a game on the game manager ends that game instance. Multiple instances of a game can be started; each game instance gets its own unique PIN. Players join a specific game instance by entering a game instance’s PIN on WearableLearning on their mobile device.

A game pin is the unique identifier for a game instance. Each game instance that is created is assigned its own unique game pin. A player can only join an active game instance by entering the game instance’s game pin on WearableLearning on their mobile device. Game pins ensure that players join the intended game instance, so it is important to have the correct game pin.

You can create a game instance by logging into WearableLearning and selecting the Game Manager mode. Click the green “+” button at the bottom center of the screen, select a game from the dropdown menu that appears, and click “Start”. Your game instance will appear at the end of the list of active game instances and will display the Game Pin necessary for players to join the game.

You can delete a game instance by logging into WearableLearning and selecting the Game Manager mode. Click the red pencil button at the bottom center of the screen. Buttons with close symbols (“X”) will appear in the top left corner of each game instance. Click the close button next to the game instance you wish to delete and press “OK” to confirm deletion. When you are done deleting game instances, click the red pencil button again to hide the close buttons. Game Managers should always delete game instances that are no longer needed (e.g., after playing the game).

The number of players who can join and play a game instance depends on how many players or teams the game is designed to support. To figure out how many players can join a game instance, start a game instance, go to the Game Player mode, and join the game. It will ask you to pick a player using a dropdown menu with all of the possible players. Counting these options will tell you the number of players that a game instance can support. Additionally, the WearableLearning games library provides details on publicly available games, including the number of players supported by each game.

You can start more than one game instance at a time and run them simultaneously to accommodate more players. Remember that each game instance has a unique game pin. Players will need the correct game pin that corresponds to the game instance that they need to join.

To play a game, you need the game pin for the game instance started by a Game Manager (see FAQs for Game Managers). Once you have the game pin, log into the WLCP and select Game Player. Enter the game pin for the instance you wish to join and click “Join”. Then select the player you wish to be and play the game!

To play a game, you need a phone, tablet, or other mobile device with stable internet connection. You also need a Game Manager (which could be yourself) to create the game instance before players log in. Some games require additional materials that are specific to the game. Check out the Playing Games section of this website to see some available games to play.

The game pin is the unique identifier for a game instance. The game pin is created when the game instance is created and it is required by the player in order to join the game. Game pins ensure that players join the intended game instance, so it is important to have the correct game pin.

To create a new game, log into the Wearable Learning platform and choose the Game Editor mode. On the builder, click the “New” button in the top left. Choose a game name (with no spaces, numbers, or special characters in the title), the number of teams that will be able to play, and the number of players per team. You can also edit the game’s visibility which is publicly viewable to all Wearable Learning users as the default setting. Clicking “Create” will make an empty game with your specifications. From there, you can add states and transitions to create your game.

If you have already created a game, you can open it again by selecting the “Load” button in the top menu bar of the Game Editor mode, selecting the game you wish to edit from the dropdown menu, and clicking “Load”. You can load your personal games and any of the public games, but you will only be able to edit the games that you have created. To edit someone else’s game, make your own copy of the game by going to “Game Options” in the top menu bar and selecting “Copy Game”.

No, only the person who created the game can edit it. To edit someone else’s game, make your own copy by going to “Game Options” in the top menu bar and selecting “Copy Game”.

Yes, your game will save automatically.

A state is a game element that represents a screen that the players will see on their mobile devices. To create a state, you can drag a state from the toolbox on the left and drop it onto the builder. Attach the state to the rest of your game by dragging an arrow from the gray circle on the bottom of one state to the gray circle on the top of the state you just added to your builder. Double clicking the state will open the state editor where you can enter the state title (for editing purposes only) and the display text/image, which will be shown on the screen that the players see.

The start is a placeholder that defines where players will begin in your game. Drag an arrow from the gray circle on the bottom of the start to the top gray circle on the state representing the screen you want all players to see first. There should only ever be one arrow coming from the start and that is the only arrow in your game that should NOT have a transition on it.

A transition is a game element that represents how the players will move from one state to the next. For instance, a player typing an answer and clicking submit to move on is an example of a transition. There are three possible transition types:(1) Button Press
(2) Color Sequence or
(3) Text EntryTo make a transition, you can drag a transition from the toolbox on the left and drop it on an arrow that connects two states. Transitions can only be placed on arrows so always connect two states prior to making a transition. Double clicking the transition will open the transition editor where you can choose the transition type and enter the response that allows players to proceed from one state to the next.

To connect states, you drag an arrow from the gray circle on the bottom of one state to the gray circle on the top of the state you want players to move to next. For instance, for players to move from State A to State B, you would drag an arrow from the bottom of State A to the top of State B. Each arrow should have a transition on it (except the arrow from the start). To remove an arrow, click and drag the gray circle that the arrowhead is attached to and drop the arrow on an empty part of the builder to delete it. If you pick up the wrong arrow, drop it back on the gray circle and try again; you will automatically pick up a different arrow.

There is no limit on the number of connections to and from a state, so make as many as you need for your game.

A Button Press is a transition type where a player clicks one button or selects one answer option to move to the next screen. There are four color options: red, green, blue, and black. A player will see all four buttons on the bottom of their screen and they will choose one button to move to another screen.

A Color Sequence is a transition type where players enter the color squares in a specific sequence to move to the next screen. There are four colors that can be included in the sequence: red, green, blue, and black. Each of these colors may be used as many times as you desire. For example, a sequence may be blue-blue-blue-blue or red-green. A player will see four colored squares and an empty box at the bottom of their screen. They can drag the colored squares into the box and then hit the submit button to enter the color sequence.

A Text Entry is a transition type where a player types in an answer to move to the next screen. A player will see an empty white box, which they can type their response into, and a “Submit” button at the bottom of their screen to process their response.

All transition types are available within the transition that you can grab from the toolbox. Once your transition is on your diagram, you can double click it to open the transition editor. Then you can select your transition type in the column on the left.

You indicate the accepted transition input in the section on the right of the transition editor. For a Button Press transition, you check off which buttons would be accepted by the transition. For Color Sequences and Text Entries, you click the “Add Sequence” or “Add Text Entry” buttons and enter an accepted input in the box that pops up.

For a Button Press transition, you can check off all the colors that are not checked off in other transitions with the same source states. For a Color Sequence or Text Entry transition, an empty input will indicate all inputs that are unassigned in all the transitions with the same source state. For example, if State A has a connection to State B and to State C and the transition on the arrow from State A to State B only accepts 7 as an input, then adding an empty transition on the arrow from State A to State C would accept any input that is not 7. To add an empty input, click the “Add” button in the Transition Editor and then click the “Accept” button on the pop up window without filling anything in.

The top row of buttons on a state or transition dialogue box always has a series of buttons labeled “Game Wide”, “Team 1”, etc. These buttons represent the scope and they function much like tabs. When “Game Wide” is selected, whatever you enter for the state or transition will be shown to all players in the game. Alternatively, you could select more specific groups, like Team 1 or Team 1 Player 1.When you select a specific player or team, whatever you enter for that state or transition will only be shown to that specific team or player. Remember that if you change the scope to team level, you need to fill out the state or transition for each team.The same applies when changing the scope to player level. When you start entering text or answers in the state editor, some of the scopes may disappear to ensure that you do not assign the same users to see two different things. If you do not see the scope you are looking for, it is already assigned; try clearing out the information you inputted or deleting and recreating the state or transition.

Yes! We recommend filling in your diagram from top to bottom as you add game elements to avoid certain errors, but you can always add more later or connect a state to a previous state that is higher up in your diagram.

The debugger is a feature of the WLCP that allows Game Editors to test their game. It simulates what a Game Player sees on their mobile device screen when playing the game so you can make sure that your game behaves as expected or fix any problems before letting others play your game.

To launch the debugger, click the “Run and Debug” button at the top of the screen. It will open a new tab with the debugger where you can select the player you want to be and then play the simulation of your game. When restarting the debugger, you will be given the option to open a new instance or open the existing instance (for if you want to debug as multiple players simultaneously). It is recommended that you debug your game periodically while creating it to catch errors early.

Once the game you want to copy is open, you can copy it by clicking “Game Options” in the top menu bar of the Game Editor mode. The menu that expands will have an option to copy a game. From there you can name your copy and create it. Remember to choose a name without numbers, special characters, or spaces.

You can rename a game by clicking “Game Options” in the top menu bar of the Game Editor mode. The menu that expands will have an option to rename a game. From there you can enter the new name for your game. Remember to choose a name without numbers, special characters, or spaces.You can rename a game by clicking “Game Options” in the top menu bar of the Game Editor mode. The menu that expands will have an option to rename a game. From there you can enter the new name for your game. Remember to choose a name without numbers, special characters, or spaces.

You can delete a game by clicking the “Game Options” in the top menu bar of the Game Editor mode. The menu that expands will have an option to delete a game.

You can not change the number of teams or players for a game after creating it. Instead, we suggest creating a new game if you want to change the number of teams or players.

This is a common message that you will see warning you about problems that could occur when saving changes to a state or transition. Some changes to a state or transition that has states and transitions attached below it could invalidate some of the data in the lower states or transitions. This may cause them to be wiped by the system. This is mostly only a concern when editing the scopes, deleting a state or transition, or deleting all content in a state or transition and saving it empty. Nonetheless, it is suggested that you build and fill in your game from top to bottom to avoid these concerns.

There can be no duplicate sequences or Keyboard Inputs that have the same source state. When a player is in a source state, their input to the transition determines which state they will proceed to. If one input is found in two transitions from the same state, then the system cannot determine which of the two transitions the player should go to. If you see this error, try examining the sequences or Keyboard Inputs in all the transitions that share the source state with the transition that gave you the error to find where this input has already been used.

Games are meant to be built top-down starting with the start. You cannot build disconnected sections of states and transitions and then try to combine them later. If you are seeing this error, you are probably trying to connect two states that do not have any connection to the start. Make sure that each state you add to the builder is first connected to a state with a path to the start.

Connections (also known as arrows) are all unique in that they go from one source state to one target state and no two connections have the same source and the same target. If you are trying to duplicate a connection, try instead to modify the scopes (Game Wide, Team 1, etc) in the transition on the existing connection and make sure you fill out all available scopes.

You cannot open (double click) a state before connecting it to the rest of your game. Drag a connection from an existing state connected to the game to the new state you want to edit and then try opening the state again.

A state can have multiple input connections (arrows to the top of the state) that come from source states. However, in order to edit a state, at least one of the source states must be filled in. In order to avoid this error, follow the guide of creating and filling in your game from top to bottom.

This error is usually an indication that the transitions leading into the state have not been set up properly. Make sure that the transitions above have been filled out before trying to edit the states.

Transitions can only be placed on the arrow connections between states. You cannot put a transition on the builder unless it is on an arrow connection.