As the title says, I'd like to know what are the consequences of setting carts as forks.

Here's an example... I submitted STAR SPLORE last month. This week, I got a reply asking for some changes. I wanted to accommodate the request without changing the main cart, so I submitted an alternative version of the cart.

I didn't want to start a new thread for this alternative cart, though. So I just embedded it in a reply on the original thread. I guess that's why the cart doesn't show up in "New Carts", nor does it appear in my profile under "Cartridges".

And that's fine! It's an alternativo cart, I don't want anyone to find it before the main one...

But I noticed that, when I click "Edit" on a cart, there is a "Forks" section. I know what a fork is in GitHub, but what does it mean here?

Should I set this alternative cart as a fork of the original STAR SPLORE? What are the consequences of doing that in the BBS?

idk

Ok, so I did it... For science.

Now, when I edit the original cartridge, I can see the fork.

Didn't notice any other changes.

Something I noticed is that, while my alternative cart doesn't show on "New Carts" if you just navigate page by page, it DOES show up if you search for it.

This was already true before I configured it as a fork, though. I believe that's just what happens when your cart doesn't have a thread of its own, and is only embedded in a reply to another cart's thread.

Anyway, is that all there is to a fork? Maybe @zep can answer - or someone else who knows how the BBS works a little better...