OK, so it’s been about an hour, and here’s where I’m at, so far!
The svn repo link on curseforge doesn’t seem to work:
svn source: https://www.curseforge.com/wow/addons/tank-points/source
Whereas the link on wowace does:
svn source: https://www.wowace.com/projects/tank-points/source
Firstly, the repo I found was using a source code version control management system called SVN, which was quite popular until around 10 years ago when something called git
started to become the defacto source control management system.
There is a site that you may be familiar with called GitHub which is a host for code repositories.
I searched GitHub for tankpoints, and it seems that a couple of people have taken a look somewhat recently:
This is what I found:
This is somewhat helpful, and gives some git repos with the source code. However, they have not preserved the branch history.
Luckily, there is a tool git svn
that seems to be a plugin for git (as it requires an additional install), and can be used to view history.
git svn clone --trunk=/trunk --branches=/branches --branches=/bugfixes --tags=/tags https://repos.wowace.com/wow/tank-points/ tank-points
will clone the SVN code repository from wowace, and place it into a directory named tank-points that has the SVN history and branches available to git.
Rather than using git branch
or git branch --list
to view the branches, since this is a cloned SVN to Git repo, we use git branch -r
to view the branches…
Here’s what they appear to be in this repo:
origin/WoD
origin/mists
origin/tags/2.8.4
origin/tags/2.8.5
origin/tags/2.8.6
origin/tags/r103
origin/tags/r104
origin/tags/r108
origin/tags/r121
origin/tags/r122
origin/trunk
origin/trunk@76
If we checkout the branch origin/tags/2.8.4
and look at the file, TankPoints.toc
, we can see ## Interface: 30200
at the top of the file, indicating it is for a 3.something version of WoW, i.e. WotLK.
Checking out origin/tags/r103
shows ## Interface: 30000
, with is also WotLK or pre-patch. I suppose it is 3.0, while the above is likely 3.2.
This means that the best historic version of the code that I could find is relevant for the 3.0 client.