Awesome, but I'd prefer if it looked same as the dialogue boxes triggered by the use of ‘cloud saves’ and this:

However, it sould have that text you put, perhaps with a slightly more muted red as to bring attention yet not hurt people's eyes.
Oops, by this I meant an automatic message, didn't quite read the original message!

PrincessPanda_test_ wrote:

I believe just putting an epilepsy warning in the notes and credits would do the same.

Alotta people (for some reason) dont read the notes & credits

PrincessPanda_test_ wrote:

(#14)
I believe just putting an epilepsy warning in the notes and credits would do the same.

But not everyone reads them. A big banner would mean more readers.

May I also suggest we have some for more things that may trigger others such as,

• shake
  
• blood/gore
  
• bright colors
  
• triggering lyrics
  
• mention of…
  

etc.

Also before you, “Read the community guidelines” me, please remember that things allowed by Scratch can easily still trigger some users.

/g

Hmm…I just can’t agree with this. At least, not in its current state. And to make my point, I’m going to go ahead and explain, in much detail, what would happen if this were to be implemented. It’s time to make an essay.

EPILEPSY WARNINGS IN PROJECTS
DAY 1
After seeing @kittycat641’s forum suggestion about adding epilepsy warnings in projects, the Scratch Team decided to add an epilepsy warning similar to the username warning. If a project fit the criteria for the epilepsy warning and the creator of the project wanted to set the warning, they could do that. Today was a great day for users with ocular disorders…at least, partially.

However, old projects with inactive owners such as this will not have the warning. Although the Scratch Team can technically choose to add the warning, it is inconsistent with the fact that it’s an option, and the Scratch Team reasoned that if it was no longer an option, then they had to make it automatic, which would have a lot of false positives. But this was a rather minor flaw, and there were still more pros than cons, so they kept this flaw silent and moved on.

They did the same when New Scratchers were confused, thinking it might have been against the rules to add lights to projects. To clear up the confusion, the Scratch Team makes an announcement explaining in detail how the warnings work. Of course, this announcement will receive much spam, and it’ll bring attention to flashing light projects. Many users will make extremely bright projects just to test out the warning. But this is inevitable if you’re making an announcement, ST ignores it for now.

DAY 8
Around this date, many users will have changed their epilepsy-inducing projects to include the warning. This really benefits the small amounts of epileptic users (or honestly just people who don’t like to see flashing lights.) Those users will be very content with the way flashing lights are warned. Scratch is a bit happier, except for the entirety of QaS. It seems as though every time an update comes out, users complain that this suggestion was implemented, while another suggestion (such as dark mode) wasn’t. The same thing will occur here, as well as other users who simply disagree with the changes.

However, forum helpers will just explain that the Scratch Team has priorities, and that was on their list. “Every implemented feature has things that people won’t like,” the Scratch Team will reason, which, of course, is correct.

DAY 18
This will be around the date that users will begin to realize that the epilepsy warning will cause less users to view the project, and excluding the epilepsy warning will not get your project taken down. Most users will not use the warning, and there’s nothing the Scratch Team can do about it since it does not break the CGs. If most users don’t include the warning, a lot of users will experience bright lights that are bothersome, and there will be much complaining.

Therefore, they have just added a feature that no one uses, effectively causing mass complaining, a new addition to Scratch that is somewhat confusing to many Scratchers (making them think it’s against the rules to add flashing lights), causing many seizure-inducing projects to be created (albeit it’s technically ok for Scratch), and wasting lots of money for the developers to invest time in this.

————

I think it would just be best, as aforementioned, to just add a warning in the Notes and Credits. Just keep the system that already works. That’s my take on this. What are your thoughts?

No support, people tend to ignore warnings in projects and as SSB20 stated, you can just write it in the Notes & Credits or in the title.

elephanttime wrote:

LionHeart70 wrote:

FancyFoxy wrote:

But how can the system detect if a project has stuff that can cause epilepsy?

If you didn't read the entire OP, it'd be a checkbox thing.

Maybe if the program checks if the project contains

OR you could report it and say it may cause a seizure. Then, Scratch says they will review it
Support This!

“Add an epilepsy warning to EVERY project with a colour effect”? What about the text engine I'm working on which doesn't allow you to change the colour of already written text already so repeatedly writing with a colour effect change only fills up and clears the screen anyway? Or a simple fading-colour background?

seizure warnings might pop up if it has a bad seizure, like this!

So you have 6 backdrops, 1 is red, 2 is orange, 3 is yellow, 4 is green, 5 is blue, and 6 is purple.

Heavy support. Although IIRC Zydrolic already has a similar system to this in their projects, where you need to click the green flag 3 times for the project to play, this would be a really neat addition for Scratch in general.

I requested this to be merged with this topic. Hopefully it doesn't make a cursed topic this time.

k7e wrote:

I requested this to be merged with this topic. Hopefully it doesn't make a cursed topic this time.

No, they're two different topics. That one is about having a report option for non-disclosed flashing lights, while this one is about easily disclosing flashing lights.

Support, this would allow me to express my creativity

blablablahello wrote:

Alotta people (for some reason) dont read the notes & credits

maybe in the project then?

kittycat841 wrote:

So, if you look around here on Scratch, you might find some scratch projects with a sprite with this script:

It might not have an epilepsy warning. If someone with epilepsy saw one of those projects, and it didn't have an epilepsy warning, someone could have a seizure.

That's why I'm proposing this idea for an epilepsy warning.
If your project contains flashing lights or fast-moving images, you can check this box that says:

My project contains flashing lights and/or fast moving images

There. Simple, and effective. If the Scratcher checked the box, a message similar to the username block warning but in red would say:

Epilepsy Warning: This project contains fast moving pictures and/or fast moving images

This is effective because some scratchers don't look at the notes and credits or instructions and it might look unprofessional if you have “EPILEPSY WARNING” in your title. Red is a bright and warning color, so people would notice it if they are sensitive to flashing lights or fast moving images.

Thoughts?

Maybe they could have an AI/block that would detect it like: