Nice to meet you! I'm Justine Leleu

COGIP

This is the COGIP Microservice Architecture Challenge. In this challenge we had to design and implement a REST API and a non-interactive CLI user interface in a microservice architecture. We were 3 working on that project and we used Srping Boot and Maven.

DataBase

For the database we were given an sql. That database contains 4 tables: company, contact, invoice and user. We used PHPMyAdmin to access the database during development and we later switch to a server.

API

Next we worked on the REST API in an exclusively API-related code repository. The API had to retrieve data in JSON format and modify the database while adhering to role-based access restrictions.

First we implemented the API using Spring Data JPA. I personally worked on the contact table implementation. First we have an entity to connect to the contact table, then a repository and a service to make the connection with the controller and finally the controller for the requests.

Authentication

Once the API was implemented I worked on the authentication and authorization using Spring Security. I implemented the JPA for the authentication and dealt with the security config allowing access depending on the authority of the login user. For the authentication I generate a token that can be stored and used to verify the authority.

CLI

Next was non-interactive CLI and for that we used Spring Shell. Since I worked on the authentication I implemented it for the client side too, I worked on the login command, stored the token and added it to the others commands.

Tic Tac Toe

This is a Tic Tac Toe game for android that I made as a first introduction to android studio. It include a two players mode to play with a friend on the same phone and also a solo mode to play against an IA made with the minimax algorithm. My objective with this project was to discover android studio with an easy to make small app.

Gameplay

Since my objective was to discover android studio, I mostly wanted to make buttons do things when clicked. So for the gameplay I simply used a grid as a background and placed buttons as the tiles. I also have two different activities, for the main menu and for the game, that communicates between them.

IA

I chose to make a Tic Tac Toe because it was simple to make but also because I thought it would be an easy project to implement a basic IA system. So I implemented a solo mode with a minimax algorithm and with the possibility to choose the difficulty by adding a maximum for the recursion of the minimax function.

WUSHU LEGACY

Wushu Legacy was a 6 months production game made at the Game Academy. Wushu is a runner where the player play as Akakin and has to make his way to the enemy camp to kill the general. To achieve that he will have to face many enemies waiting for him along the path and kill them by entering the rights keys in time. The game is playable in solo and versus and also have an online leaderboard to compare score between all the players. We were a team of 5 and I worked on it as a gameplay and UI programmer. Here is a few mechanics I made for the game and some of my work on the UI.

Inputs

Since Wushu is a runner, the player does not have the hero control and move automatically trough the level. All he need to do is focus on the keys and enter them correctly.

The keys to enter appears to the player next to the enemy it belongs to once it has been activated. And the player has to enter them correctly before reaching the enemy or it will be to late. A line on the ground is there to tell the player when the time is almost up.

Enemies

There is 4 different types of enemies in the game and one of them is a special type, the crossbowmen. It's there to add a long distance enemy and a variation to the attacks. Crossbowmen launch a salve of arrows and each arrow has one key, a bullet time start to give the player enough time to enter those keys. But the point is not to kill the player with one salve so to avoid that only one arrow can hurt him and the others just don't give any point.

The enemies are also spawned differently in the level. Some are waiting on the side of the road and get in position when the player arrive and others are packed waiting directly in the middle of the road. In the group situation there is only the middle enemy to defeat, the others are clones following him and dying in the same attack.

Obstacles

Beside the enemies the player will also encounter obstacles like the statues. They spawn on the side of the road and so Akakin has to decal a little from his trajectory to hit them. Those obstacles are there to relax after series of enemies so they only have one key and don't hurt Akakin if the player miss it. They are also meant to give a little spectacular moment to the player by adding a camera movement and a bullet time.

UI

The biggest problem with the UI was the navigation and the focus with gamepad. The buttons have different textures/materials and animations for each state. So for each group of buttons communicating with each other there is a function that deal with the navigation. Those functions first reset the last button focus and then find the next one to focus from the direction gave by the player. This way the focus is easily change and only once when the player decide it.

NIGHTMARE AT THE MUSEUM

Nightmare at the Museum is a game made during the Global Game Jam 2021. The player incarnate a little boy locked inside a museum at night with a monster and a music box for only weapon. To win the game he has to find a way out but beware of the monster. We were a team of 7 and I worked as a gameplay programmer. Here is some of my work during those few days.

Fear

In the game the player incarnate a little boy trapped in a very scary situation and more the boy spend time in the dark the more he became frightened. Once his fear is too high, the player faint and have to start over. And the only indication for the player is the screen fading working as a fear bar by playing an animation.

The player can reduce the fear by calming the boy only by playing music which has to reload eventually or by standing in the light but it will not last forever.

Exits

There is locked doors everywhere in the museum but only one key hidden somewhere. To win the game the player has to find that key and then find the right door to escape.

MULTIPLAYER GAME

I wanted to learn about multiplayer, so I made this prototype with the help of an online course. It is made with UE5 and mainly with C++.

Multiplayer plugin

First I made a plugin using the online subsytem steam. That plugin contains a widget offering the player two options: Host and create a session or join an existing one.

Weapons and pick ups

That project includes diverse types of weapons, projectile weapons, hitscan weapons, grenades. And an actor component is in charge of all that concern the fighting part including equipping and swapping weapons and the ammos. Then there is some pick ups allowing the player to obtain more ammos or regain health. Those also have their own actor component.

Replication

Since this is a multiplayer project there has to be some replication. Since the server is in charge things like health or some effects are replicated so the clients can know and display it.

Lag Compensation

Since it is a shooter, it's important to deal with lag problems. So, this project includes Client-side prediction allowing the client to do some actions like aiming or reloading without perturbation due to the lag. And also Server-side rewind using hit boxes to confirm a hit on the server even with lag. But the server side rewind is not used in case of really high ping to keep it fair for everyone.

Cheating

In this case, the server is in charge and verify everything, but there are still things like the fire delay that are not checked and in that case there is a validation used to verify that data and kick out the cheating player.