<![CDATA[CrochetPARADE forum

<![CDATA[CrochetPARADE forum - All Forums]]> https://crochetparade.org/crochetforum/ Thu, 23 Apr 2026 09:54:09 +0000 MyBB <![CDATA[How to sew or use zips]]> https://crochetparade.org/crochetforum/showthread.php?tid=63 Sun, 29 Mar 2026 22:33:06 +0000 dcampbellg]]> https://crochetparade.org/crochetforum/showthread.php?tid=63
I am working on a pattern were I need to stitch two separate components and then work in the round after stitching both together. I've done it in real life and it works really well, but I want to do it in CrochetPARADE to test the shape for the rest of the pattern.

This is my code:

#Instructions originally written in CrochetPARADE 1.0 language.
DEF Confused

tart_at=&start_at^A(start):B~A-B::!-skip-A;B-0.0001-A
DOT:inflate=2
ring.R
[6*sc]@R
[6*sc2inc]
[sc2inc,sc],[sc2inc,sc],[sc,sc@[2,4].Z[0],sc.Z[2]],[sc.Z[4],sc@[2,6],sc],[sc2inc,sc],[sc2inc,sc]
start_anew
[ch,[2*ch],ch.Z[3]],turn
[sc.Z[1],3sc],sc3inc,sc@[5,0],sc@[5,1],sc@[5,2],sc@[5,3].Z[5]

#Sewing together
COLOR:magenta
DEF Confused

s0=&ss0^:B~::B-0.180000-!
DEF Confused

s1=&ss1^A(ss2tog):B~A-B::!-1-A;B-0.180000-A
DEF Confused

s1start=&start_at^A(hidden):B~A-B::!-skip-A;B-0.180000-A

#Zips/Caps
(ss1start)@Z[0],(ss0)@Z[1]
(ss1start)@Z[2],(ss0)@Z[3]
(ss1start)@Z[4],(ss0)@Z[5]

I got the Zips code from your video on 3D Model to CrochetPARADE. I wanted to make the zips smaller or practically with a 0 length, but it causes errors. What do you recommend for joining the two pieces above?

Thanks in advance!

.png

Screenshot 2026-03-29 183055.png (Size: 64.41 KB / Downloads: 0) ]]>
I am working on a pattern were I need to stitch two separate components and then work in the round after stitching both together. I've done it in real life and it works really well, but I want to do it in CrochetPARADE to test the shape for the rest of the pattern.

This is my code:

#Instructions originally written in CrochetPARADE 1.0 language.
DEF Confused

s0=&ss0^:B~::B-0.180000-!
DEF Confused

s1=&ss1^A(ss2tog):B~A-B::!-1-A;B-0.180000-A
DEF Confused

Screenshot 2026-03-29 183055.png (Size: 64.41 KB / Downloads: 0) ]]> <![CDATA[New experimental tool: Plain English → CrochetPARADE translator]]> https://crochetparade.org/crochetforum/showthread.php?tid=62 Fri, 13 Mar 2026 18:11:37 +0000 admin]]> https://crochetparade.org/crochetforum/showthread.php?tid=62
I added a new experimental tool to CrochetPARADE that tries to translate plain-English crochet instructions into CrochetPARADE code.

Warning: the generated code can very possibly be wrong even when the tool succeeds, so please check everything carefully. It should be treated as a rough draft, not as reliable output.

A few limitations:

-- it is not AI so it's success depends strongly on the exact phrasing
-- it assumes US crochet stitch names
-- some patterns or rows will fail
-- some will translate only partially
-- some may parse and still produce wrong CrochetPARADE code

So if you use it, use it on one pattern at a time, inspect the result, and use the Debug button when something looks suspicious.

Also, the proper reference for learning CrochetPARADE is still the manual and the examples in the drop-down menu on the main website. This translator is only a convenience feature and is not meant to replace those.

Still, even with these limitations, it may be useful as a starting point for producing a first draft from written crochet instructions.]]>
I added a new experimental tool to CrochetPARADE that tries to translate plain-English crochet instructions into CrochetPARADE code.

Warning: the generated code can very possibly be wrong even when the tool succeeds, so please check everything carefully. It should be treated as a rough draft, not as reliable output.

A few limitations:

-- it is not AI so it's success depends strongly on the exact phrasing
-- it assumes US crochet stitch names
-- some patterns or rows will fail
-- some will translate only partially
-- some may parse and still produce wrong CrochetPARADE code

So if you use it, use it on one pattern at a time, inspect the result, and use the Debug button when something looks suspicious.

Also, the proper reference for learning CrochetPARADE is still the manual and the examples in the drop-down menu on the main website. This translator is only a convenience feature and is not meant to replace those.

Still, even with these limitations, it may be useful as a starting point for producing a first draft from written crochet instructions.]]> <![CDATA[CrochetPARADE documentation: physics engine descripiton]]> https://crochetparade.org/crochetforum/showthread.php?tid=61 Mon, 16 Feb 2026 11:20:42 +0000 admin]]> https://crochetparade.org/crochetforum/showthread.php?tid=61
I few of you have contacted me privately to ask about the internals of the physics engine. The documentation is here (you can also access it from the help menu on CrochetPARADE):

Physics engine algorithm

Periphery extraction

The initial documentation was generated automatically from the code. I then reviewed it for accuracy and added explanations to justify key algorithmic choices.]]>
I few of you have contacted me privately to ask about the internals of the physics engine. The documentation is here (you can also access it from the help menu on CrochetPARADE):

Physics engine algorithm

Periphery extraction

The initial documentation was generated automatically from the code. I then reviewed it for accuracy and added explanations to justify key algorithmic choices.]]> <![CDATA[New STL Export used for Resizing Crochet Patterns + 3D‑Print a 3D Model of a Crochet]]> https://crochetparade.org/crochetforum/showthread.php?tid=60 Mon, 16 Feb 2026 11:01:28 +0000 admin]]> https://crochetparade.org/crochetforum/showthread.php?tid=60
1. **Resizing / rescaling crochet patterns** (by remeshing the STL with more/fewer stitches in CrochetPARADE Remesher)
2. **3D printing** a physical 3D model of your crochet project (from the same STL)

Resizing a crochet pattern (CrochetPARADE → STL → Remesher → new instructions)

1. Start with your CrochetPARADE instructions (your original pattern).
2. Calculate the 3D model (press “Calculate and show model in 3D”, or press Shift+Enter in the editor).
3. Go to “Tools” → “Find project periphery/Save 3D Model to STL”.
4. Enable “Save detected 3D model surface as STL file”.
5. Run/Re-run the periphery tool to download the STL file.
6. Open CrochetPARADE Remesher and load the STL.
7. Change `L` to control how many stitches you get:
* smaller `L` → more stitches / higher resolution
* larger `L` → fewer stitches / lower resolution
8. Remesh, then copy the generated CrochetPARADE instructions back into CrochetPARADE and render to verify.
9. Iterate on `L` until the stitch count / resolution matches what you want.

