You have some options, and the one you may want will depend on how you want to be tied to TweakScale: Option 1: TweakScale as Hard Requirement
#Ksp module manager 2019 Patch#
FancyAddOn :P and want to add a TweakScale patch to a new fancy tank of yours, called.
For Add'On Authors/Maintainers, the magic word is :FOR. Module Manager has some operators to help us to prevent that Fest. So this can be hairy, as it's incredibly easier to trigger a Rogue Patching Fest - i.e., uncontrolled patching on parts leading to indeterministic (and some times, dangerous) state on the part. Since you are The One for your Add'On, you are the maximum authority as how things should behave on your parts, and everybody else can choose to agree with you or to write their own patches in order to override yours. Use Cases I'm an Add'On Author/Maintainer and want to add a TweakScale patch to my parts So let's split this Crash Test Course into "Use Cases", instead of shoving a gazillion of new technical data into your head. Module Manager's documentation is somewhat vast, and besides being not that hard to understand, it's a lot of things to assimilate. At least, for now - someone else can have a better idea later, and I don't have any love for any of my convictions: I throw them alway in the exact instant I'm convinced that something else is better. All of that was somewhat confusing for me at the beginning.īut I can tell you what I think is the better way to write a patch. I have my reasons to call it Add'On, while most of the people like "Mods" more - besides the Forum calling them Add'On and people calling the Moderators "Mods". It's hard to tell the correct/preferred method/way on a somewhat ad-hoc organisation as the KSP Add'On Scene. Module Manager Patches for TweakScale :: Crash Test Course :: Part I
0 kommentar(er)
