Project: https://scratch.mit.edu/projects/970620181/
–
Layout | Layout Conditions | Project Conditons | Q&A
Hello!
Welcome to the Hen Farm's Find Bugs and Report Them Here station!
Here's how it works.

1. Get into the project (linked above) and check for bugs in the gameplay.
2. If you find a bug:
Check the project code and move to Step 3.
If not:
Keep playing and go to Step 5.
3 (Found a bug). If you find the bug in the code, remix the project and fix the bug.
4. Report this bug by replying to this post in the layout below. Do not do Step 5 and beyond.
5 (No bug found). Once you've finished checking all areas of the game, check the code.
6. If you still haven't found a flaw, report that no bug has been found by replying to this post with the below layout.
Thank you! Please read the below posts!

That’s not exactly what this forum is for. This forum is for if you need help with a specific problem or script, not if you want people to find bugs for you. Try making a topic in the Show and Tell section to tell people about your project, and ask them to report any bugs they find there.

Layout
This is the layout of your report.

Bug Found? Yes or No
Description: Explain your bug… or don't if you don't have one!
Where the flaw is in the code: Where is the flaw? Skip this if there's no bug.
How you fixed it: The name explains itself. Also skip this if there's no bug.
Link to the fixed project: Link the project that you remixed. Don't remix if there's no bug.

Good Examples

Bug Found? Yes
Description: The ducks are not moving, whatever I do, it won't go
Where the flaw is in the code: In the tick loop, it doesn't broadcast the message that moves the duck
How you fixed it: I added the broacast message to the loop
Link to the fixed project: https://scratch.mit.edu/projects/996744226/

Bug Found? No
Description: Everything is fine; I checked everywhere and it was all okay

Bad Examples

Bug Found? ye
Description: duk wont move
Where the flaw is in the code: i don now
How you fixed it: do i relly hav 2 explane
Link to the fixed project: (The same project with the flaw)

Bug Found? nup
Description: dere wes no bug

Pixilized wrote:

That’s not exactly what this forum is for. This forum is for if you need help with a specific problem or script, not if you want people to find bugs for you. Try making a topic in the Show and Tell section to tell people about your project, and ask them to report any bugs they find there.

Okay. I'll finish up with the setup of this topic, then I'll move it there.

Layout Conditions
Remember those examples! Now, the good examples are following these conditions:

1. Don't be lazy and don't make mistakes.
2. Detail the description, the flaw in the code and how you fixed it.
3. Explain everything.

There may be three, but you will need to follow them!

Project Conditions
What would your remix have?

1. The fix, obviously
2. Comments highlighting which blocks were added, changed or removed
3. Comments highlighting how these blocks affect and fix the bug (don't just say a very simple sentence like “it fixes it” or “the ducks move now” or even “its magic” or even, even “it connects the moving message”, say something like “Before there wasn't any message that moves the ducks, this added message contains code that moves the ducks.”, etc.
4. The instructions part saying where this code is (which sprite? if its a backdrop just say that)

Q&A

Can I report multiple bugs in one post?
Of course yes, obviously! You can do it in any way you like.
Why shouldn't I break the conditions?
Breaking the conditions make your report and remix unclear and hard to navigate. Clearness helps!
Why do I need to highlight where my code is?
Users may remix, but remember; they're fixing the flaws they found. They may not have the patch you have, and I will have to add each patch one by one. Highlighting where your code is with comments help find the blocks for the patch and won't stress me!

If you still have a question that's not here, ask me and I'll add it here…