Should I expand the tech tree or distribute parts over existing nodes?

[Sharpy]

I'm creating a new 'part pack' mod - Cubesat System. Unlike most existing Cubesat mods that provide ready-made cubesats, my mod consists of a lot of tiny parts - you assemble your cubesat from a lot of distinct (tiny) components. A separate control board (probe core), separate SAS module, separate KerbNet module, generally - a very high granularity; unlike standard KSP stuff where parts are 'aggregates' with probe cores coming with SAS, reaction wheel, weak radio and built-in battery, this one's parts are really 'atomic'. One cubesat, to be actually useful instead of just 'being in orbit' will need good 8 or more modules. If it's to fly anywhere instead of just sitting in one orbit, that number might double.

I'm considering - would it be worth making entirely new R&D nodes - a separate branch splitting off from 'Start' and going all the way to 1000-sci RTG battery for cubesats - or should I rather keep the tech tree untouched and distribute these parts over existing nodes?

I'm fine with either way, but I want to hear what people have to say.

 

 

 

[steedcrugeon]

have you considered using the nodes in the community tech tree? that is a popular tree and a starting point. I'm guessing you'd write the original for stock and then implement the node changes through Module Manager?

[Sharpy]

@steedcrugeon I considered it and I'll probably add it - if I find enough will to go through it

[COL.R.Neville]

use the existing branches its not new tech its just smaller. so if you want put it with the rest of the sas and stuff after Miniaturization 

[Tyko]

Sounds like a great idea. use existing nodes and then write support for CTT. That will give you an audience with people who prefer stock tech tree and with those who like modded trees.