Provide a description of the KSP bug or improvement
In EditorLogic.Awake(), the inaccessiblePartsFilter is set by the following:
inaccessiblePartsFilter = new EditorPartListFilter<AvailablePart>("inaccessibleParts", (AvailablePart aPart) => aPart.partPrefab != null && aPart.TechRequired != "Unresearcheable", "Cannot be used in the Editor");
"Unresearcheable" is in fact a typo of the word "Unresearchable", which is pretty typical for KSP. A quick search on github shows that 176 mods are using this typo correctly. However, a search for the actual word Unresearchable shows that 133 mods are using this, likely not knowing that this pattern is not correct.
Maybe KSPCF should edit the inaccessiblePartsFilter to include those requiring the Unresearchable node in addition to the Unresearcheable node? It might be better as an optional patch defaulted to off, as this is technically intentionally changing the stock behavior for hundreds of mods (but it is changing the behavior to what they already think should be working)
Provide a description of the KSP bug or improvement
In
EditorLogic.Awake(), the inaccessiblePartsFilter is set by the following:"Unresearcheable" is in fact a typo of the word "Unresearchable", which is pretty typical for KSP. A quick search on github shows that 176 mods are using this typo correctly. However, a search for the actual word
Unresearchableshows that 133 mods are using this, likely not knowing that this pattern is not correct.Maybe KSPCF should edit the inaccessiblePartsFilter to include those requiring the
Unresearchablenode in addition to theUnresearcheablenode? It might be better as an optional patch defaulted to off, as this is technically intentionally changing the stock behavior for hundreds of mods (but it is changing the behavior to what they already think should be working)