benecaster_get_template_part()

Renders one of Benecaster’s template parts, resolving it through your child theme, then your parent theme, then any directory an add-on registered with benecaster_register_template_directory(), then the plugin’s own copy. This is how you build a page out of Benecaster’s pieces without copying its markup — you get whatever the current theme has overridden, which is the behaviour a podcaster expects when they have customised something.

A theme still wins over everything, add-ons included. An add-on directory sits third, so it can replace a core default but can never outrank an override a site owner wrote by hand.

Pair it with benecaster_locate_template() when you need to know whether a theme has actually overridden a part, and benecaster_get_template_path() when you need the file that would be loaded.