3D printing the 3D model

1. Export the STL using the same steps as above.
2. Open the STL in Blender for example.
3. Scale and print.]]>
1. **Resizing / rescaling crochet patterns** (by remeshing the STL with more/fewer stitches in CrochetPARADE Remesher)
2. **3D printing** a physical 3D model of your crochet project (from the same STL)

Resizing a crochet pattern (CrochetPARADE → STL → Remesher → new instructions)

1. Start with your CrochetPARADE instructions (your original pattern).
2. Calculate the 3D model (press “Calculate and show model in 3D”, or press Shift+Enter in the editor).
3. Go to “Tools” → “Find project periphery/Save 3D Model to STL”.
4. Enable “Save detected 3D model surface as STL file”.
5. Run/Re-run the periphery tool to download the STL file.
6. Open CrochetPARADE Remesher and load the STL.
7. Change `L` to control how many stitches you get:
* smaller `L` → more stitches / higher resolution
* larger `L` → fewer stitches / lower resolution
8. Remesh, then copy the generated CrochetPARADE instructions back into CrochetPARADE and render to verify.
9. Iterate on `L` until the stitch count / resolution matches what you want.

3D printing the 3D model

1. Export the STL using the same steps as above.
2. Open the STL in Blender for example.
3. Scale and print.]]> <![CDATA[CrochetPARADE Remesher: Turn a 3D Model Into Crochet Instructions]]> https://crochetparade.org/crochetforum/showthread.php?tid=59 Sat, 14 Feb 2026 11:04:13 +0000 CrochetPARADE]]> https://crochetparade.org/crochetforum/showthread.php?tid=59
I’m excited to announce a new tool on CrochetPARADE: CrochetPARADE Remesher. In short: you give it a 3D model (an `STL` file), and it generates crochet instructions in the CrochetPARADE language that (when rendered/simulated) reproduce the shape as a crocheted surface.

What it does (from a crocheting perspective)

- You crochet in rounds only (no turning chains / no back-and-forth rows). The Remesher grows the fabric outward on the surface, round by round.
- Two ways to start:
- Magic Ring: you pick (or let it infer) a ring point + axis + stitch direction.
- Starting Chain: you pick a chain midpoint + axis + number of chains, and it grows from that.
- It can use multiple yarns when the shape is complicated (thin parts, deep concavities, separate “pockets”, etc.).
- When independently-grown regions meet, it can emit “sewing” edges (zips) to join them cleanly.
- You can manually intervene when needed: if the automatic stitch layout gets stuck (or if you want creative control), you can pause at specific points and inject your own moves, such as a short sequence of stitches, starting/ending a yarn, or forcing a zip. The Remesher will continue from there and incorporate your edits into the final pattern.
- You get:
- a 3D preview of the crocheted surface (so you can visually inspect what it produced), and
- the CrochetPARADE instructions you can copy/paste and render on the CrochetPARADE website.

What it cannot do (current limitations)

- The input `STL` should be a closed (watertight) surface (no holes / no open boundaries).
- The stitch plan is round-based only (again: no turning chains yet).
- Very fine stitch size (small `L`) can explode stitch count and make runs heavy; in the browser you can hit WebAssembly memory limits. (If that happens, use a larger `L` or the desktop app build.)

How to try it

- On crochetparade.org, click the **Remesher** button in the CrochetPARADE toolbar.
- Load an STL, choose your seed (Magic Ring or Starting Chain), tune settings if needed, then press **Calculate**.

A few technical notes (for those interested)

- The backend is a surface remesher that grows a stitched patch while maintaining a frontier (the current boundary of the crocheted surface). At each step it tries a small set of stitch operations (the classic “stitch / decrease / increase”-style moves; it supports different stitch heights: ss, sc, hdc, dc, etc), checks a bunch of geometric/topological guards (overlap, surface proximity, etc.), and commits the best candidate.
- When it gets stuck, it can backtrack to a previous snapshot, and it has an adaptive relaxation ladder that selectively loosens certain epsilons/guards to escape local dead-ends.
- If you want to report a failure, the most useful bundle is: the input STL + exported settings JSON + the run log (`output.out`) + the saved output folder.

Some screenshots

Input model:

.png

Screenshot From 2026-02-13 19-51-21.png (Size: 221.63 KB / Downloads: 0)
Remeshed model:

.png

Screenshot From 2026-02-13 19-51-27.png (Size: 513.01 KB / Downloads: 0)
Model rendered in CrochetPARADE from the generated crochet instructions:

.png

Screenshot From 2026-02-13 19-54-19.png (Size: 407.27 KB / Downloads: 0)

Happy crocheting!]]>
I’m excited to announce a new tool on CrochetPARADE: CrochetPARADE Remesher. In short: you give it a 3D model (an `STL` file), and it generates crochet instructions in the CrochetPARADE language that (when rendered/simulated) reproduce the shape as a crocheted surface.

What it does (from a crocheting perspective)

- You crochet in rounds only (no turning chains / no back-and-forth rows). The Remesher grows the fabric outward on the surface, round by round.
- Two ways to start:
- Magic Ring: you pick (or let it infer) a ring point + axis + stitch direction.
- Starting Chain: you pick a chain midpoint + axis + number of chains, and it grows from that.
- It can use multiple yarns when the shape is complicated (thin parts, deep concavities, separate “pockets”, etc.).
- When independently-grown regions meet, it can emit “sewing” edges (zips) to join them cleanly.
- You can manually intervene when needed: if the automatic stitch layout gets stuck (or if you want creative control), you can pause at specific points and inject your own moves, such as a short sequence of stitches, starting/ending a yarn, or forcing a zip. The Remesher will continue from there and incorporate your edits into the final pattern.
- You get:
- a 3D preview of the crocheted surface (so you can visually inspect what it produced), and
- the CrochetPARADE instructions you can copy/paste and render on the CrochetPARADE website.

What it cannot do (current limitations)

- The input `STL` should be a closed (watertight) surface (no holes / no open boundaries).
- The stitch plan is round-based only (again: no turning chains yet).
- Very fine stitch size (small `L`) can explode stitch count and make runs heavy; in the browser you can hit WebAssembly memory limits. (If that happens, use a larger `L` or the desktop app build.)

How to try it

- On crochetparade.org, click the **Remesher** button in the CrochetPARADE toolbar.
- Load an STL, choose your seed (Magic Ring or Starting Chain), tune settings if needed, then press **Calculate**.

A few technical notes (for those interested)

- The backend is a surface remesher that grows a stitched patch while maintaining a frontier (the current boundary of the crocheted surface). At each step it tries a small set of stitch operations (the classic “stitch / decrease / increase”-style moves; it supports different stitch heights: ss, sc, hdc, dc, etc), checks a bunch of geometric/topological guards (overlap, surface proximity, etc.), and commits the best candidate.
- When it gets stuck, it can backtrack to a previous snapshot, and it has an adaptive relaxation ladder that selectively loosens certain epsilons/guards to escape local dead-ends.
- If you want to report a failure, the most useful bundle is: the input STL + exported settings JSON + the run log (`output.out`) + the saved output folder.

