Thursday, May 30th

Class hours: 10:05 – 2:45
Mr. Bohmann | wbohmann@ewsd.org

10:05 Today’s Notes & Attendance

Two More Days left in May
Equipment – Please return to me – equipment is now late!
SkillsUSA Test – Alex, Miah, Josh, Colleen, Ben, Lee – 10:10am – check in to classroom first
Monday, June 3rd – we (CAWD2) will all test each others games for feedback, then we will do a final sprint to incorporate changes and prepare for publishing for Wednesday. You are working to get your game ready for testing.
Finally, Senior Survey – that’s all of you – complete for Ms. Charron

10:10 CAWD Game Studio

Most of you are just about ready begin the Testing & Integration Phase. We are working towards game play and testing tomorrow and into next week.

The testing & implementation phase is an essential part of the game development cycle. Testing or Quality Assurance includes careful planning, documentation of bugs and errors and follow up on the fixes that need to be made. Check out this job listing for a QA.

Before you start testing, it is a good idea to develop a test plan. The test plan details exactly what kind of performance tasks/tests need to be made. Basically, what are you testing? This might be the ease of use of the GUI, the core game mechanic, the story, user inputs and or the user experience.

Rather than ask a person to play your game and tell you what you think, consider creating some specific questions that you want feedback on. We talked about this yesterday and came up with some ideas of questions we can ask. Remember: We are testing not only gameplay, but how the user interacts with the game – so make sure you are observing that too.

*Grandma’s Boy – Happy Madison Productions* Game Testers

Larger projects may involve dozens of tests, especially when a new version or release is created.
Alpha testing is usually done by dedicated testers (the people who assembled the program)

Beta testing allows external people (outside the project) a chance to find problems the internal testers might have missed.

5 Minute Scrum Meetings / Update Trello Boards

Remember a good meeting is quick and on target. What am I working on today, What help do I need. Those are the questions you should be responding to in your group or individually.

Want some code for a shooter – I was working on a simple example yesterday. You will need to create an empty for the location of the bullet to spawn on your player. You will also need to create a prefab for your bullet. Two Scripts – One for the Player and one for the Bullet

Player Shooter

using System.Collections;
using System.Collections.Generic;
using UnityEngine;

public class PlayerShoot : MonoBehaviour
{

    public float fireRate = .05f; //you can adjust the cooldown
    public Transform firingPoint; // location of where the bullet comes from
    public GameObject bulletPreFab;
    float timeUntilFire;



    // Update is called once per frame
    void Update()
    {
        if (Input.GetMouseButtonDown(0) && timeUntilFire < Time.time)
        {
            Shoot();
            timeUntilFire = Time.time + fireRate;
            //Time.time is the time at the beginning of the current frame in seconds since the start of the application 

        }

    }

    private void Shoot()
    {
       Instantiate(bulletPreFab,firingPoint.position, Quaternion.identity);
        
    }
}

Bullet Script

using System.Collections;
using System.Collections.Generic;
using UnityEngine;

public class BulletScript : MonoBehaviour
{
    public float bulletSpeed = 15.0f;
    public float bulletDamage = 2.0f;
    public Rigidbody2D rb;
  
    void FixedUpdate()
    {
      rb.velocity = Vector2.right * bulletSpeed;
      Destroy(gameObject, 3); // this will destroy the bullet after 3 seconds
    }

    private void OnCollisionEnter2D(Collision2D collision)
    {
        if(collision.gameObject.tag == "enemy")
        {
            Destroy(collision.gameObject);
            
        }
        
    }
}

10:50 Break

11:00 CAWD Game Studio Development Time

OBS Walkthrough – Core Mechanic due tomorrow – see yesterday’s dayplan for details

Throw in the Towel (I’m done until game testing feedback)

If you have completed the alpha of your game and do not plan to continue developing, revising and generally working on your CAWD final game project until after game testing, you will need to continue working on a project independently. This may be:

A CAWD Knowledge Exchange – where you take your favorite topic, build a lesson and plan to teach us how to do it. You become the teacher and we build, learn, practice with you. We can schedule a day to present next week.

CAWD Project Revision – you take a project from the year that you’d like to improve, add on, revise or just overall go “further”. You’ll share your “mod” with us next week. No grade will change on your revision.

SkillsUSA Practice (if this applies to you)