<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/a4dec44eafdd476894425151396612ea&quot; frameborder=&quot;0&quot; width=&quot;1920&quot; height=&quot;1440&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1440</height><width>1920</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1440</thumbnail_height><thumbnail_width>1920</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/a4dec44eafdd476894425151396612ea-6b284afc35efc4b7.gif</thumbnail_url><duration>40.708333</duration><title>Day 16 - Crash-n-Clash - 01 Plan</title><description>In today&apos;s video, I’m excited to discuss our new tool aimed at preventing clashes on site by creating a crash on clash tool. This tool will allow us to identify and fix intersecting elements with full control over our criteria and intersection rules. Importantly, we’re enhancing the existing Navis workflow rather than replacing it, making our process more powerful within Rave. I encourage everyone to scroll down to the research section so we can prepare for today’s coding session.</description></oembed>