Dependencies or Lots First ?

[sticky.widget]

Greetings!

I have a new laptop coming shortly and after much thought and consternation have decided rather than just simply copy over my gigs and gigs of SC4 custom content I'm going to start with a fresh install, wade through the mountains of content available and *try* to be a little more selective about what custom content I install (sigh).  Which brings me to my question...

What would be the best method and order to go about doing this...download most of the main dependency and prop packs first and then lots and custom content or download the custom content first and then go after all the dependencies?

At first I thought the best way would be dependencies first, but maybe not. Maybe the better way is to download lots first, then dependencies so you can run Cleanitol to make sure it's pulling all the replaced or duplicated files out. 

If I go dependencies first then lots, is there a Cleanitol method to pull out all the duplicate/unneeded content after the fact?

I aplogize if this is a NooB question...I use Cleanitol regularly, but have never really started from scratch.  If I'm going to follow through with the huge undertaking, I'd like your input as to the best route to take to hopefully save me a lot of angst in the end....

Cheers !

[catty]

I did that recently, copied my old plugin folder to a flash drive and started from scratch, but didn't download anything as I got the SC4D DVD which is available on this site for a donation of 25 Euros, instant 3 gb plugin folder with no worries about missing dependencies, then slowly put back a few old time favourites that I have gotten from other sites and wouldn't be without ie a factory that makes brown sc4 boxes.

My plugin folder is starting to grow again but at least I know what I am adding in this time as opposed to grabbing everything when I first started out.   

[Andreas]

I'd suggest to pick your favorite BATs and lots first, and make a list of the needed dependencies while you're installing them. Then take that list and install all dependencies that are needed. This will ensure that your plugins folder is as small as possible, with no unnecessary file.

[wes.janson]

I agree with Andreas. I recently re-built my plugins folder and after getting rid of files I never really ended up using and dependancies I had no need for I was able to trim my plugins folder down by 1.5gb