Some screenshots

Input model:

.png

Screenshot From 2026-02-13 19-51-21.png (Size: 221.63 KB / Downloads: 0)
Remeshed model:

.png

Screenshot From 2026-02-13 19-51-27.png (Size: 513.01 KB / Downloads: 0)
Model rendered in CrochetPARADE from the generated crochet instructions:

.png

Screenshot From 2026-02-13 19-54-19.png (Size: 407.27 KB / Downloads: 0)

Happy crocheting!]]> <![CDATA[Crochet Along Back Centre of Oval]]> https://crochetparade.org/crochetforum/showthread.php?tid=58 Sat, 03 Jan 2026 22:07:02 +0000 boredwillow]]> https://crochetparade.org/crochetforum/showthread.php?tid=58
I'm loving the app for helping visualise designing amigurumi! But I can't figure out how to do one thing that I had in part of my pattern:

I'm trying to make an oval and then, after a number of rows, sc across the back centreline to create a hard fold along the length (to make the inside of a mouth)

Basically I want to do the following in a round:
1) start crocheting around the oval as normal;
2) stop crocheting around when I reach the centreline (ie in line with the starting chain);
3) sc across the back of the oval around the posts of the stitches (and around the starting chain itself), until I reach the other end of the centreline; and then
4) continue crocheting around the oval from there to the beginning of the round

(similar to how this pattern makes the inside of the mouth, except using an oval instead of a circle)

Any help would be amazing!

So far I have this:

Code:
DEF: htr=&half-treble crochet^A(htr):B~A-B::!-1-A;B-2.5-A

(11ch.R1).R1A, turn

(sk, 9sc, sc4inc)@R1, (sk, 8sc, sc3inc, ss)@R1A~

2(8sc, 4inc)

2(8sc, 4(sc, inc))

2(8sc, 4(inc, 2sc))

2(8sc, 4(3sc, inc))

2(8sc, 4(inc, 4sc))

2(8sc, 4(5sc, inc))

hdc, 2dc, 2htr, 2dc, 3hdc, 2sc, 3hdc, 5dc, 4htr, 

...\travelling across the back of the piece\26sc, 

...\back around the edge, finishing the round\4htr, 5dc, 3hdc, 2sc, 2hdc

]]>
I'm loving the app for helping visualise designing amigurumi! But I can't figure out how to do one thing that I had in part of my pattern:

I'm trying to make an oval and then, after a number of rows, sc across the back centreline to create a hard fold along the length (to make the inside of a mouth)

Basically I want to do the following in a round:
1) start crocheting around the oval as normal;
2) stop crocheting around when I reach the centreline (ie in line with the starting chain);
3) sc across the back of the oval around the posts of the stitches (and around the starting chain itself), until I reach the other end of the centreline; and then
4) continue crocheting around the oval from there to the beginning of the round

(similar to how this pattern makes the inside of the mouth, except using an oval instead of a circle)

Any help would be amazing!

So far I have this:

Code:
DEF: htr=&half-treble crochet^A(htr):B~A-B::!-1-A;B-2.5-A

(11ch.R1).R1A, turn

(sk, 9sc, sc4inc)@R1, (sk, 8sc, sc3inc, ss)@R1A~

2(8sc, 4inc)

2(8sc, 4(sc, inc))

2(8sc, 4(inc, 2sc))

2(8sc, 4(3sc, inc))

2(8sc, 4(inc, 4sc))

2(8sc, 4(5sc, inc))

hdc, 2dc, 2htr, 2dc, 3hdc, 2sc, 3hdc, 5dc, 4htr, 

...\travelling across the back of the piece\26sc, 

...\back around the edge, finishing the round\4htr, 5dc, 3hdc, 2sc, 2hdc

]]> <![CDATA[Update: Edge Work Made Simple: Periphery Finder + INDEX_ARRAY + SORT_LABEL]]> https://crochetparade.org/crochetforum/showthread.php?tid=57 Mon, 22 Dec 2025 00:59:04 +0000 CrochetPARADE]]> https://crochetparade.org/crochetforum/showthread.php?tid=57
I made a major update to CrochetPARADE. It includes a couple of expansions to the language (see below) as well as a new tool: Find project periphery (in the Tools menu). The Periphery finder is all about making edge work (borders, edgings, joining, finishing rounds, attaching motifs, picking up stitches along a side, etc.) much less fiddly in CrochetPARADE.

In crochet, the periphery or border is where so many practical and decorative things happen. It’s where you add a clean border, where you join panels such as granny squares, where you pick up stitches along the side of rows, and where you often “finish” a shape. If you’ve ever added a border to a blanket or motif, you know the edge/finish step is basically its own mini-project. And even in plain “add a border” scenarios, picking up stitches evenly along an edge is one of those deceptively tricky steps that can make things ruffle or warp if you just “pick up everything.”

But if you’re not crocheting in the round, say you’re working rows with turns, attaching motifs (Irish crochet!), or anything where the boundary is built from ends of rows + possibly side posts + turning chains + joins, then the stitches that are consecutive along the boundary are often not consecutive in the order you crocheted them. That’s exactly what makes “crochet around the edge” annoying in a text-driven workflow: you need to find boundary stitches one-by-one, and if you want to label them sequentially (for example with something like A[k++]) it quickly turns into a “where am I on the edge?” scavenger hunt.

So this update is about giving CrochetPARADE a real periphery workflow: find it, visualize it, edit it when needed, and then label it in a way that makes it easy to work stitches in the periphery, and in a way that stays stable even as you keep editing/refactoring the project. (Which is the whole point of CrochetPARADE’s “precise text → 3D model workflow.)

1. Find project periphery

This adds a new workflow under **Tools → Find Project Periphery**.

Think of it as: **“show me the stitches that are on the outside edge of this piece, in the order I’d actually work them if I were crocheting along the edge.”**

That “in the order I’d actually work them” part is the key. In anything made with rows + turns (or motifs that get attached), the stitches that touch each other along the outside edge are often *not* next to each other in your written instructions. CrochetPARADE now finds the *edge stitches* for you and gives you an edge-walk order you can use for borders, joining, and finishing.

What you’ll see:

* One (or sometimes a few) **possible peripheries**. Pick one and CrochetPARADE highlights it on the 3D model so you can sanity-check it quickly.
* If your pattern text is expanded down to individual stitches, it can also **highlight those exact stitches in the editor** (so you can edit or label them precisely).

A typical “crocheter workflow” looks like:

* Build / calculate your project as usual.
* Run **Tools → Find Project Periphery**, pick the periphery that looks right, and check the highlight.
* If you want the periphery stitches highlighted in the text as well: run **Tools → Expand instructions** (select the option to “run twice”).
* Use the tool’s **Apply label to periphery stitches** section to stamp labels *around the edge in edge order*.

