Devlog 2: Adam Mashaw

Problem: Issues with source control

Some of the biggest issues that we have encountered so far have been issues with our source control. Having lost about 2 or 3 days of solid work, we have been fighting it. Every single time that we push there has been an issue, someone didn't get the revision to the code, some people didn't get an update to a blueprint, things like that where we have to go back and figure out why it wasn't actually working. We have tried looking it up, but never made much progress that way. 

All of these issues compound and make it so we can't reach the deliverables that we have set out to achieve. at first we weren't sure how we were going to proceed, if this was just how the rest of development was going to go. We had other smaller issues with development like getting the Gameplay Ability System up and running. I am unfamiliar with getting some of the stuff set up so it took longer than expected to set up the simple things like base attributes and such.

Solution: Talking

After hearing that we all were having similar issues, we were trying to break down exactly why things were breaking, we tried being more careful when we made changes, making sure to add them in the client. We also talked with the professor about these issues that we have had, and he was able to give us way more information about what the source control is able to do, and what it lacks. By listening to the professor and using the tricks that we were able to figure out on our own, the risk of introducing new bugs because of that were minimized. This along with having smaller more commits, so we know what is in them will have a great impact on the future of the project. 

We still do encounter some issues if we forget to do one of the things mentioned above, but after learning what we have, the larger issues have become less and less of a problem, and we can go back to working on the project itself and not lose time to fighting our source control.