LDraw.org Discussion Forums
Incomplete list in the section on patterned parts - Printable Version

+- LDraw.org Discussion Forums (https://forums.ldraw.org)
+-- Forum: General (https://forums.ldraw.org/forum-12.html)
+--- Forum: Help (https://forums.ldraw.org/forum-13.html)
+--- Thread: Incomplete list in the section on patterned parts (/thread-29465.html)



Incomplete list in the section on patterned parts - Manfred Schaefer - 2026-03-30

Hello,

I viewed the list of all patterned parts for 22385 and noticed that the list was incomplete. For example, all parts relating to Nexo Knights were missing.

   

The following image shows the missing parts in list form.

   

Is there an error in the presentation here?

Regards

Manfred


RE: Incomplete list in the section on patterned parts - Orion Pobursky - 2026-03-30

The NEXO knight patterns break the naming convention. I'm going to have to code them in as a special exception.


RE: Incomplete list in the section on patterned parts - Manfred Schaefer - 2026-04-03

(2026-03-30, 21:41)Orion Pobursky Wrote: The NEXO knight patterns break the naming convention. I'm going to have to code them in as a special exception.

Why do the NEXO Knight pattern break the naming convention?
Is there a simple way to change the header so that you don’t have to write an exception for this case?
Perhaps I could take care of that and send you the files with the header updated.

Best regards,

Manfred


RE: Incomplete list in the section on patterned parts - Orion Pobursky - 2026-04-03

(2026-04-03, 18:20)Manfred Schaefer Wrote: Why do the NEXO Knight pattern break the naming convention?
Is there a simple way to change the header so that you don’t have to write an exception for this case?
Perhaps I could take care of that and send you the files with the header updated.

Best regards,

Manfred

It's not a header thing. It's because the filename uses pNNN (where N is a number 0-9). Right now the only legal 3 character codes are p[cd]XX for Collectible Minifigures.

We probably should move them all from pNNN to p0NNN but that should be automated via custom backend code.