* You can label them with a simple label (like `Edge`, which can be sorted in periphery-adjacent order using SORT_LABEL, see below) or a numbered label (like `Edge[k++]` or `Edge[k]; the latter could be indexed with an INDEX_ARRAY, see below).
* There’s an option to reverse the order, which is handy depending on whether you want to go clockwise/counterclockwise around the piece.

And when the automatic periphery is *almost right* but you want to tweak it (lace holes, very openwork edges, multi-piece joins, “I only want this outer side”, etc.) there’s a **Custom Periphery editor**:

* You can define the periphery as a list of **pairs of stitches that are neighbors on the edge**, one per line, like:
`stitch1 -- stitch2`
* CrochetPARADE will then treat that as a custom periphery and will try to walk it in order.
* With the editor open, you can **Alt+Click edges on the 3D model** to add them to the list, which is a nice “pick it off the model” way to fine-tune the boundary.

2. Update to the CrochetPARADE language: New labeling with INDEX_ARRAY and SORT_LABEL

This update is about one practical thing: labeling a set of stitches in a specific order without turning your whole pattern into a soup of stitches with labels such as sc.Edge[3] with numbers that are not sequential in the order they were worked in (but are sequential in some other sense, in periphery order for example).

So: CrochetPARADE now supports two ways to keep labels *ordered* in a way other than the order in which the labeled stitches were worked.

### A) INDEX_ARRAY

`INDEX_ARRAY:` lets you keep your stitch labels looking clean (like `Edge[k]`) while storing the actual list of numbers k *somewhere else*.

So let's say you want to mark the edge of the pattern in the example below:

6ch,turn
[sk,ch,5sc,turn
]*4

which is a simple single crochet swatch. The periphery is the first and last row as well as the edge pieces. Taking account of the turns, if one wants to label the stitches in sequential order around the periphery, one had to do it by hand before. Now with the periphery tool, one can Expand Instructions; Find project periphery and label stitches with Edge[k++] (or label of your choice) to get the following ugly mess:

[[[ch].Edge[9]],[[ch].Edge[10]],[[ch].Edge[11]],[[ch].Edge[12]],[[ch].Edge[13]],[[ch].Edge[14]]],turn
[sk,[[ch].Edge[15]],[sc,sc,sc,sc,[[sc].Edge[8]]],turn
],[sk,[[ch].Edge[7]],[sc,sc,sc,sc,[[sc].Edge[16]]],turn
],[sk,[[ch].Edge[17]],[sc,sc,sc,sc,[[sc].Edge[6]]],turn
],[sk,[[ch].Edge[5]],[[[sc].Edge[4]],[[sc].Edge[3]],[[sc].Edge[2]],[[sc].Edge[1]],[[sc].Edge[0]]],turn
]

with Edge[k] going sequentially from 0 to 17 around the periphery (taking account of the turn's). The indexed labels have their indices baked in. So, if you wanted to do Tools->Simplify instructions, the simplification will stumble because of the non-sequential indices (non-sequential in crochet order). Even after selecting: "Attempt to simplify numerical indexing..." in the Simplify Instructions dialog, we get (after replacing the automatically generated index "vara" with "k" for brevity):

[ch].Edge[$k=9$k],5*[[ch].Edge[++k]],turn
sk,[ch].Edge[++k],4sc,[sc].Edge[$k=8$k],turn
sk,[ch].Edge[--k],4sc,[sc].Edge[$k=16$k],turn
sk,[ch].Edge[++k],4sc,[sc].Edge[$k=6$k],turn
sk,[ch].Edge[--k],5*[[sc].Edge[--k]],turn

With an INDEX_ARRAY, the above simplifies to (and yes, many of the square bracket can be deleted; this is what the code returns automatically):

INDEX_ARRAY:k={9,10,11,12,13,14,15,8,7,16,17,6,5,4,3,2,1,0}
6*[[ch].Edge[k]],3*[turn
sk,[ch].Edge[k],4sc,[sc].Edge[k]],turn
sk,[ch].Edge[k],5*[[sc].Edge[k]],turn

And in this case pattern simplifiction works much better as it sees the same label Edge[k] and the non-sequential indices are saved in the INDEX_ARRAY field.

And yes: the periphery tool generates this for you automatically when you label the periphery with something like `Edge[k]`. The steps are: Expand Instructions; Find project periphery and label stitches with Edge[k] (or label of your choice); Simplify Instructions.

### B) SORT_LABEL

Sometimes you don’t want indexed labels at all. You just want:

* “these stitches are the edge stitches,” labeled `Edge`,
* but you still want CrochetPARADE to remember the *order around the edge* (so later steps that say “work around Edge” by typing say 18*sc@Edge)

That’s what `SORT_LABEL:` is for.

It keeps the stitch text simple (for example using a label `.Edge`), while storing the “walk around the edge” order in a SORT_LABEL. For the example above, it takes the form:

SORT_LABEL:Edge={17,16,15,14,13,12,11,8,7,0,1,2,3,4,5,6,9,10}
6*[[ch].Edge],3*[turn
sk,[ch].Edge,4sc,[sc].Edge],turn
sk,[ch].Edge,5*[[sc].Edge],turn

And again: the periphery tool generates this automatically when you apply a non-numbered label to the periphery. The steps are: Expand Instructions; Find project periphery and label stitches with Edge (or label of your choice); Simplify Instructions.

If you want to mark different parts of the edge with different labels, use the Edit edges button in the periphery tool to delete edges that are not part of say the bottom/right/left/top edge. Each time you edit it, you an save it as a Custom periphery. Then you an apply separate labels to each part of the periphery. Here is an example of a swatch with Top and Bottom edges labeled, and separated edgings worked into them in different colors (once rendered, click on the 3d canvas, and press 'c' to see the colors):

COLOR:Yellow
6*[ch.Bottom],3*[turn
sk,ch,5sc],turn
sk,[ch].Top,5*[sc.Top],turn
SORT_LABEL:Top={0,1,2,3,4,5}
SORT_LABEL:Bottom={0,1,2,3,4,5}
COLOR:Blue
[start_at,ch,5sc]@Top
COLOR:Red
[start_at,ch,5sc]@Bottom

---

# Additionally (just mentioning these):

* The undo Ctrl+Z / Cmd+Z (and the redo Ctrl+Shift+Z or Ctrl+Y) is now a much better history tracker while editing patterns.

* The stitch highlighting mechanism (in the editor and the 3D canvas) is more robust and the different types of highlights have different colors.

* Improved error reporting.

* Produce errors when unsupported stitch labeling is used. The intention of the CrochetPARADE language has always been to use labels to mark groups of stitches that are single runs of adjacent stitches (not necessary sequentially worked, but still attached to each other). Morever, accidental attachment to stitches that have not been worked yet should not be allowed. The code until now was making some checks for those conditions but those are not robust. Now, the parser is much stricter and emits errors when non-adjacent stitches are labeled with one and the same label, or when one tries to crochet into the "future" (in stitches that are still to be worked).

* Improved and expanded Manual.

.png

Screenshot From 2025-12-21 20-00-33.png (Size: 709.92 KB / Downloads: 1) ]]>
I made a major update to CrochetPARADE. It includes a couple of expansions to the language (see below) as well as a new tool: Find project periphery (in the Tools menu). The Periphery finder is all about making edge work (borders, edgings, joining, finishing rounds, attaching motifs, picking up stitches along a side, etc.) much less fiddly in CrochetPARADE.

In crochet, the periphery or border is where so many practical and decorative things happen. It’s where you add a clean border, where you join panels such as granny squares, where you pick up stitches along the side of rows, and where you often “finish” a shape. If you’ve ever added a border to a blanket or motif, you know the edge/finish step is basically its own mini-project. And even in plain “add a border” scenarios, picking up stitches evenly along an edge is one of those deceptively tricky steps that can make things ruffle or warp if you just “pick up everything.”

But if you’re not crocheting in the round, say you’re working rows with turns, attaching motifs (Irish crochet!), or anything where the boundary is built from ends of rows + possibly side posts + turning chains + joins, then the stitches that are consecutive along the boundary are often not consecutive in the order you crocheted them. That’s exactly what makes “crochet around the edge” annoying in a text-driven workflow: you need to find boundary stitches one-by-one, and if you want to label them sequentially (for example with something like A[k++]) it quickly turns into a “where am I on the edge?” scavenger hunt.

So this update is about giving CrochetPARADE a real periphery workflow: find it, visualize it, edit it when needed, and then label it in a way that makes it easy to work stitches in the periphery, and in a way that stays stable even as you keep editing/refactoring the project. (Which is the whole point of CrochetPARADE’s “precise text → 3D model workflow.)

1. Find project periphery

This adds a new workflow under **Tools → Find Project Periphery**.

Think of it as: **“show me the stitches that are on the outside edge of this piece, in the order I’d actually work them if I were crocheting along the edge.”**

That “in the order I’d actually work them” part is the key. In anything made with rows + turns (or motifs that get attached), the stitches that touch each other along the outside edge are often *not* next to each other in your written instructions. CrochetPARADE now finds the *edge stitches* for you and gives you an edge-walk order you can use for borders, joining, and finishing.

What you’ll see:

* One (or sometimes a few) **possible peripheries**. Pick one and CrochetPARADE highlights it on the 3D model so you can sanity-check it quickly.
* If your pattern text is expanded down to individual stitches, it can also **highlight those exact stitches in the editor** (so you can edit or label them precisely).

A typical “crocheter workflow” looks like:

* Build / calculate your project as usual.
* Run **Tools → Find Project Periphery**, pick the periphery that looks right, and check the highlight.
* If you want the periphery stitches highlighted in the text as well: run **Tools → Expand instructions** (select the option to “run twice”).
* Use the tool’s **Apply label to periphery stitches** section to stamp labels *around the edge in edge order*.

* You can label them with a simple label (like `Edge`, which can be sorted in periphery-adjacent order using SORT_LABEL, see below) or a numbered label (like `Edge[k++]` or `Edge[k]; the latter could be indexed with an INDEX_ARRAY, see below).
* There’s an option to reverse the order, which is handy depending on whether you want to go clockwise/counterclockwise around the piece.

