"The problems isn't the size of the craft image, it's actually implementing different hangar types and sorting craft into hangars."
If this is using my ideas for hangers. 2 hanger type. 1x1 for small and 2x2 for large craft.
Small craft uses services from small and large hangers.
Large craft uses services only from large hangers. Can't use services from small hangers.
Why would this need sorting crafts into hangers?
Similar to the code "requiresBaseFunc" and "provideBaseFunc"
Say the craft is a small flying sub hybrid. Can use 1x1 hanger and subhanger, 2x2 hanger and subhanger.
1x1 hanger provide XYZ service, 2x2 hanger provide ZXS services.
1x1 subhanger provide TXA and 2x2 subhanger provide XAX
Smallsub require XYZ, ZXS, TXA and XAX
Largesub can only use XAX
"That would probably break vanilla compatibility. As I understand it Yankes doesn't want to go the one craft = one hangar type route, but allow multiple hangar types per craft."
My system above answers the problem.