Bluedog-Design-Bureau icon indicating copy to clipboard operation
Bluedog-Design-Bureau copied to clipboard

Native CWPT Integration | Current: THOR/SATURN

Open DeltaDizzy opened this issue 5 years ago • 12 comments

TBA

DeltaDizzy avatar Oct 05 '19 04:10 DeltaDizzy

By family is probably easier to review for merging.

zorg2044 avatar Oct 05 '19 13:10 zorg2044

Agena family is ready for fact-checking

DeltaDizzy avatar Oct 05 '19 18:10 DeltaDizzy

Starting to wonder if I'll be able to get everything in by the 25th (or is the BDB 1.6.0 due date just a vain hope?)

DeltaDizzy avatar Oct 09 '19 19:10 DeltaDizzy

@KerbalKore did you do the lander parts as well?

DeltaDizzy avatar Nov 04 '19 14:11 DeltaDizzy

I did everything

KerbalKore avatar Nov 04 '19 19:11 KerbalKore

What about MOL, as it is in a different folder?

DeltaDizzy avatar Nov 04 '19 20:11 DeltaDizzy

Also tagged, as it’s a Gemini subfolder @DeltaDizzy

KerbalKore avatar Nov 05 '19 00:11 KerbalKore

Wait it’s not a separate folder, the parts are all directly in the Gemini folder. They are all tagged, but huh.

KerbalKore avatar Nov 05 '19 00:11 KerbalKore

Should these tags come with a :NEEDS[CWPT] to avoid spamming the KSP log with eg:

[LOG 14:55:01.489] PartLoader: Compiling Part 'Bluedog_DB/Parts/Explorer/bluedog_Pioneer4/bluedog_Pioneer4'
[WRN 14:55:01.494] PartLoader Warning: Variable techtag not found in Part

To avoid touching all the files again, consider a separate clean-up patch in one place:

@PART[bluedog*]:HAS[#techTag]:NEEDS[!CWPT]:LAST
{
  !techTag = DEL
}

This at least cleans everything up on the way out if the tag won't be used. If some other tech tree mod comes about and wants to use techTag, it's a single place to change.

DRVeyl avatar May 20 '20 20:05 DRVeyl

Well the idea is for the techtags to be available for any mod to use, regardless of if BDB has updated to let them use it, especially since BDB updates so rarely. What is causing that error?

DeltaDizzy avatar May 20 '20 22:05 DeltaDizzy

That is -the- KSP PartLoader that runs after all MM patching is complete, when it builds the prefab/availablePart parts, warning that it found a parameter for a PART that doesn't belong. So I suggested a patch that runs in :LAST, such that any mod that wants the tag has had access to it before BDB cleans it up.

Since I suggested :LAST, you could actually just delete the NEEDS and not worry about tracking it.

DRVeyl avatar May 21 '20 17:05 DRVeyl

What I may do is add a patch in the Compatibility folder that deletes all techtags in BDB parts duringthe LAST[Bluedog_DB] pass. (for LAST you input a modname)

DeltaDizzy avatar May 21 '20 19:05 DeltaDizzy