Attempting to simplify the game development process while upholding the C++ Core Guidelines.
Game design patterns are used to simplify the development, I have attempted to implement some patterns specific to the needs of Julgen. Some patterns are more specific and should be left out of the engine, but here are some patterns I included for ease of use.
Observer Pattern - Julgen has a build in Event class that allows to be used similar to a Unity Action or a UE Delegates. These can be used to bind a (member) function to a object of type Event. Once Invoke() is called on the event all (member) functions will immediately be invoked. The observer class will require to inherit from IEventListener, this allows for automatic removal of the observer or the sender.
Command Pattern - In short, allowing users to encapsulate input requests as objects.
Singleton - A simple implementation of Singleton is included in the engine. Use it judiciously.
Dirty Flag - Used in various places within the engine. Most notably the transform component; to allow for world and local positions within huge hierarchical structures.
Update Method - Update Method - Double Buffering - As most modern game engines, Julgen also employs a Update method. This seemingly easy design pattern allows for very practical game programming. At the same time Julgen includes a helpful GameTime class allowing for frame independent gameplay. While double buffering is quite a brought topic, Julgen uses it within the components using Late Update to allow for more control over squenced operations.
Component The good old Gameobject Component system has been used and allows for more modular and diverse games.
C++ Core Guidlines Game Programming Patterns by Robert Nystrom Beautiful C++
Julgen is build with both Windows, Linux and web in mind. The engine should be able to be compiled using both MSVC and GCC. Web builds can be made using Emscripten.
- Game Loop The current game loop uses some resources to loop over all components and game objects to check if they are set to be destroyed. There are some similar scenarios and these could be addressed by smartly moving objects between containers. This however should be properly tested for real world performance difference.
- Rendering The rendering sorting is currently manually being done on the cpu every frame and should ultimately be replaced with proper rendering. Also allowing hte engine for 3D rendering. Rotating and scaling is also on the list ;)
Julgen is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 3 of the License, or (at your option) any later version.