And when the automatic periphery is *almost right* but you want to tweak it (lace holes, very openwork edges, multi-piece joins, “I only want this outer side”, etc.) there’s a **Custom Periphery editor**:

* You can define the periphery as a list of **pairs of stitches that are neighbors on the edge**, one per line, like:
`stitch1 -- stitch2`
* CrochetPARADE will then treat that as a custom periphery and will try to walk it in order.
* With the editor open, you can **Alt+Click edges on the 3D model** to add them to the list, which is a nice “pick it off the model” way to fine-tune the boundary.

2. Update to the CrochetPARADE language: New labeling with INDEX_ARRAY and SORT_LABEL

This update is about one practical thing: labeling a set of stitches in a specific order without turning your whole pattern into a soup of stitches with labels such as sc.Edge[3] with numbers that are not sequential in the order they were worked in (but are sequential in some other sense, in periphery order for example).

So: CrochetPARADE now supports two ways to keep labels *ordered* in a way other than the order in which the labeled stitches were worked.

### A) INDEX_ARRAY

`INDEX_ARRAY:` lets you keep your stitch labels looking clean (like `Edge[k]`) while storing the actual list of numbers k *somewhere else*.

So let's say you want to mark the edge of the pattern in the example below:

6ch,turn
[sk,ch,5sc,turn
]*4

which is a simple single crochet swatch. The periphery is the first and last row as well as the edge pieces. Taking account of the turns, if one wants to label the stitches in sequential order around the periphery, one had to do it by hand before. Now with the periphery tool, one can Expand Instructions; Find project periphery and label stitches with Edge[k++] (or label of your choice) to get the following ugly mess:

[[[ch].Edge[9]],[[ch].Edge[10]],[[ch].Edge[11]],[[ch].Edge[12]],[[ch].Edge[13]],[[ch].Edge[14]]],turn
[sk,[[ch].Edge[15]],[sc,sc,sc,sc,[[sc].Edge[8]]],turn
],[sk,[[ch].Edge[7]],[sc,sc,sc,sc,[[sc].Edge[16]]],turn
],[sk,[[ch].Edge[17]],[sc,sc,sc,sc,[[sc].Edge[6]]],turn
],[sk,[[ch].Edge[5]],[[[sc].Edge[4]],[[sc].Edge[3]],[[sc].Edge[2]],[[sc].Edge[1]],[[sc].Edge[0]]],turn
]

