Keeping Track of Hacks

[pgowder]

I've seen some threads about tools that people have developed to keep track of installed threads to make upgrading vB and the hacks easier. Now that I've removed all the hacks off my board and will be upgrading to vB3 in the next week, I want to start off right.

Any recommendations?

Thanks

[Zachery]

Htl :)

[pgowder]

Htl :)

Ok, excuse my ignorance, but what is Htl?

[pgowder]

Ok, I found it. But it appears that it doesn't support all hacks, and the hacks have to be formatted for it?

Is that correct?

Are there other apps or tools that people have written?

[NTLDR]

Just click install for each hack you install, you can then get the full list in your User CP here.

[pgowder]

Just click install for each hack you install, you can then get the full list in your User CP here.

True, but I was looking for something a little more comphrensive.

[Xenon]

everytime you isntall a hack, use comments areound it, so you can easily find the hack in your files.

There is nothing more you need...

[Zachery]

I was only suggesting the HTL as thats what it does do

Personally ive never installed so many hacks i didnt know what ive installed

but to quicken things for me

// ## HACK $HACKNAME HACK ##

goes around all my hacks, making it very simple to find ;)

[JustAskJulie]

I'm running into this now. I need to find and remove the hacks I've installed so that I can upgrade my board. The hacks were installed so long ago tho that I have no idea anymore what's a hack and what's not.

[AN-net]

i usually create a new folder in on in my upload files folder and call it "modifed_files" and in that folder for each modification i make i make a new folder and put the file i modified in it. eventually it builds up so you can easily go backwards and never have to make file edits over again or if something goes wrong you dont have to reinstall each hack;) thats just my systematic system