The reason Co-Host were rejected is because of raids and confusion. Someone suggested 1-10 Co-host which is where raids and confusion mostly fall in. Really what you actually need to do is only one co-host per studio, and the host can set permissions for the co-host and restrict what they can and can't do. Restrictions like changing the thumbnail, name, desc, turning on and off comments, and removing people. Of course I can still see flaws in the rethought system. The one co-host can still raid when given the opportunity. This system could use some more thinking and I would love it if someone pitched ideas to help improve it too . So please if you actually want to help collab on this idea and add more to it, instead of saying “oh well scratch rejected it the idea can NEVER be came back to and rethought!!” it would be great! Lets try and get this system as perfect as we can so Scratch Team can add it to the site.

#staytrue

I support this, it would be really good if you needed a backup.