with Edge[k] going sequentially from 0 to 17 around the periphery (taking account of the turn's). The indexed labels have their indices baked in. So, if you wanted to do Tools->Simplify instructions, the simplification will stumble because of the non-sequential indices (non-sequential in crochet order). Even after selecting: "Attempt to simplify numerical indexing..." in the Simplify Instructions dialog, we get (after replacing the automatically generated index "vara" with "k" for brevity):

[ch].Edge[$k=9$k],5*[[ch].Edge[++k]],turn
sk,[ch].Edge[++k],4sc,[sc].Edge[$k=8$k],turn
sk,[ch].Edge[--k],4sc,[sc].Edge[$k=16$k],turn
sk,[ch].Edge[++k],4sc,[sc].Edge[$k=6$k],turn
sk,[ch].Edge[--k],5*[[sc].Edge[--k]],turn

With an INDEX_ARRAY, the above simplifies to (and yes, many of the square bracket can be deleted; this is what the code returns automatically):

INDEX_ARRAY:k={9,10,11,12,13,14,15,8,7,16,17,6,5,4,3,2,1,0}
6*[[ch].Edge[k]],3*[turn
sk,[ch].Edge[k],4sc,[sc].Edge[k]],turn
sk,[ch].Edge[k],5*[[sc].Edge[k]],turn

And in this case pattern simplifiction works much better as it sees the same label Edge[k] and the non-sequential indices are saved in the INDEX_ARRAY field.

And yes: the periphery tool generates this for you automatically when you label the periphery with something like `Edge[k]`. The steps are: Expand Instructions; Find project periphery and label stitches with Edge[k] (or label of your choice); Simplify Instructions.

### B) SORT_LABEL

Sometimes you don’t want indexed labels at all. You just want:

* “these stitches are the edge stitches,” labeled `Edge`,
* but you still want CrochetPARADE to remember the *order around the edge* (so later steps that say “work around Edge” by typing say 18*sc@Edge)

That’s what `SORT_LABEL:` is for.

It keeps the stitch text simple (for example using a label `.Edge`), while storing the “walk around the edge” order in a SORT_LABEL. For the example above, it takes the form:

SORT_LABEL:Edge={17,16,15,14,13,12,11,8,7,0,1,2,3,4,5,6,9,10}
6*[[ch].Edge],3*[turn
sk,[ch].Edge,4sc,[sc].Edge],turn
sk,[ch].Edge,5*[[sc].Edge],turn

And again: the periphery tool generates this automatically when you apply a non-numbered label to the periphery. The steps are: Expand Instructions; Find project periphery and label stitches with Edge (or label of your choice); Simplify Instructions.

If you want to mark different parts of the edge with different labels, use the Edit edges button in the periphery tool to delete edges that are not part of say the bottom/right/left/top edge. Each time you edit it, you an save it as a Custom periphery. Then you an apply separate labels to each part of the periphery. Here is an example of a swatch with Top and Bottom edges labeled, and separated edgings worked into them in different colors (once rendered, click on the 3d canvas, and press 'c' to see the colors):

COLOR:Yellow
6*[ch.Bottom],3*[turn
sk,ch,5sc],turn
sk,[ch].Top,5*[sc.Top],turn
SORT_LABEL:Top={0,1,2,3,4,5}
SORT_LABEL:Bottom={0,1,2,3,4,5}
COLOR:Blue
[start_at,ch,5sc]@Top
COLOR:Red
[start_at,ch,5sc]@Bottom

---

# Additionally (just mentioning these):

* The undo Ctrl+Z / Cmd+Z (and the redo Ctrl+Shift+Z or Ctrl+Y) is now a much better history tracker while editing patterns.

* The stitch highlighting mechanism (in the editor and the 3D canvas) is more robust and the different types of highlights have different colors.

* Improved error reporting.

* Produce errors when unsupported stitch labeling is used. The intention of the CrochetPARADE language has always been to use labels to mark groups of stitches that are single runs of adjacent stitches (not necessary sequentially worked, but still attached to each other). Morever, accidental attachment to stitches that have not been worked yet should not be allowed. The code until now was making some checks for those conditions but those are not robust. Now, the parser is much stricter and emits errors when non-adjacent stitches are labeled with one and the same label, or when one tries to crochet into the "future" (in stitches that are still to be worked).

* Improved and expanded Manual.

.png

Screenshot From 2025-12-21 20-00-33.png (Size: 709.92 KB / Downloads: 1) ]]> <![CDATA[Attaching limbs to body]]> https://crochetparade.org/crochetforum/showthread.php?tid=56 Sun, 14 Dec 2025 05:37:43 +0000 CyborgDucky]]> https://crochetparade.org/crochetforum/showthread.php?tid=56
.png

Screenshot 2025-12-13 213350.png (Size: 342.26 KB / Downloads: 2)
I'm trying to make a dinosaur, but I cant figure out how to make it so the tail connects properly to the body.
I've looked at the manual but I think i just don't understand something because it comes out all screwy.
DEF:inc=Copy(sc2inc)
DEF:dec=Copy(sc2tog)
ring.A
6sc@A
6inc
6(sc, inc)
6(2sc, inc)
24sc
24sc
24sc
24sc
6sc, 6dec, 6sc
6sc, 3dec, 6sc
15sc
6sc, 3inc, 6sc
18sc
6sc, 6inc, 6sc
9sc, dc5bobble, 5sc, dc5bobble, 8sc
24sc
6(3sc, inc)
30sc
30sc
6(3sc, dec)
6(2sc, dec)
6(sc, dec)
6dec

start_anew
ring.B
6sc@B
6sc
6inc
sc@[21,1],sc@[21,0],sc@[19,28],sc@[18,28],sc@[17,28],sc@[16,23],sc@[17,0],sc@[17,1],sc@[18,2],sc@[19,2],sc@[20,2],sc@[21,1]]]> <![CDATA[pattern folds in on itself in a previous row, when adding a new one]]> https://crochetparade.org/crochetforum/showthread.php?tid=55 Fri, 28 Nov 2025 10:33:59 +0000 Lukina]]> https://crochetparade.org/crochetforum/showthread.php?tid=55
I just found this amazing tool and wanted to use it to help me get color changes at the right places. I put the pattern in row for row and everything worked great until I added the 19th row. Suddenly the 8th row, that was previously fine, folded in on itself. I finished the pattern anyway and no, every time I deactivate the rows after the 18th it looks good, but as soon as they are included it is folded in on itself at the 8th row. I attached two pictures for reference.One where the 19th row and onward are not active (
.png

19th-and-on-active.PNG (Size: 242.57 KB / Downloads: 3) ) and one where the 19th row and onward are active (
.png

19th-and-on-not-active.PNG (Size: 229.14 KB / Downloads: 2) ).]]>
I just found this amazing tool and wanted to use it to help me get color changes at the right places. I put the pattern in row for row and everything worked great until I added the 19th row. Suddenly the 8th row, that was previously fine, folded in on itself. I finished the pattern anyway and no, every time I deactivate the rows after the 18th it looks good, but as soon as they are included it is folded in on itself at the 8th row. I attached two pictures for reference.One where the 19th row and onward are not active (
.png

19th-and-on-active.PNG (Size: 242.57 KB / Downloads: 3) ) and one where the 19th row and onward are active (
.png

19th-and-on-not-active.PNG (Size: 229.14 KB / Downloads: 2) ).]]> <![CDATA[Amigururi with AI]]> https://crochetparade.org/crochetforum/showthread.php?tid=54 Sun, 16 Nov 2025 20:42:55 +0000 beucherm]]> https://crochetparade.org/crochetforum/showthread.php?tid=54 Do you think it is possible to general Amigururi tuto with AI ?

I would like to create several new model.]]> Do you think it is possible to general Amigururi tuto with AI ?

