> For the complete documentation index, see [llms.txt](https://ms-kb.msd.unimelb.edu.au/msdmaker/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ms-kb.msd.unimelb.edu.au/msdmaker/msd-model-making-space/card-cutter-1/tips-tricks-and-common-mistakes.md). # Tips, Tricks and Common Mistakes ## Create **Score Lines** When setting up your file for card cutting, it is important to consider the edges of your geometry, as sharp corners and the end of lines can often be torn by the card cutter. A simple way of avoiding this is to insert short score lines along the cut line. ### **How to create score lines** Draw a curve perpendicular to your selected line, offset this 1mm. Select both of the perpendicular curves, use the command **array-curve** to populate these around your selected line. Set the distance between the arrayed elements as far apart, or close together as works for your geometry (eg. 50mm), hit enter. Now use the **split** command to split the curve into segments, **select** the small curve segments and place on the **score layer**. ## Use Labels ![](/files/-M62oJV0PblQpobcNTlo) Its a good idea to label your pieces, its up to you where you want to place these labels inside of the geometry you're cutting, or off to the side (as is pictured above). Labels allow for ease of construction once you've processed your job, and help with trying to work out which piece goes where! Use the Rhino **text** command to create these labels, once you have them use the command **seltext** to select all of the text in your file and run **explode** to make them into vector curves that the Card Cutter will be able to read. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://ms-kb.msd.unimelb.edu.au/msdmaker/msd-model-making-space/card-cutter-1/tips-tricks-and-common-mistakes.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.