FANDOM



Pre-Lesson Day

  1.  If 4Di is used, ensure all components are working.
  2. Familiarise yourself with the game and its objectives.
  3. Ensure 3DHive is installed on all computers.
  4. Go through cyber wellness principles and how it will apply to a multiplayer game environment like 3DHive.
  5. Prepare physical materials if required (i.e. Case Notes, QR codes, Exhibit Objects).
  6. Plan and allocate players for each team to ensure an adequate distribution (i.e. do you have enough prey?).
  7. Book a time in the 3DHive server to play your game.
  8. Ensure you have login names and passwords.
  9. Printing out a handout with the visual command screen for each student will reduce motion questions during gameplay; allowing you to spend more time on quality questions about strategy etc.
  10. Decide if you’d like to have a verbal debrief/reflection with the students or a worksheet/journal and prepare as such.

Lesson Day

Before Gameplay

  1. Assign students to their seats based on their teams. This will make it easier for you to brief each team during gameplay.
  2. Remind students on cyberwellness principles and etiquette before using 3DHive.
  3. Before starting the game, discuss with students the topics that are relevant to the game. A recap of skills learnt can be useful.
  4. If the game is a primer of what is to come, ask them for their understanding of the topic so they can test their assumptions.
  5. Set out the scenario of the game for the students to help them immerse themselves in the role and to help them understand their objectives.
  6. Do a pre-survey via discussion and encourage students to predict what the outcome of their game might be. Look out for questions that could encourage experimentation and point them out.
  7. Give out the handout of the visual command screen and go through movements and commands with them.
  8. If 4Di is going to be used, explain to students that the entire lab is an extension of the 3DHive world and that they may be directed to clues outside of their computers.
  9. Guide students through the Login screen to the Team Selection screen.

During Gameplay

  1. Allow students to experiment and find their own way through the 3DHive world.
  2. Using the Teacher’s Console, watch the behaviours of students and see if anyone is having particular difficulty completing tasks.
  3. In game-based learning, it is important for students to come to their own conclusions, so ask them questions that help bridge their way to the answer.
  4. Remind students of the ability to communicate ideas through the chat function.
  5. The Teacher’s console will allow you to make the game easier or harder for students and to change their user experience. This power is immense, but with great power, comes great responsibility. Use it wisely.
  6. The Pause option in the Teacher’s Console will allow you to pause the game for the entire class to introduce a new concept or direction. Take note of when you use it as you’ll be able to track with the 3DHive Assessment Tool how your new instructions affected the students’ gameplay.

After Gameplay

  1. Ensure every student is out of the 3DHive world.
  2. Discuss how they played the game, i.e.:
• Did they meet their objectives?
• What difficulties did they have?
• What strategies did the teams employ?
• What could they have done better?
• What did they learn / use from their lessons?
  1. Discuss with students what you observed in terms of teamwork, ingenious solutions, etc.
  2. You could bring up the 3DHive Assessment Tool with the students and show them some of the parts that their classmates mentioned.
  3. If part of the lesson plan, replay the game. This time, switch teams, or ask them to employ what they just discussed.
  4. At the end of the lesson, ask them to reflect on their individual contributions to the game and how they worked together as a team. This can be done in a journal or reflection worksheet.