I would like to create several new model.]]> <![CDATA[Amigurumi pattern inverts/turns inside out after 26 rows.]]> https://crochetparade.org/crochetforum/showthread.php?tid=53 Sat, 01 Nov 2025 23:25:50 +0000 Copper]]> https://crochetparade.org/crochetforum/showthread.php?tid=53 I tried just using ctrl+enter to calculate the added row, but it comes out really wonky, same as ctrl+r.

I need help!
I provided 2 screenshots of the pattern, one with 2 rows, the other with 27. I couldn't seem to get them oriented the same way, but I hope it's useful enough.
Any advice is useful, thanks.

.png

Screenshot 2025-11-01 191714.png (Size: 882.79 KB / Downloads: 1)

.png

Screenshot 2025-11-01 191603.png (Size: 759.88 KB / Downloads: 1) ]]> I tried just using ctrl+enter to calculate the added row, but it comes out really wonky, same as ctrl+r.

I need help!
I provided 2 screenshots of the pattern, one with 2 rows, the other with 27. I couldn't seem to get them oriented the same way, but I hope it's useful enough.
Any advice is useful, thanks.

.png

Screenshot 2025-11-01 191714.png (Size: 882.79 KB / Downloads: 1)

.png

Screenshot 2025-11-01 191603.png (Size: 759.88 KB / Downloads: 1) ]]> <![CDATA[Attachment points not working]]> https://crochetparade.org/crochetforum/showthread.php?tid=52 Mon, 13 Oct 2025 03:38:45 +0000 burgendorf]]> https://crochetparade.org/crochetforum/showthread.php?tid=52 this pattern to make it a gray fox. But when I get to round 19, which is all supposed to be scbl, the stitches just disappear and only the sc2tog shows up. I need to close the stuffed head at round 20 and then start round 21 again in the front loops of round 19. But it doesn't work. The best that'll happen is only one stitch will attach to that attachment point. I've tried scfl@[19,0], I've tried labeling the first scbl.F and then scfl@F, I've tried just using sc@[19,0] but the rest of the stitches for round 21 won't "stick" to round 19. It just kind of spirals, folds in on itself, and separates. I've tested my methods on the example Earth pattern and my methods should work.
Here's the code:

Code:
COLOR: gray,ring.R

(6sc)@R

6sc2inc # 12

6*(sc, sc2inc) # 18

6*(sc, sc2inc, sc) # 24

6*(3sc, sc2inc) # 30

6*(2sc, sc2inc, 2sc) # 36

6*(5sc, sc2inc) # 42

10sc, COLOR: red,3sc, COLOR: gray,16sc, COLOR: red,3sc, COLOR: gray,10sc # 42

10sc, COLOR: red,3sc, COLOR: gray,16sc, COLOR: red,3sc, COLOR: gray,10sc # 42

10sc, COLOR: red,3sc, COLOR: gray,16sc, COLOR: red,3sc, COLOR: gray,10sc # 42

10sc, COLOR: red,3sc, COLOR: gray,16sc, COLOR: red,3sc, COLOR: gray,10sc # 42

10sc, COLOR: red,3sc2inc, COLOR: gray,16sc, COLOR: red,3sc2inc, COLOR: gray,10sc #48

10sc, COLOR: red,2sc, 3sc2inc, sc, COLOR: gray,16sc, COLOR: red, 3sc2inc, 3sc, COLOR: gray,10sc #54

7sc, sc2tog, sc, COLOR: red,6sc, sc2tog, sc, COLOR: gray, 2*(6sc, sc2tog), COLOR: red,7sc, sc2tog, sc, COLOR: gray,6sc, sc2tog,sc #48

3sc, sc2tog, 3sc, COLOR: red,3sc, sc2tog, 4sc, COLOR: white,2sc, sc2tog, 6sc, sc2tog, 2sc, COLOR: red,3sc, sc2tog, 5sc, COLOR: gray,2sc, sc2tog, 3sc # 42

3sc, sc2tog, 3sc, COLOR: red,3sc2tog, COLOR: white,sc2tog, 10sc, sc2tog, COLOR: red,3sc2tog, sc, COLOR: gray,2sc, sc2tog, 3sc # 32 

6sc, COLOR: red,5sc, COLOR: white,10sc, COLOR: red,5sc, COLOR: gray,6sc # 32

2*(2sc, sc2tog), COLOR: red,2sc, sc2tog COLOR: white,2*(2sc, sc2tog), COLOR: red,2sc, sc2tog, COLOR: gray,2*(2sc, sc2tog) # 24

2*(scbl, sc2tog), COLOR: red,scbl, sc2tog, scbl, COLOR: white,sc2tog, scbl, sc2tog, COLOR: red,scbl, sc2tog, scbl, COLOR: gray,sc2tog, scbl, sc2tog # 16

2sc2tog, COLOR: red,sc2tog, COLOR: white,2sc2tog, COLOR: red, sc2tog, COLOR: gray,2sc2tog

scfl@[19,0], 5scfl, COLOR: red,3scfl, COLOR: white,7scfl, COLOR: red,3scfl, COLOR: gray,5scfl # 24

3*(sc, sc2inc), COLOR: red,2sc, COLOR: white,9sc, COLOR: red,2sc, COLOR: gray,sc2inc, 2*(sc, sc2inc) # 30

3*(2sc, sc2inc), sc, COLOR: red, 3sc, COLOR: white, 5sc, COLOR: red, 3sc, COLOR: gray,3*(2sc, sc2inc) # 36

14sc, COLOR: red, 3sc, COLOR: white, 3sc, COLOR: red, 3sc, COLOR: GRAY, 13sc # 36

15sc, COLOR: red, 7sc, COLOR: gray,14sc, # 36

15sc, COLOR: red, 7sc, COLOR: gray,14sc, # 36

14sc, COLOR: red,2sc, COLOR: white,5sc, COLOR: red,2sc, COLOR: gray, 13sc #36

2*(2sc, sc2tog, 2sc), sc, COLOR: red, sc, sc2tog, COLOR: white,4sc, sc2tog, COLOR: red,2sc, COLOR: gray, 2sc, sc2tog, 4sc, sc2tog, sc, COLOR: red,sc # 30

3sc, COLOR: gray,8sc, COLOR: red,2sc, COLOR: white,5sc, COLOR: red,2sc, COLOR: gray,9sc, COLOR: red,sc # 30 

3sc, COLOR: gray,sc2tog, 3sc, sc2tog, sc, COLOR: red,2sc, COLOR: white,sc, sc2tog, 2sc, COLOR: red,sc2tog, COLOR: gray,3sc, sc2tog, 3sc, COLOR: red,sc2tog  # 24

COLOR: red,2*(sc, sc2tog, sc), sc, sc2tog, COLOR: white, 2sc, sc2tog, COLOR:red, sc, 2*(sc, sc2tog, sc) # 18

COLOR: white,6*(sc, sc2tog) # 12

