At the moment the raycasting algorithm is super slow. Need to research and implement a better algorithm.

Since the engine is a separate thing now. Need a way to configure it properly when using it as a library. Presumably this would be something like being able to pass a configuration file/object to it and perhaps even set individual configuration options at a later time.

Currently levels produced by the level loader create an individual tile object for each tile in the level file. This could theoretically slow down the game in levels with a lot of tiles. Probably a good idea to implement some sort of tile amalgamation for same tiles.

Currently, utility functions for SFML vectors like length, normalize, etc. are implemented as pure functions which take vectors as arguments. It may be a better idea to create a child class of sf::Vector2<T> and implement these as member functions of that class.

There doesn't seem to be much reason to have these as separate classes (other than messiness) since there can only really be a single game object manager and the engine implements a bunch of wrapper functions for the manager anyway.

Currently a lot of different structure types (Wall, Ceiling, Floor) are separate game object types in code. It may be more practical to make this a common type like Structure and then use tags instead to denote their role.

It might be useful to be able to pass constructor arguments in create() and createComponent().

At the moment, game objects can be connected but there is no hierarchy between them (e.g. the player is connected to the portal gun but the portal gun is not a 'child' of the player, it's transform is not influenced by the player's, etc.). It might be worthwhile implementing a properly hierarchical structure. However, this is likely to be very challenging and time-consuming.

This is bad. Must fix.

ATM components are connected via the createComponent() function and references to them are stored in each gameobject. Is there perhaps a better way to connect these? Perhaps just storing components directly on the gameobject?

Need to make these const references rather than passing by value

Make the FPS counter look a little bit nicer and add an option to enable/disable it in the engine.

• Enable/disable fps counter?
• Set window size?
• Set framerate?
• etc.

I accidentally committed a copyrighted font (😬) which will need to be scrubbed from the history at some point.

Now that we have a portal gun and a ray, we need to actually make portals!

ATM all includes are relative (e.g. "../../foo"). I believe best practice is to make these absolute but I'm not quite sure how right now. I probably have to change something in Visual Studio.

Would save having to create a Component(GameObject& gameObject) constructor for each component.

At the moment I'm returning just sf::Vector2<T> which is creating a potentially unnecessary copy every time. Returning a const reference will enable the option of not making a copy if need be.

It's too short atm :(

If the idea is for the engine to become an independent library at some point, it will need its own namespace.

https://yusastudios.itch.io/tileset-generator