It is a global and system-wide id that always increments. Closed betas or company internal testing will use private branches.Ĭhangenumber: ANY change to a Steam game, public or private get a bump in the change number. Branches can be private though, they can only be accessed via a password to see it's contents. There can be a public beta branches for open betas. Other differently-named, public branches may exist to store older versions of the game, for people to downgrade to, for whatever reason. The current "public" named branch is usually the latest version of the game that can be installed via Steam. Public branches are accessible by everyone. A Package is item that is sold on Steam or can be given away with a key.īranch: A game or application on Steam can be in one or more branches. Package: A collection of one or more depots. It is some sort deployable package of files and data. SteamDB has different entities of items, lets describe some of them so you know what is going on.ĭepot: A collection of contents, whether it is executables, binaries, game data, config data. The team working on TPS has a different approach to Steam change management than the team working on BL2.įirst, some terminology. TPS has many updates, but it seems like two different teams are working on whatever content is there. Mainly, BL2 has more branches and better descriptions of branches and depots than TPS does. While TPS and BL2 are both experiencing a constant stream of updates in the last few weeks, I am going to focus on the BL2 updates. This is not the final word or an authority of what is really happening, just the rant of a fascinated person who loves the BL games and is a professional software developer (but not a game developer) This is an analysis and some educated guesses on what I think is happening with the BL2 (and TPS) SteamDB activity.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |