Cyber Threat Defender
Cyber Threat Defender is a fun focused collectible card game that introduces kids, ages 11 and up, to cybersecurity terminology and concepts, basic network infrastructure, attack vectors, cyber threats, and defensive countermeasures. The "Fun first" ethos has been the guiding light for the development of Cyber Threat Defender because players that are enjoying themselves will remain engaged and play more often, thus learning more through repetition. Cyber Threat Defender exists as a physical head-to-head game and digital version against AI available for download at the official Center for Infrastructure Assurance and Security CTD digital page. You can learn more about Cyber Threat Defender here.
Cyber Threat Defender Gameplay.
Role
My primary role for the physical version of Cyber Threat Defender has been to handle the production of our cards and maintain a positive working relationship with our vendor. In the past I handled all logistics from the production of the cards to the shipment to our customers and tracking information, however, my role has shifted. Some of the other responsibilities I have regarding CTD are to developed new mechanics for the game, design new cards and booster packs for sponsorships, quality assurance testing, attend conferences to support the game, instruct teachers and students, support tournaments, and conduct research on existing cybersecurity related topics that may fit in the game including malware, defensive software, policies, services, and more. We are working to expand the digital version of CTD into an online multiplayer game for which I am responsible for the frontend and backend code. For this we have selected Playfab for their authentication and server services, while we are using Unity's Netcode for Gameobjects to handle the networking side, including the lobby, and matchmaking.
Lessons Learned
I have learned that nearly everything will take longer than we expect and the bigger the project scope, the bigger the margin for error will be. Estimating project timelines are one of the most difficult tasks as a software developer, especially when other expected or unexpected duties may come into play. Working on CTD digital has taught me how difficult it is to take code that is made for single player and repurpose it for a multiplayer game. Since there are very little comments within the code it has further driven home the importance of documentation as well. I had very little knowledge of backend development before this project so I have learned a lot about network topology, authentication, and best practices for developing multiplayer games.
I've also gained a deeper understanding of the full product pipeline, logistics, communication, and UTSA policies regarding bids, contracts, and conducting business with overseas organizations.