top of page

Reptoads

Tomorrow Engine

Custom C++ Game Engine

reptoadsLogoSmallerWithBG.png

Quick Info

  • Duration: 24 weeks total, join in last 8

  • Team Size: 25

  • Engine: Custom C++ Engine (Tomorrow Engine)

  • Role: Engine Programmer

  • Platform: Windows, Playstation 4

My Work

More detail regarding my contributions I made to this project, as well as the biggest challenges I faced.

Client-Side Rework

One of the biggest contributions I made to this project is reworking and cleaning up the Client application. This cleanup included restructuring of the architecture, reworking the network code and reconnecting other systems. 

Architecture

As the previous structure of the engine did not facilitate for much growth, we had to rewrite a couple things. I mainly took ownership over the ClientApplication.cpp file. This class is where all the client side systems come together and where the client receives the packets from the server. I made the architecture more consistent, considering ownership, inheritance and access levels into account. Practically implementing the OOP pillars. 

Network Code

As a part of the restructuring, I also took a look at the packets that were sent/received. Together with the other engine programmers that took ownership of the server, I implemented different packet and identified when and what data needs to be sent to the server and received by the client. 

Flowchart of a turn (Programmer Edition)
bottom of page