This game is still in the early stages of development. It is a side project right now with my efforts and time going into other projects. Our team of two (my partner Anthony and myself), have worked together to write the story and are still discussing potential game mechanics.
This is a detective mystery game with horror elements. You play as a detective new to the job and are sent to help locate a missing teenager in the town of Pope Lick. You must investigate, discover clues, and solve the mystery that goes deeper than one missing kid.
It is just the two of us so we are taking on several roles and those roles ares still evolving.
In charge of all graphic assets and world building. He works in Blender. He has also taken the lead on story development.
In charge of all programming, lighting, and other Unity specific tasks. I also contribute to story development.
- Player Movement
- Interaction System
- Camera System
- Inventory System
- UI
- Animations
- Lighting
- Input System
I built essentially what will be the first draft of the player and player controller. Anthony built the first scene (Office Scene) and I added all the textures and did all the lighting design for it. All doors and drawers were made interactable so that the player could open them.
The storyline is still in process but there is a script that maps out the key elements to the story.
Anthony is building assets and I am still grey-boxing or testing out the player controller and all the assets and actions a player has.
All game objects use Vectors that allow you to track object locations and to move and apply other forces on the Player Controller.
- Walk left, right, forward, and backwards
- Sprint
- Jump
- Crouch
- Quickturn
- Look
An interactable abstract class was created using the Template Method Pattern that all interactable object scripts inherit from.
The player casts a ray from the center of the cameras FOV. Data from the hitCollider is used with the input system and events to allow the player to interact with different objects with different outcomes.
- Turn on lights
- Opening doors
- Picking up items
- Talking to another character
Allows player to use a camera in-game.
They can take pictures with the camera and it saves the image in an array in a Film object that stores 5 pictures at a time.
These pictures can then be used to develop and print the images onto a photo that will be used to help solve the mystery.
Uses a ray to detect an object that inherits from the abstract class Photographable, and marks the item so that clues can be tracked as either photographed or notPhotographed.
The camera system is currently not working, but was working previously.
A system that allows items to be stored in containers. The player has its own container (inventory) that is represented in the UI for the player menu.
Player can use the interaction system to pick up items and store them in the inventory.
When finished the player will have more options to interact with items in the inventory like, drop, or place in another container from the inventory.
- Crosshairs
- Interactable Item Text (Interactable items will prompt the user with a message displayed in the Player HUD to describe the object or the interaction type.
- Menu (Currently just allows player to pause the game, veiw the menu, and return to the game.
- Player Menu (Displays Inventory, Camera with slot for Film, and slots for items to equip, one for each hand. Just a stand-in for testing pourposes)
- Currently only the inventory is interactable. Items can be selected and moved to different inventory slots.
I believe right now the only animations being used are the ones to simulate the players head bobbing as they walk or run.
Also the animation to open the car door when the player interacts with it.
I have been learning how to improve the lighting in the game using Post Processing to add a grainy look, bloom, and other effects.
Bake light maps to improve the visual quality of the scene.
I have now placed all current code of this project on GitHub but that is all this repository contains and cannot be ran.We are now using the version control that is built into Unity (Plastic SCM).
We are currently rebuilding everything we've made so far to optimize.
We were having issues with all the assets having high poli counts and the UVs were not oriented properly which was causing problems when we tried to apply the textures in Unity.
Now that I know how to work with version control and Anthony and I are able to work on the same repository, redefine our workflow and rebuild our game, I will no longer be making any commits to this repository.
Until I have a better way of including this porject in my portfolio, I will use this repository as a reference for others to explore the code that I wrote.
I plan to make a website to display screenshots and videos to showcase all the work that we did and plan to recreate in a more optimal and organized way.
This repository only contains the scripts for this game. All other assets are not included and therfore this game can not be ran from this repository. This is just to include in my portfolio and more details will be added soon.
Check back soon for a link to the website to showcase all of our work so far. I also plan to start a social media account and a dev blog for this project as soon as we start it back up.
This is the first scene. Anthony created all the assets and I added the textures and did the lighting design.
I created this whole scene to test in. I created the fire and smoke assets with the particle system.
Player takes a photo and it prints to this gameobject.
