net-lisias-ksp / KSP-Recall

Recall for KSP blunders, screw ups and borks.
GNU General Public License v2.0
25 stars 2 forks source link

Find a way to survive KSPCF's ~~Stupidity~~ *Less Than Smartness*. #62

Closed Lisias closed 1 year ago

Lisias commented 1 year ago

So, KSPCF decided to blindly disable KSP-Recall, whatever their fixes are active or not.

https://github.com/KSPModdingLibs/KSPCommunityFixes/issues/124

https://github.com/KSPModdingLibs/KSPCommunityFixes/blob/1.24.6/GameData/KSPCommunityFixes/MMPatches/ModSupport/KSPRecall.cfg (currently the latest)

@PART[*]:HAS[@MODULE[Refunding]]:NEEDS[KSPRECALL-REFUNDING]:FINAL
{
    !MODULE[Refunding]{}
}

@KSP-Recall:AFTER[999_KSP-Recall]
{
  @INSTALLED
  {
    @Refunding = false
  }
}

And there's no way I can civilly overcome this crap, I will need to brute force my way on the problem.

OBJECTIVE

Find the less brute and intrusive way to allow users to activate the updated Refunding if this is what they want.

Some people is going to yell on me for sure - as it would be any difference by now. :/

Lisias commented 1 year ago

Hope to had made someone more happy today. :D

Lisias commented 1 year ago

Well, this is what I had done:

  1. Split the current Refunding Stunt in two PartModules
    • One will deal exclusively to the original problem
    • The other will try to handle the float precision problem
  2. And, yeah, a new MetaResource will be added.
    • (sigh)
  3. Both PartModules can be individually activated or deactivated.
Lisias commented 1 year ago

Implemented on commit https://github.com/net-lisias-ksp/KSP-Recall/commit/6f7aa4c09ef8e543445422b493716ce70d806561

Additionally, the Meta Resources are not created anymore when they are not needed. This will shrink a bit the surface of the exposition of the solutionhack.

Lisias commented 1 year ago

Now I need to retest the following Issues:

Lisias commented 1 year ago

Oukey. All tests are good. Closing this.