Introducing radial containers for all of the things! Plus
I won't be using spaceport until spaceport2 is released because it's pretty inconvenient.
.7z Dev 12MB, User 3MB
.zip Dev 25MB, User 4MB
Alternate texture set by Lebannehn (does not contain alternates for the hexpod or aeronautics kit)
ModuleManager Patch Adding HexCans into the Tech Tree by Grays42
The Dev packages, which includes the SpacePort download, include the installed content plus all of the raw assets to allow anybody to add to or alter any of the elements in this pack with as much ease as possible.
It also includes unfinished parts if you want to mess around with them.
The User packages only include the installed content so if you're afraid you might not understand it; or your internet is limited, that's the one for you.
Also useful as structural elements because they have so many nice flat sides
You can also find the development thread here: http://forum.kerbalspaceprogram.com/...sters-20-Ready
This set of parts are released under CC-BY 3.0, you are free to use, alter, or add to as you desire, you may release your works using HexCans under whatever license you desire though I suggest open source as it's good for the community. You may distribute your works however you like.
Rules of Attribution
To make it simple and concrete I require only one thing to consider your released works sufficiently attributing me.
In the .cfg files for all HexCans parts there is the line
"Greys" must remain in that field, you of course can add your own name/names and I do not care about the order.Code:author = Greys
Nothing else is required for the license to be satisfied.Code:author = BobDole & Greys
If you can I would like to have a link to either of the HexCans forum threads in your release thread, it does not need to be prominent, and that is not required.
You are free to include as much of the base HexCans set alongside your add-on as you like with two conditions:
1. Do not distribute the original part set without modification.
If you'd like to make modified variants of the stock parts that is fine, either as part of a greater add-on or a derivative HexCans set, but do not distribute the original parts as is.
2. Try to include only the assets that you need for your add-on
Limiting the HexCan assets that are distributed alongside your add-on to those that are necessary has three main benefits:
It reduces your distribution size which means players have to download less
It eliminates unused assets which KSP will still load, reducing player's memory load if they don't choose to install the main set (marginally)
It helps to prevent conflicts with the main set if assets have changed between your version and mine.
If you experience any bugs please let me know ASAP, either in this thread or in the dev thread.
Thanks for your time!