# Feature Request: Custom Blocks with Python Backend

**URL:** <https://xrp.discourse.group/t/feature-request-custom-blocks-with-python-backend/958>\
**Category:** Blockly programming\
**Created:** [July 15, 2026, 10:44pm UTC](https://xrp.discourse.group/t/feature-request-custom-blocks-with-python-backend/958 "2026-07-15T22:44:03Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Tinker](https://avatars.discourse-cdn.com/v4/letter/t/e47774/32.png) [@Tinker](https://xrp.discourse.group/u/Tinker)\
**Post date:** [July 15, 2026, 10:44pm UTC](https://xrp.discourse.group/t/feature-request-custom-blocks-with-python-backend/958/1 "2026-07-15T22:44:03Z")

</div>

**Feature Request: Custom Blocks with Python Backend**

We’ve been playing Orbit Odyssey with a group of middle schoolers over the summer, and we are really liking the XRP platform (especially the XBS v2 printed parts!).

It would be helpful if there were a way to create and share custom blocks with our students. For example, we have written a field-oriented Mecanum drive in Python, but recreating and sharing that logic using visual blocks is impractical with middle schoolers. We would love a way to define a custom block that maps directly to an underlying Python function so our block-based students can still utilize these.