Don't Spill Your Beans (WindieGo)

 During the final week of our group project focused on creating a third-person platforming RPG game, a significant challenge emerged with one of the UI elements I was responsible for. The specific UI component, crucial for the overall player experience, suddenly stopped working. This unexpected setback added a layer of complexity during our critical final stages, requiring swift and effective resolution to ensure the project's success. To address the malfunctioning UI element, I immediately delved into debugging to identify the root cause. After thorough analysis, it became apparent that recent changes in other scripts had inadvertently impacted the functionality of the UI component. Recognizing the need for a systematic solution, I undertook a refactoring process to align the affected section of code with the modifications introduced in other parts of our project. This careful adjustment not only resolved the immediate issue but also ensured the seamless integration of our UI el

  During the last week, I dedicated my time to ensuring the final project was in optimal condition for our post-mortem analysis. While conducting the final playthrough of the title, we encountered a sudden crash. Initially, the cause of the crash eluded us. Employing the IDE and the game engine, I systematically tested various features and scrutinized crash reports. Although reproducing the crash proved challenging, recording video during testing allowed for a detailed examination, revealing similarities between occurrences.   Through the use of these diagnostic tools, I identified the crash as resulting from a double call of the power-ups, leading to an access violation. Armed with this insight, I promptly implemented a straightforward safety net to prevent the recurrence of this issue. Author: Justin Bethea Date: 12/14/23

  In the last week of our group project, while immersed in code cleanup and finalizing our Post-Mortem presentation, a notable challenge arose related to the absence of a standardized commenting style within our codebase. The lack of consistency in commenting practices made it challenging for team members to grasp the intricacies of different sections of code, leading to confusion and a slowdown in our progress. The issue of poor commenting not only hindered immediate collaboration but also posed potential challenges for future maintenance and scalability. To address the problem of inconsistent commenting, our team opted for a pragmatic solution. We initiated a discussion to collaboratively define a simple yet effective commenting style that everyone could adopt. This involved agreeing on conventions for documenting functions, explaining complex logic, and providing context for important decisions. While we didn't enforce an overly rigid style, the goal was to establish a set of gu

  This week, our primary emphasis was on refining code, implementing necessary refactors, and addressing bugs as we geared up for our upcoming post-mortem event. The past month posed challenges for our team, as various external commitments vied for our attention during the final days of our time here at Full Sail. Despite these obstacles, we proactively managed our schedules, ensuring that everyone was aligned on project timelines and availability.   Maintaining constant communication and unwavering focus allowed our team to sustain momentum and dedication towards our project goals. As our time at Full Sail nears its conclusion, the Windiego team executed a final, concerted effort to ensure that our project reflects the high standards we set for ourselves. This journey has been nothing short of remarkable, thanks to an amazing team.   From the beginning of our project in month one to its peak in month four, our team collaborated seamlessly, crafting something we can look back o

 I was working on a virtual keyboard and issue I ran into was the sprite sheet missing a few letters.  This is an issue for the player since they need to be able to read what a key is. TEMP FIX WITH THE MISSING SPRITES  To get around this till I could find a new sprite sheet or draw the missing letters. I made a temporary button with text. When I was in the process of drawing the missing letters it occurred to me that they were not missing it was just the style of font that made it seem that way. Author: Krishnie Katie Naidoo Posted on 12/07/2023

  In the latest strides of our Unreal Engine 5 project, my primary focus this week honed in on refining our quest system. A noticeable snag arose as NPCs within the game failed to accurately communicate information to the quest log. The crux of the issue lay in the NPCs misreporting crucial details sourced from their designated data tables, introducing a disruptive glitch that hindered the seamless progression of our game. Specifically, the NPCs were not extracting the correct information from the data tables, jeopardizing the fluidity of the player's journey. To address this dilemma, a targeted solution was implemented. Upon investigating Unreal Engine 5's editor functionalities, it became apparent that the NPCs' exposed properties needed an update. By diligently aligning and fine-tuning these properties, I successfully restored the proper information flow. This intervention ensured that the quest log now updates accurately based on player interactions with NPCs throughout