What am I doing wrong? I tried the DOT: start=integer trick and that made it worse. I just want to start a new round from round 19 to continue the pattern. Each subsequent stitch should be attached to the next stitch on round 19. And I get the same results whether I make round 21 all scfl or just sc. I've been tearing my hair out for days on this!]]> this pattern to make it a gray fox. But when I get to round 19, which is all supposed to be scbl, the stitches just disappear and only the sc2tog shows up. I need to close the stuffed head at round 20 and then start round 21 again in the front loops of round 19. But it doesn't work. The best that'll happen is only one stitch will attach to that attachment point. I've tried scfl@[19,0], I've tried labeling the first scbl.F and then scfl@F, I've tried just using sc@[19,0] but the rest of the stitches for round 21 won't "stick" to round 19. It just kind of spirals, folds in on itself, and separates. I've tested my methods on the example Earth pattern and my methods should work.
Here's the code:

Code:
COLOR: gray,ring.R

(6sc)@R

6sc2inc # 12

6*(sc, sc2inc) # 18

6*(sc, sc2inc, sc) # 24

6*(3sc, sc2inc) # 30

6*(2sc, sc2inc, 2sc) # 36

6*(5sc, sc2inc) # 42

10sc, COLOR: red,3sc, COLOR: gray,16sc, COLOR: red,3sc, COLOR: gray,10sc # 42

10sc, COLOR: red,3sc, COLOR: gray,16sc, COLOR: red,3sc, COLOR: gray,10sc # 42

10sc, COLOR: red,3sc, COLOR: gray,16sc, COLOR: red,3sc, COLOR: gray,10sc # 42

10sc, COLOR: red,3sc, COLOR: gray,16sc, COLOR: red,3sc, COLOR: gray,10sc # 42

10sc, COLOR: red,3sc2inc, COLOR: gray,16sc, COLOR: red,3sc2inc, COLOR: gray,10sc #48

10sc, COLOR: red,2sc, 3sc2inc, sc, COLOR: gray,16sc, COLOR: red, 3sc2inc, 3sc, COLOR: gray,10sc #54

7sc, sc2tog, sc, COLOR: red,6sc, sc2tog, sc, COLOR: gray, 2*(6sc, sc2tog), COLOR: red,7sc, sc2tog, sc, COLOR: gray,6sc, sc2tog,sc #48

3sc, sc2tog, 3sc, COLOR: red,3sc, sc2tog, 4sc, COLOR: white,2sc, sc2tog, 6sc, sc2tog, 2sc, COLOR: red,3sc, sc2tog, 5sc, COLOR: gray,2sc, sc2tog, 3sc # 42

3sc, sc2tog, 3sc, COLOR: red,3sc2tog, COLOR: white,sc2tog, 10sc, sc2tog, COLOR: red,3sc2tog, sc, COLOR: gray,2sc, sc2tog, 3sc # 32 

6sc, COLOR: red,5sc, COLOR: white,10sc, COLOR: red,5sc, COLOR: gray,6sc # 32

2*(2sc, sc2tog), COLOR: red,2sc, sc2tog COLOR: white,2*(2sc, sc2tog), COLOR: red,2sc, sc2tog, COLOR: gray,2*(2sc, sc2tog) # 24

2*(scbl, sc2tog), COLOR: red,scbl, sc2tog, scbl, COLOR: white,sc2tog, scbl, sc2tog, COLOR: red,scbl, sc2tog, scbl, COLOR: gray,sc2tog, scbl, sc2tog # 16

2sc2tog, COLOR: red,sc2tog, COLOR: white,2sc2tog, COLOR: red, sc2tog, COLOR: gray,2sc2tog

scfl@[19,0], 5scfl, COLOR: red,3scfl, COLOR: white,7scfl, COLOR: red,3scfl, COLOR: gray,5scfl # 24

3*(sc, sc2inc), COLOR: red,2sc, COLOR: white,9sc, COLOR: red,2sc, COLOR: gray,sc2inc, 2*(sc, sc2inc) # 30

3*(2sc, sc2inc), sc, COLOR: red, 3sc, COLOR: white, 5sc, COLOR: red, 3sc, COLOR: gray,3*(2sc, sc2inc) # 36

14sc, COLOR: red, 3sc, COLOR: white, 3sc, COLOR: red, 3sc, COLOR: GRAY, 13sc # 36

15sc, COLOR: red, 7sc, COLOR: gray,14sc, # 36

15sc, COLOR: red, 7sc, COLOR: gray,14sc, # 36

14sc, COLOR: red,2sc, COLOR: white,5sc, COLOR: red,2sc, COLOR: gray, 13sc #36

2*(2sc, sc2tog, 2sc), sc, COLOR: red, sc, sc2tog, COLOR: white,4sc, sc2tog, COLOR: red,2sc, COLOR: gray, 2sc, sc2tog, 4sc, sc2tog, sc, COLOR: red,sc # 30

3sc, COLOR: gray,8sc, COLOR: red,2sc, COLOR: white,5sc, COLOR: red,2sc, COLOR: gray,9sc, COLOR: red,sc # 30 

3sc, COLOR: gray,sc2tog, 3sc, sc2tog, sc, COLOR: red,2sc, COLOR: white,sc, sc2tog, 2sc, COLOR: red,sc2tog, COLOR: gray,3sc, sc2tog, 3sc, COLOR: red,sc2tog  # 24

COLOR: red,2*(sc, sc2tog, sc), sc, sc2tog, COLOR: white, 2sc, sc2tog, COLOR:red, sc, 2*(sc, sc2tog, sc) # 18

COLOR: white,6*(sc, sc2tog) # 12

Code:
ring

sc8inc

[8sc

]*17

sc,2sc2inc,5sc

2sc,2sc2inc,6sc

New Picture (11).jpg (Size: 138.07 KB / Downloads: 1)
.jpg

New Picture (12).jpg (Size: 137.44 KB / Downloads: 1) ]]>

Code:
ring

sc8inc

[8sc

]*17

sc,2sc2inc,5sc

2sc,2sc2inc,6sc

New Picture (11).jpg (Size: 138.07 KB / Downloads: 1)
.jpg

New Picture (12).jpg (Size: 137.44 KB / Downloads: 1) ]]> <![CDATA[Foundation chain]]> https://crochetparade.org/crochetforum/showthread.php?tid=48 Mon, 08 Sep 2025 22:07:56 +0000 miocene]]> https://crochetparade.org/crochetforum/showthread.php?tid=48 <![CDATA[Magic Circle question]]> https://crochetparade.org/crochetforum/showthread.php?tid=46 Sun, 17 Aug 2025 17:06:01 +0000 aurquid2]]> https://crochetparade.org/crochetforum/showthread.php?tid=46
I am trying to customize the magic circle from the default. Is the default 5 stitches because I want to add 8? Please let me know if there is a way.

Thank you!]]>
I am trying to customize the magic circle from the default. Is the default 5 stitches because I want to add 8? Please let me know if there is a way.

Thank you!]]>