Bug #19524
Updated by marr75 over 5 years ago
Several popular mods add new categories and set `category = none` in part configs to take advantage of these new categories. The `none` category is also used to hide parts, however (asteroids, parts that have been renamed/updated, etc.).
In every instance I could find that a stock/dlc part had `category = none`, the part also had `TechHidden = True` or `TechRequired = Unresearcheable`, so replacing the opening the condition of BasePartCategorizer.PartMatchesSearch with `part.category == PartCategories.none && (part.TechHidden || part.TechRequired == "Unresearcheable")` would solve the issue quickly and easily.
Another option would be to add a value to the ``PartCategories` enum ("Other", "ModAdded", "Uncategorized", etc.).
In every instance I could find that a stock/dlc part had `category = none`, the part also had `TechHidden = True` or `TechRequired = Unresearcheable`, so replacing the opening the condition of BasePartCategorizer.PartMatchesSearch with `part.category == PartCategories.none && (part.TechHidden || part.TechRequired == "Unresearcheable")` would solve the issue quickly and easily.
Another option would be to add a value to the ``PartCategories` enum ("Other", "ModAdded", "Uncategorized", etc.).