Technologies Used
- Plain HTML, CSS and JavaScript in the front-end.
- Express JS for the api server.
- PostgreSQL for the database (and Pg-Promise as the connector).
- The Unity Game Engine (C#).
Responsibilities and Contributions
Game
- Game Design.
- Game UI.
- Hitbox logic.
- Simple procedural generation.
- Consumables and interactive objects.
- Map design.
- Character stats: balancing and fetching data.
- HTTP Requests to the API using Unity’s WWW class.
API
- Designing the interface.
- Implementing routers.
- Deployment (I used Railway).
- Database connection.
- Cross-Origin Resource Sharing (CORS).
- Rate limiting.
Database
- Data Modeling.
- Stored Procedures.
- Triggers.
- Database Views.
- Migrating from MySQL to PostgreSQL.
Front-end
- Design and implementation of the website.
- Deployment (I decided to use GitHub Pages).
- Fetching data from the API.
- Embedding the game.
Challenges
This project was challenging as it was made possible by a team of 3 members in a decently small amount of time. The 3 of us had to learn how to use the Unity Game Engine, while trying to implement the features we thought about on our previously written Game Design Document (GDD).
It was also difficult to find where to deploy the project and connect all the services, as we had to use a database, an API and a website. We ended up using Railway for the API and Database, while GitHub Pages allowed us to deploy the front-end with ease.