WOOOO MORE DRAMA!!!!!!! EMBRACE CHAOS!!!!! That's what I'd normally say. I don't like getting my hands messy in situations like these, but I feel obligated to this time. So... Yesterday, a bunch of managers (including myself) got purged from the SOSC studio, and as per usual, when something strange happens, the drama tends to follow it. There's blame being thrown around over who's responsible for it, so I'm going to create this project to clear some things up. The last thing we need is for people to attack one another over something like this. It all started back quite literally only 4 days ago, so that's how you know how rapidly this situation grew. @heyoheyoheyo346 announced in a project about re-establishing some rules and cracking down on inappropriate comments. They then announced that a manager purge would be happening to remove some of the less active managers who likely already moved on from Scratch, or don't pay as much attention to the SOSC anymore. Less than a day later, more info about the manager purge came to light in another project they made, requiring some of us to list some reasons why we should stay. At the same time, they released another project for "Manager Auditions" for other users looking to become manager. At first, it was extremely surprising and out-of-the-blue for me, and likely a lot of other managers, and I didn't really appreciate the lack of communication. However, heyo DID mention that they got permission to do this, and this was in the works for months. I did a bit more digging, and managers like @TackyMacaroni, @Craft1000, @Yellowsheep43, and myself didn't really ever catch wind of this. This was a collaboration between heyo and @InfinityNinja1, with @TheMagicEraser being aware of what was happening. I'll provide screenshots for evidence. @MegaGameAnimator, the owner of the SOSC studio, likely wasn't involved in this though. All this seems like a lot, but that's just the appetizer: Prepare for the main course. Less than 24 hours ago, a user by the name of @IntentCement went through and wiped out nearly all the managers and a slew of other creators in the SOSC studio. They then proceeded to post a string of cryptic projects, claiming they were sorry and advertising their camp/show (idk) and podcast. Oddly enough, they also added @sosc-drama-alert as a manager, almost as if it were intentional, knowing that some form of drama would come from this. It's either an interesting metaphor, or had something else to do with the whole thing. To be clear, I'm not pointing fingers, I just find this interesting. I've taken their screenshots and added them to this project for evidence. Here's the project they came from though: https://scratch.mit.edu/projects/961202489/ @RandomScratcher938 hit me up with a DM which is how I found out about this whole mess. I decided to try and ask around to figure out what actually happened. @IntentCement did indeed go rogue, and just wiped a bunch of people out. Judging by their projects and what not, their mind's not in a good place right now. Of course, no nuclear bomb will go off without its fallout. In the aftermath of the event, users started to get re-invited to the studio and some managers reclaimed their manager roles. However, this is where the blame game began. A lot of people started pointing fingers at heyo for this whole mess, saying that they "indirectly caused this whole mess." Even @MegaGameAnimator, who is the owner of the studio, decided to insert their two cents and make that suggestion. And that's pretty much the whole thing. Now, this situation isn't anyone's fault except for @IntentCement and what they ultimately did. No one could've predicted it coming. However, I don't think heyo OR Mega are 100% innocent either. For heyo, while you didn't cause this separate purge, the lack of communication from the one you were organizing wasn't helpful at all. A lot of us were left in the dark on what was going on up until a few days ago, and then stalk what Intent did on top of that. If there was a bit more communication, things would've been smoother and not so sudden. As for Mega, it's awfully rich hearing a response like that from you as the server owner. To be fair, this did happen under your watch. Passing off the blame to someone else in a different situation isn't just disrespectful to the person on the receiving end, but it's also rather irresponsible. I know you aren't all that invested in the SOSC anymore, but you're sticking around so the community doesn't submerge when a problem like this arises, but this doesn't really help your case. Based off what you had said, you'd need to be more proactive than you're currently being as an Owner. Anyway, these are just my thoughts on the whole thing. I'm not trying to sway any opinions, I'm just trying to state the facts. If you're looking for the evidence I was able to uncover, it's inside the project in a sprite. Peace out. Pls follow :D
