[KSP >= 1.3.0] TweakScale - Under Lisias' Management - 2.4.8.6 - 2024-0921

[Lisias]

ANNOUNCE

Release 2.4.8.6 is available for downloading, with the following changes:

• Due recently realised changes on the way CKAN handles alternate downloads, some safeties were implemented to alert the user if by some reason it was installed a non CKAN approved package on a CKAN managed installment.
• Closes Issues:
  • #339 Prevent non CKAN safe binaries from being used on CKAN managed installations.

We are not dead yet.

Scale safe!!!
(and keep launching)

 

Known Issues

• There's a long standing issue on TweakScale™ about scaling ModuleEnginesFX's plumes - some engines' plumes is just not scaled, while others scaled pretty badly. It's something that never worked right on TweakScale™, and it will only be really fixed on TweakScale™ 2.5 (when this thing goes gold)
  • The best workaround (and also the reason I'm dragging my feet on this) is to use SmokeScreen or Waterfall.
    • For SmokeScreen, you need:
      • SmokeScreen itself.
      • Real Plumes (to enable SmokeScreen on Stock parts)
        • Additional Part Sets and Add'Ons may need specialised support not included on Real Plumes.
    • For Waterfall, you need:
      • Waterfall itself.
      • StockWaterfallEffects (to enable SmokeScreen on Stock parts)
        • Additional Part Sets and Add'Ons may need specialised support not included on StockWaterfallEffects.
  • See Issue #27

Disclaimer

By last, but not the least...

Spoiler

No Module Manager, EULA or Forum Publishing Guidelines were harmed during the development of TweakScale™.

But a priest may had...

 

This Release will be published using the following Schedule:

• GitHub, reaching first manual installers and users of KSP-AVC. Right now.
• CurseForge. Right Now.
• SpaceDock. Right Now.

Being a bug fix release, I hushed the thing into everything at once.

Edited 4 hours ago by Lisias
All your Distributions Channels are belong to us.

[JonnyOThan]

I’m pretty confused about the intentions here.  We’ve sorted out the issues of CKAN pulling from GitHub right? And CKAN will not index pre-release packages from GitHub anyway. If you communicate your intentions to the CKAN team maybe we can come to a better solution?

[Lisias]

1 hour ago, JonnyOThan said:

I’m pretty confused about the intentions here.  We’ve sorted out the issues of CKAN pulling from GitHub right? And CKAN will not index pre-release packages from GitHub anyway. If you communicate your intentions to the CKAN team maybe we can come to a better solution?

 The intention is to warn the user that CKAN managed installments should had TweakScale installed by CKAN, and that only the packages I had specifically tested on CKAN should be used. This is meant to prevent non CKAN approved TS packages to be unattendedly installed on CKAN managed installments, avoiding stomping in your toes - one of the main concerns is on the TweakScale.WatchDog component that aims to prevent mishaps going unnoticed on manual installations, but that have some features turned redundant when the rig is managed by CKAN where such mishaps would not happen.

Note that I have a CurseForge specific package too, where another set of rules is used. You will notice on the commit that I created the boilerplate to do the same for CurseForge. As long as I find a way to detect a Curse Installer managed rig, I will do the same there.

The rationale is that things perfectly valid on CurseForge are inconvenient (or plain undesired) under CKAN (and probably vice versa). And manual installations need checks that should not be made on both of them - double guessing CKAN while using CKAN is a bad idea.

I will quote what will be logged on KSP.log if the user do a manual install (from github or, Kraken knows why, CurseForge) on a CKAN managed rig for reference:

	Log.force("**YOUR ATTENTION PLEASE!** This TweakScale packaging is not meant to be used under CKAN. It's usually a bad idea to do manual installings when using CKAN, futurelly this may break things for you! Please CKAN to install TweakScale on CKAN managed rigs.");

And, other that having redundant checks activated, this will be the only change the user installing manually a non CKAN approved package on a CKAN managed rig will see.

Edited 2 hours ago by Lisias
less is more.