Bosquet
|
Genre: Serious Game, Auto-battler, Dungeon Crawler
Stack: Unity Engine, DOTween
Team size: 19
Duration: July 2024
Role: Tools & system programmer
|
|
On the back of Gustave, explore the grove looking for medicine to save "P'tite Pousse". Meet new friends, make them
happy, and overcome difficulties together. And when death comes, do not mourn but cherish the time spent with them.
This game was created in partnership with ESPPERA a French association of doctors and nurses, and
the Léon Berard Research Center. Designed for children to play with their parents and healthcare
providers, it conveys an important message: sometimes, it's worth leaving the hospital even missing treatments to
go on trips, make memories, and truly live.
SAVE
The data-saving system, though hidden, is a crucial feature of the game. Designed with adaptability in mind, it supports
both WebGL (browser) and Windows platforms.
The system manages two distinct versions of game saves:
• Accurate Save: Frequently synchronized to preserve precise player progress.
• Approximate Save: Synchronized once per macro gameplay loop, used to allow players to restart from
not too far when they lose.
EVENTS
Events are one of the key features of Bosquet's architecture. They power many of the other game systems (dialogues,
special cases of level design, etc.).
Figure 3.1. Event integration tool
DIALOGUES
Dialogues immerse the player in the game's story. They are its strong point. To facilitate the integration of narrative
designers, I developed a tool in Unity (see Figure 4.1).
Figure 4.1. Dialogue integration tool
From the latter, it is possible to choose the events to which it will subscribe. Once the corresponding events are
invoked, it is added to the stack of dialog boxes to be displayed (see figure 4.2).
Figure 4.2. In-game dialogue box
MAP
The game map allows the player to make progression choices within a gameplay loop. The loop is dynamic; it and the
elements it displays are revealed as the player progresses, acting similarly to a fog of war (see Figure 5.1).
DOTween and the save system were very important in the development of this feature.