tijmenuu / smarttalesii Goto Github PK

Currently the Readme is kind of overloaded with information. Use separate pages with the Wiki function of Github to better organise the information.

Update the readme with a description of the available branches and their purposes.

Currently the logic assumes a resolution of 1280x720 all over the place. Make it so that it no longer relies on this, in the event the game can't be run at the requested resolution.

Easy fix: hardcore the default view to 1280x720. Keeps all the hardcoded values, but allows for dynamic changes of resolution.
Harder fix: make the game's logic resolution independent.

Title says it all.

The Obstacles logic has branched enough to warrant a refactor. The obstacles with sensor upgrades in level need their own class, the door needs its own class and the phone needs its own class.

It would make a lot more sense if the game difficulty, speed curve and reward curve could be controlled through scripting.

Use Lua for this, or perhaps Chaiscript?

Have a message overlayed on a timeout saying something along the lines: "Evade all obstacles by doing the required gesture/swipe!"

Implement as seperate mode which centers the desired text on screen and pops itself off the stack when its life expires (both string and lifetime should be configurable, perhaps through the constructor).

Maybe use some music too, like blippy trance?

The naming of the files and namespaces no longer reflect the actual purpose of it. It currently concerns itself with the obstacles and game difficulty. This should be separated to make it more clear, then have a difficultydefinition.hpp/cpp fileset and obstacledefinition.hpp/cpp fileset.

Good additions would be:

• Relative position where the neutralization hint should appear
• Relative position where the score bubbles should spawn

Potential additions / up for consideration:

• What happens on neutralization --> second texture file (e.g. open door)? fade out?
• Associated difficulty value in order to make random spawning more "fair" (lower chance for difficult obstacles)

And anything else we can come up with.

One singleton class to store spritesheets, textures, fonts and audio. Right now the resources are being loaded multiple times whilst the memory footprint is small enough to warrant a simple singleton class holding all the resources.

Program.cpp would be responsible for instantiating the static variables.