A console game inspired from the game Age of War and the minigame Bed Wars from minecraft.
Require CMake version 1.17 or more.
Compiled and tested under linux with gcc version 7.5.0 and c++ 17.
Before compiling run cmake <pathToProject> in a directory above the one that contains the project. On windows you need to add a corresponding -G parameter.
Then run make to compile.
Usage : ./AgeOfBedWars <backgroundFile> <baseHealth> <moneyPerTurn> <roundsBeforeGameOver> [initialMoneyAmount]
<arguments> are required. [arguments] are optionnal.
<backgroundFile>: A YAML file containing the terrain parameters. See resources/test.yaml and resources/test3pl.yaml for file structure.
You can easily make your own game terrain by duplicating one of the examples and following the given comments.
All the extensions are accepted if intern file structure is correct. For more information on the file strucuture, see src/Battlefield.cpp.- Other parameters are self explanatory, for more more informations you will have to look at the code.
Recommended parameters are : resources/test.yaml 100 8 100 2
As this is part of my student work, I try to use a wide range of C++ features. Because of that I may code two things that has similar meaning in different ways.
Besides that I try to use the c++ library and especially the algorithms library as often as possible.
- includes : .hpp files for sources and libraries. Sub-directories have same structure as src/ except for libraries folders.
- libraries : currently contains libyaml-cpp.a as a static library built for linux.
- resources : YAML files needed to provide game information at startup. Included txt files are ascii arts from the game candy box 2 https://github.com/candybox2/candybox2.github.io I took with planning to add great looking backgrounds in config files.
- src : c++ sources with unit-related classes in unit/ subdirectory.
- Game.cpp : Entry point, parse command arguments and contains the game loop.
- Battlefield.cpp : Load and parse the yaml file that configures the playfield. During the game it handles the actions of the units and draws the terrain.
- Player.cpp : Player class.
- Base.cpp : Class to handle the player bases.
- units/ :
- Unit.cpp : abstract parent class for units.
- Archer.cpp : Archer class.
- Catapult.cpp : Infantryman class.
- UnitPool.cpp : Wraps a collection of unique pointers to store units.
Although the game is ment to be configurable with files, the terrain variations are limited by the virtual grid beeing spread on the entire background and units beeing centered in the cells only displaying theirs initials. The grid spread problem can be work around by creating a grid bigger than needed (like a grid of 3 by 10 with bases only in the middle line and not at the edge cells of the grid) this helps not creating too large cells. The second problem, with units, would need a system to load custom sprites for each unit type this is something I want but need further rework of the code before this could be implemented.
One big code modification I would like to make is making a template system to instanciate Units this allows to store informations like unit prices directly in the class and this is a step to the ultimate goal of having unit behavior fully dynamic and defined by config files at execution time. Also this would discard the need for a UnitType enum, redundant with the information provided by the class hierarchy.
Finally some part of the code have grown steadily, adding one functionality at a time, and could now benefit a good cleanup and rework. I think of the Battlefield playActions/doActionPhase system with its dependent functions.