> For the complete documentation index, see [llms.txt](https://docs.plummerindustries.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.plummerindustries.com/bumper-mounts/designing-bumpers/choosing-a-bumper-height.md). # Choosing a bumper height Selecting a height to set your bumpers at can impact your designs in a multitude of ways. As an opinion we like to mount them as low to the ground as we can get away with but there is a limit to how low you can go. ## Rules The rules will change year to year on the maximum and minimum mount heights that are legal. Check the current rulebook and design accordingly. ## Intakes and mechanisms Intakes and mechanisms can be over or under the bumper this will most likely be the biggest driver of what your bumper height will be. Do you need a game piece to go under the bumper(2024)? Or do you need the most amount of space above the bumper for a mechanism or intake to reach the ground. ## Game Piece Interaction Since the game pieces change every year this is a topic teams should revisit. Can the game piece be pushed by bumpers? Can the game piece become stuck under bumpers? ## Picking up robots by the bumper Bottom heights lower than or equal to 1/2" from the ground leave no room for fingers to get under the robot and it can drag fabric at times. If you want to pick up your robot from the bumpers we recommend having no less than 3/4" between the bumper backing material(Plywood) and the floor. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.plummerindustries.com/bumper-mounts/designing-bumpers/choosing-a-bumper-height.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.