To Git or Not To Git

To Git or Not To Git: A Horrific tragedy of Hubris and Time

By: Pedro Colon 5/26/2023

 

Reference: https://github.blog/2021-10-29-thirteen-short-and-scary-games-plus-source-to-play-or-hack-this-halloween/

Prelude

To Git or Not To Git-That is the question. Since the beginning of time, developers have been finding ways to better work on projects together and to ensure that a safe backup of their work works well. From centralized to distributed, Developers still ponder on the tool that is right for the job. For if a tool can hurt progress, productivity dies and so does the sanity of the developer. This is one of those stories.

Or at least a story of how I managed to make things harder for me all because I didn't carefully read Gits errors and instead set back a good chunk of work which I was able to make up thankfully, but was still terrifying!

Welcome to this story of mine.

Part 1: The Horror, The Horror!

The horror of misreading errors! So what did happened? Well what occurred was that I delegated a task to one of my teammates (shout outs to David Powers, he really did the work towards this final especially with getting the pause menu and FPS counter working)! However, there was a mistake made on my end that is too easy to make. Working on the same binary asset with git! And from there, the horror begins. There was an error that appeared. It told me that there was an issue with two assets. I tried to resolve. In turn, I discard it. And from there, my early hours of work has vanished. I was sad. I was angry. Hope vanished. Divine light severed. What can I do to fix? What can I do? There was only one answer.

Do it all again...but faster!

And so I did. And tedious it was.

Part 2: The Light at The End of The Tunnel

I wish I was able to screenshot the error when it occurred so I can show you. But if I did, then this wouldn't have happened. So maybe it was a blessing in disguise? Who knows honestly. Whatever it may be, I did solved the issue. No matter how painful it was, I was able to regain all the work I done prior. As a matter of fact, I was also able to do some additional work as well, adding in some sounds for the kart and fixing up Hud along with getting the installer working and going. Was it tedious? Yes. But did I learned something? Yes.

So what is the moral then? The moral is quite simple friends: Never give up! Always preserve even when things are rough. You may just surprise yourself with how far you can go!



Comments

Post a Comment

Popular posts from this blog

The Pitfalls of Crafting a Position Placement and Lap Counter for Kart Racing Games

Kart racing games have always been a favorite among gamers, offering thrilling experiences of speed and strategy. Behind the scenes, however, game developers face numerous challenges in creating a seamless Position Placement and Lap Counter system. In this article, we'll explore the intricate web of issues encountered when striving to implement these essential features in kart racing games. 1. Real-time Position Tracking: Creating a Position Placement system that accurately reflects the real-time positions of players on the track is a daunting task. Traditional methods, such as grid-based placement, fail to capture the dynamic nature of kart racing, where players can change positions rapidly. Developers often resort to complex algorithms that require intensive computation to track player movements accurately. 2. Lap Counting Accuracy: Lap counting seems straightforward, but ensuring precise lap detection can be surprisingly intricate. Developers must consider factors like collisio...
Read more

Troubleshooting Unity GameManager Input Handling

Navigating Unity's complex ecosystem of scripts, input handling, and camera management can be challenging. This guide sheds light on the issues faced while implementing input actions in a Unity GameManager script and demonstrates a concise solution. Issue 1: Unresponsive Input Actions At first, the GameManager script wasn't responding to the LocalMultiplayerStart input action. The issue was traced to incorrect syntax usage. By replacing inputActions.Player.LocalMultiplayerStart.actionMap.enabled with inputActions.Player.LocalMultiplayerStart.triggered, the input action was correctly detected and acted upon. Issue 2: Inactive Update Calls Another roadblock was the GameManager's Update method not being called. This led to confusion and halted gameplay mechanics. The issue was mitigated by ensuring that the GameManager script was properly attached to an active GameObject within the scene. Furthermore, script execution order settings were adjusted to ensure proper function call...
Read more

Only one line of code

Image
 Only one line of code      For a while I was having trouble with a part of the drifting where the kart would completely stop at the drift zone. I made sure the trigger for the box collider was on so I was confused on why it would completely stop. I checked and messed with the drifting part of the code that maybe it was a way I made it but it still didn't work. I was working on it so much I reworked the drifting 3 times and even added a second boolean and I had no clue. Then after looking at how I'm calling the Drift method I thought about maybe moving it out of it's own if statement and it worked.     I didn't realize that it stopped moving rather than getting stuck. It was picking one over the other and after changing that it finally worked. I'm not sure if my previous code would have worked but now I'm making it so that the kart would drift after turning into a certain angle. I still can't believe that I overlooked the fixedupdate again.
Read more