Four Years of BATTLETECH File Creation Visualized
- Thread starter HBS_HighCommand
- Start date
-
We have updated our Community Code of Conduct. Please read through the new rules for the forum that are an integral part of Paradox Interactive’s User Agreement.
Outstanding Run, full of Big and Stompy AWESOMENESS!
Thank you Team HBS... from the bottom of my BattleTech Heart, thank you. :bow:
Thank you Team HBS... from the bottom of my BattleTech Heart, thank you. :bow:
It has been a long and joyous journey. It has been a pleasure to share it. The visualization is really cool.
I saw mitchgit in there! Who allowed him to check anything into the git repo?!? We're all doomed! DOOMED I tells ya! 
I saw mitchgit in there! Who allowed him to check anything into the git repo?!? We're all doomed! DOOMED I tells ya!
I never noticed my own name in there! Yes, I actually MAKE games.
Great video, very informative. Hope it represents especially how much HBS has learned and grown with making and maintaining BATTLETECH.
Looking forward to watch (and play) your further growth in the videogame's industry!
Looking forward to watch (and play) your further growth in the videogame's industry!
Well damn, that music made it whole lot more emotional than I was expecting. *sniff*
Shout-outs to "Firstname Lastname" doing the hard work without even the need to be credited! What a selfless person!
What was the long branch that sprouted off on the upper left hand side about a third of the way through? It basically didn't get touched afterwards. I was expecting it to be the expansions, but as the timeline progressed, that didn't appear to be the case.
My guess, and this is just a guess, is that it was the Backer Beta. Which from my understanding was a branch of the project that was unable to be merged back into the main line since they had diverged too significantly. If i'm wrong, well, one of the HBS peeps can correct me.
I can't be 100%, but if I had to guess it was some build system architecture that got added. Each big branch I believe is a new or different file path, and that build stuff doesn't get used by devs on the regular, so it may even sit outside parts of the Unity Project.
I suspect it's Build stuff because it appears that the person who spawned the branch is our very own Build-and-Git-guru Jesse. He does the hard work of making the game build into an actual playable executable, and wrangling the machines that do it. Additionally this commit was in November of 2017 which is when we started getting serious about the Spring 2018 ship. Finally you see the "py" file count (python scripts) jump from no rank on the list to like 8th. I believe much of the build automation is a python based. Build automation is also fairly static, meaning once it's in place all that happens is small feature additions and tweaks, which explains why the branch didn't grow substantially after being created.
Build automation and creation is not glamorous, but it is vitally important to making a game. Jesse did an incredible job of managing that pipeline delivering build across like 10ish different platforms for testing and release.