banana439monkey

This is a newer, cleaned up version of this topic. Please do not report glitches with Scratch in this topic. Your post will be removed. Instead, make a new topic. Also, keep to the topic of the forum. This includes suggestions, questions and problems with scripts. Problems with scripts should be moved to the help with scripts forum. Anything offtopic will be reported to be moved.

We've found glitches somewhere in Scratch, right?
Right?

The point is, you should have. The first thing you want to do is make a new topic. Alternatively, you can hit the blue button in the corner of the Bugs and Glitches (BaG) forum that says new topic.

For a subject, summarise your glitch in a few words. In my example, I'm going to use “Character limit stays red if limit hit after comment posted”. Yes it's jank. Yes it's being fixed, but hey. Why not?

In the main topic, you want to include the following things:
A bug description
When it started
Where it is
Reproduction steps
Expected result
Actual result
Operating system, browser and Flash version (should be already there. if not, click the globe icon in the tools bar above the topic itself)
Screenshot (even better if you record a GIF. I recommend using ScreenToGif)

Trying to be as descriptive as possible will help a lot.

Animated tutorial (middle click to enlarge):


So what if there's a topic to reply to?
Glad you asked. Preferably, there are these codes you should follow. They're the way to reply to a bug.
NAB - Not a bug - Used if the topic is not on the topic of the forum or if the “bug” is intended.
Dupe - Duplicate - There's another topic. Preferably link to it.
Known - Does what it says on the tin - This is different to Dupe. This means the Scratch team knows (with reference) about the bug.
CNR - Cannot reproduce - Include your system specifications.
CR - Can reproduce - Include your system specifications.
LOI - Lack of information - Asks the person to provide more information about the bug. Tell them what is missing and to include it.
Please include as much information as possible. The more information you provide, the more helpful it is to everyone.

Since this topic is far from perfect, reply to this if you have a suggestion, need help or have a question.

Banana

Paddle2See

Nice! I might add, that if you find a recent (no more than a day or two old) existing topic describing the same problem, there is no need to make a new topic. Just add a post to the existing topic.

Thanks for making this

banana439monkey

Paddle2See wrote:

Nice! I might add, that if you find a recent (no more than a day or two old) existing topic describing the same problem, there is no need to make a new topic. Just add a post to the existing topic.

Thanks for making this
Yeah, I made a new one for archival purposes.

Banana

BabyCowOfLove

oh

Awesomedude2001

i hate scratch 2.0 editor bug fixes, they say they fixed it, but yet it acts up.

banana439monkey

Awesomedude2001 wrote:

i hate scratch 2.0 editor bug fixes, they say they fixed it, but yet it acts up.
Then reopen the topic and tell them is is not fixed.

Banana

TheBurger82

banana439monkey wrote:

This is a newer, cleaned up version of this topic. Please do not report glitches with Scratch in this topic. Your post will be removed. Instead, make a new topic. Also, keep to the topic of the forum. This includes suggestions, questions and problems with scripts. Problems with scripts should be moved to the help with scripts forum. Anything offtopic will be reported to be moved.

We've found glitches somewhere in Scratch, right?
Right?

The point is, you should have. The first thing you want to do is make a new topic. Alternatively, you can hit the blue button in the corner of the Bugs and Glitches (BaG) forum that says new topic.

For a subject, summarise your glitch in a few words. In my example, I'm going to use “Character limit stays red if limit hit after comment posted”. Yes it's jank. Yes it's being fixed, but hey. Why not?

In the main topic, you want to include the following things:
A bug description
When it started
Where it is
Reproduction steps
Expected result
Actual result
Operating system, browser and Flash version (should be already there. if not, click the globe icon in the tools bar above the topic itself)
Screenshot (even better if you record a GIF. I recommend using ScreenToGif)

Trying to be as descriptive as possible will help a lot.

Animated tutorial (middle click to enlarge):


