There has not been a lot of activity on this project for a few months. XanderChaos has not had the time to fix some known bugs that are rather severe and cause Borderlands to be unable to load editied savegames at times. I currently have the time and inclination to fix these bugs so I recently joined XanderChaos on the project development team. I think I have fixed the most severe bugs in the savegame reading and writing code and I am hoping we can release a new official version with these fixes soon.
The SVN source code repository hasn't been used for awhile, but I'm trying to bring it back into a usable form so people will be able to access and test the internal revisions of the source code between releases. To this end I recenty updated the format of the SVN archive to a more standard trunk/branches/tags format and I have imported the latest internal revision of the code into the trunk folder.
The folders of the SVN are now arranged like so:
trunk - This folder contains the most recent working revision of the software. This is where a developer will get the latest code from if they want to work on something. If bug fixes and simple changes need to be made the code will be checked out here and committed back when the change is complete. For more complex changes that will break the code a branch will be used. This should be able to compile at all times.
branches - If revisions need to be made that are not simple and will break the code for a period of time, the trunk will be copied into a subfolder here (a branch) and checkouts and commits will be preformed on the branch. When the revisions are complete the branch will be merged back into the trunk and the branch may be deleted.
tags - When an an official release of the software is made, a copy of the trunk or branch that contains that revision shall be made into a sub-folder here. The work in these folders is completely frozen. No checkouts, commits, or updates will be performed from them. They exist to archive the exact state of the software at the time of any released version so they should never change. If further work needs to be done on something in one of these tags that is not the latest revision (which would be held in trunk), a copy of the code will be made from the sub-folder here into a branches sub-folder and checkouts and updates will be performed from there until a new release is ready at which time there will be a new tag created from that branch. The original tag will not ever be modified.
I have updated the trunk with the latest internal revision so it should be functional if people want to fetch the latest version of the code. Sourceforge.net suffered a hacking attack a few days ago so they were forced to temporarily take the SVN source code viewer offline. This means that for now you can't browse the SVN with your web browser right now, but you *can* use an SVN client to check out the most current code which would be found in the trunk at https://willowtree.svn.sourceforge.net/svnroot/willowtree/trunk . There is also a .ZIP archive of the latest version of the code that was made two days ago but is still current at the moment in the Internal folder in the download section. That folder is likely to be removed in the near future since I have imported the source into the SVN archive, but since it is still current I will leave it there for the time being.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
There has not been a lot of activity on this project for a few months. XanderChaos has not had the time to fix some known bugs that are rather severe and cause Borderlands to be unable to load editied savegames at times. I currently have the time and inclination to fix these bugs so I recently joined XanderChaos on the project development team. I think I have fixed the most severe bugs in the savegame reading and writing code and I am hoping we can release a new official version with these fixes soon.
The SVN source code repository hasn't been used for awhile, but I'm trying to bring it back into a usable form so people will be able to access and test the internal revisions of the source code between releases. To this end I recenty updated the format of the SVN archive to a more standard trunk/branches/tags format and I have imported the latest internal revision of the code into the trunk folder.
The folders of the SVN are now arranged like so:
trunk - This folder contains the most recent working revision of the software. This is where a developer will get the latest code from if they want to work on something. If bug fixes and simple changes need to be made the code will be checked out here and committed back when the change is complete. For more complex changes that will break the code a branch will be used. This should be able to compile at all times.
branches - If revisions need to be made that are not simple and will break the code for a period of time, the trunk will be copied into a subfolder here (a branch) and checkouts and commits will be preformed on the branch. When the revisions are complete the branch will be merged back into the trunk and the branch may be deleted.
tags - When an an official release of the software is made, a copy of the trunk or branch that contains that revision shall be made into a sub-folder here. The work in these folders is completely frozen. No checkouts, commits, or updates will be performed from them. They exist to archive the exact state of the software at the time of any released version so they should never change. If further work needs to be done on something in one of these tags that is not the latest revision (which would be held in trunk), a copy of the code will be made from the sub-folder here into a branches sub-folder and checkouts and updates will be performed from there until a new release is ready at which time there will be a new tag created from that branch. The original tag will not ever be modified.
I have updated the trunk with the latest internal revision so it should be functional if people want to fetch the latest version of the code. Sourceforge.net suffered a hacking attack a few days ago so they were forced to temporarily take the SVN source code viewer offline. This means that for now you can't browse the SVN with your web browser right now, but you *can* use an SVN client to check out the most current code which would be found in the trunk at https://willowtree.svn.sourceforge.net/svnroot/willowtree/trunk . There is also a .ZIP archive of the latest version of the code that was made two days ago but is still current at the moment in the Internal folder in the download section. That folder is likely to be removed in the near future since I have imported the source into the SVN archive, but since it is still current I will leave it there for the time being.