GameDevlog#2 (Kevin)
- In your area, what were your team's goals for the past week?
- Click on a cube -> Cube appears over player head
- Cube above player head -> Give that specific item to the customer
- Destroy the customer
- Destroy the icon above player head
- New Customer moves up
- Line queue (gravity) drawn to center of the desk
- Throw the item at the customer
- Click on a cube -> Cube appears over player head
- In your area, which of these goals have been accomplished by the team?
We made line queueing, constraints, bombs, script/ mechanics working, Clicking on a cube registers in the console.
- In your area, what are the team's goals for next week?
Creating the queue system so the customer can line up in the T shape according to our Miroboard.
- As an individual, what have you accomplished in the past week?
Worked on the game design macro so that we can implement the mechanics. Worked on refining some of the ideas, instead of a puzzle type chain system we changed it to making the kangaroo throw the item at the customer. We are working on the code in unity which is hard and we had many errors which delayed us. After getting unity to work we made the project and organized the structure, created script folder, assets, prefabs, and worked on making the board to interact with.
- As an individual, what will you accomplish by next week to stay on time?
We need to get our unity project working, i am having troubles on my computer. After resolving the issues, we worked on the queue system which was challenging the cubes were flying off the map so we added some restrictions to prevent that issue, the customers now stack up accordingly but there is still fleshing out to do.
- As an individual, what will you need to learn to accomplish these goals? We pushed our project to github and was working on our project and script together over the weekend and we accomplished the queue system, clicking on an item and it responding in the console, as well as the cast time delay.
- You must have at least 1 visual aid per WDL (diagrams, sketches, screenshots, etc.). Our visual is the unity project we are working in now.
Each WDL should also have a playtesting report. Each team member should be seeking specific feedback from players and having people outside of their team test this. Please include photos of your playtesting. Sample questions for the types of info to include:
- What were you playtesting? We made the queue system and tried to see how to make that flow better. We needed specific starting points
- What did you want to learn through this playtest? The queue system need to stack better and more constraints
- Who were your playtesters? Do they represent your target audience? Our group
- What did you observe? What did you see when they were playing? Did they interact the way you expected? We played the game together and feel it out, we needed more constraints to solve some problems, such as the gravity issue, the spawning randomized, narrowing down the path for the customer line according to the miroboard.
- What questions did you ask your playtesters after they played the game? How will we get the queue system to work and not flow out? We needed walls and constraints to help align the customers.
- What feedback did you receive from your players? Clicking on the items/ customers interaction is not working and we fixing that
- What, if anything, will you do with that feedback? Did you learn anything? We learn so much
Get Kangaroo Hotel
Kangaroo Hotel
Status | Released |
Author | Kevin |
Genre | Simulation |
More posts
- Code Devlog #621 days ago
- Code Devlog#535 days ago
Leave a comment
Log in with itch.io to leave a comment.