So what if there's a topic to reply to?
Glad you asked. Preferably, there are these codes you should follow. They're the way to reply to a bug.
NAB - Not a bug - Used if the topic is not on the topic of the forum or if the “bug” is intended.
Dupe - Duplicate - There's another topic. Preferably link to it.
Known - Does what it says on the tin - This is different to Dupe. This means the Scratch team knows (with reference) about the bug.
CNR - Cannot reproduce - Include your system specifications.
CR - Can reproduce - Include your system specifications.
LOI - Lack of information - Asks the person to provide more information about the bug. Tell them what is missing and to include it.
Please include as much information as possible. The more information you provide, the more helpful it is to everyone.

Since this topic is far from perfect, reply to this if you have a suggestion, need help or have a question.

Banana
How do I include a screenshot?

banana439monkey

TheBurger82 wrote:

-snip-
How do I include a screenshot?
Please don't quote the original post.

Anyway, use snipping tool to snip a portion of (or the whole) screen. Save it, then upload it to cubeupload. From there, use [img]link[/img] to send your image.

Banana

fluffyd419

Ha!

banana439monkey

fluffyd419 wrote:

Ha!
Hmm?

Banana

GeckoTwin11

banana439monkey wrote:

This is a newer, cleaned up version of this topic. Please do not report glitches with Scratch in this topic. Your post will be removed. Instead, make a new topic. Also, keep to the topic of the forum. This includes suggestions, questions and problems with scripts. Problems with scripts should be moved to the help with scripts forum. Anything offtopic will be reported to be moved.

We've found glitches somewhere in Scratch, right?
Right?

The point is, you should have. The first thing you want to do is make a new topic. Alternatively, you can hit the blue button in the corner of the Bugs and Glitches (BaG) forum that says new topic.

For a subject, summarise your glitch in a few words. In my example, I'm going to use “Character limit stays red if limit hit after comment posted”. Yes it's jank. Yes it's being fixed, but hey. Why not?

In the main topic, you want to include the following things:
A bug description
When it started
Where it is
Reproduction steps
Expected result
Actual result
Operating system, browser and Flash version (should be already there. if not, click the globe icon in the tools bar above the topic itself)
Screenshot (even better if you record a GIF. I recommend using ScreenToGif)

Trying to be as descriptive as possible will help a lot.

Animated tutorial (middle click to enlarge):


So what if there's a topic to reply to?
Glad you asked. Preferably, there are these codes you should follow. They're the way to reply to a bug.
NAB - Not a bug - Used if the topic is not on the topic of the forum or if the “bug” is intended.
Dupe - Duplicate - There's another topic. Preferably link to it.
Known - Does what it says on the tin - This is different to Dupe. This means the Scratch team knows (with reference) about the bug.
CNR - Cannot reproduce - Include your system specifications.
CR - Can reproduce - Include your system specifications.
LOI - Lack of information - Asks the person to provide more information about the bug. Tell them what is missing and to include it.
Please include as much information as possible. The more information you provide, the more helpful it is to everyone.

Since this topic is far from perfect, reply to this if you have a suggestion, need help or have a question.

Banana
no it doesn't!
it doesn't turn red and it doesn't work
.


ha ha ha

GeckoTwin11

banana439monkey wrote:

TheBurger82 wrote:

-snip-
How do I include a screenshot?
Please don't quote the original post.

Anyway, use snipping tool to snip a portion of (or the whole) screen. Save it, then upload it to cubeupload. From there, use [img]link[/img] to send your image.

Banana
What is the snipping tool?????

banana439monkey

GeckoTwin11 wrote:

banana439monkey wrote:

TheBurger82 wrote:

-snip-
How do I include a screenshot?
Please don't quote the original post.

Anyway, use snipping tool to snip a portion of (or the whole) screen. Save it, then upload it to cubeupload. From there, use [img]link[/img] to send your image.

Banana
What is the snipping tool?????
It's a feature built into Windows.

Banana

MrSquirrelDeDuck

When I reported a bug, using this guide, I made sure to give credit. Great guide! I never would have reported the bug as well as I did without this! Thanks!

banana439monkey

MrSquirrelDeDuck wrote:

When I reported a bug, using this guide, I made sure to give credit. Great guide! I never would have reported the bug as well as I did without this! Thanks!
No problem! <3

Banana