Hi there remember me? I have been applying for um… i forgot. Maybe 3-4 times in a row. And today im applying again.
P.S. comment on my profile if the application suceeds
thanks

1080GBA wrote:

Hi there remember me? I have been applying for um… i forgot. Maybe 3-4 times in a row. And today im applying again.

Read: https://scratch.mit.edu/discuss/post/7160292/

1080GBA wrote:

Hi there remember me? Im applying again.

Takeover qualifications:

Experience thinking outside the box.
Experience putting in continuous work.
Both of them the same project. I made it before this takeover application is available.
link: https://scratch.mit.edu/projects/717436975/
I got stuck when i had to code the UI and the main gravity scripts myself from scratch. But soon i figured it out.
I took a lot of breaks during this time, and i came back around every 2 weeks to continue coding.

Baseline experience with the Scratch programming language.
Above lol.

Experience writing longer informative content.
https://scratch.mit.edu/discuss/topic/586734/?page=8#post-6176747

Ideas for the guide!
I will be posting new workarounds that i find when coding projects here. also i will test out people's posts and they work i'll post it here.

P.S. sry im a bit too impatient and impolite b4 (0.5 -1 year ago)

@_nix, do you know how to make nested lists in the forums?

This requires an extra variable, though

When I'm adding a workaround, I try to think of the simplest way to do it—the one which requires the least previous understanding of other topics. So like, these are great ways to use loops to calculate how many costumes there are (or to make a list of costume names), but a Scratcher reading it does need to understand how to use loops for stuff besides animation for the workaround to make sense.

That doesn't mean I don't want to teach new concepts with workarounds—that's actually the main point of this thread! But, I'm careful to pick and choose which new ideas I want to focus on. In the Control section, for example, talking about loops (and unique ways of using them) is really natural, because the person who is reading is already learning about control structures and different kinds of loops. But complex ways of using loops don't fit the Looks section quite as well, because there, the reader is probably way more interested in animating their sprites with handy blocks than anything to do with customized control structures.

That's why in the Looks section Zaglo Text Generator, I try to place a focus on unique behaviour of Scratch looks blocks: I combine “switch to final costume” (switch costume to 0 + 0) with “costume number” because it's pretty intuitive when you think about it, and it shows a creative way to get more useful behavior from another workaround. I think it's an interesting solution to the problem which focuses on Looks behavior, teaching relevant new concepts and showing a different way of solving the problem than you might've thought of, hopefully helping spark new ideas and solutions to more involved problems later on

BTW, this is why a bunch of workarounds have more than one method, especially in the Control section where what you're doing is more abstract—if I can't decide between two approaches and they both show educational, focused ways to tackle the problem, I include ‘em both! So when the reader compares, they aren’t just choosing which one they like better…I'm also sneakily tricking them into noticing the differences and learning how they might choose between two solutions to their own unique coding challenges

https://fontsbunch.com/zalgo-text-generator/

I'm being 100% honest: This 100% deserved to be stickied. Much more explanatory than the previous owner! Almost 1 year later, congratulations!

Hi, I’d like to apply to take over this guide, and after reading through the takeover qualifications and just figuring out whether I myself have the time to maintain this, I decided that I wanted to apply, so I decided I’d tell you about my qualifications in the form of a story:

I was introduced to Scratch in 2019, and I liked the idea of coding, but it just never really held on to me, so I Just created this account and then left it to “collect dust” I guess. However, in 2020, when the COVID pandemic struck and I was stuck at home with not much to do, I somehow worked my way back onto Scratch. From there I decided I’s start developing my account, but really just put whatever idea sprung to my head into code with not much effort going into any of my projects (probably at most 2 weeks of coding). After a while of this, I thought I’d enter a competition (which I was really into at the time), and that meant I had to make something more advanced, and way more unique. In October of 2020, I had an interesting idea. I wanted to make a game with no visible sprites to interact with, just characters on a list. This was my first time doing this, and it was a real head-scratcher. I couldn’t really figure out how to do it, but after a lot of thinking, charting, and visualizing I got an idea. Eventually, after about 3 months of coding my theory, testing my theory, failing, and debugging, I managed to get a outcome that I was happy with. This was my first list game, and I was proud of it. It was my List Space Invaders.

After a while, I discovered that I could request my own projects to be curated and tried it with this project. I was lucky, and it did indeed get curated, and being on the front page, and getting attention on Scratch like I never had before fueled me. It fueled me to continue making list-based projects. But, because my list project got curated, I received a fair number of comments along the lines of “HOW??!!!!1”, and I felt the need to answer that. So, with a bit of work I made a Remixable List Game Starter. But, even after that I was fueled to make another idea of mine come true. It was to make a List Platformer. This took significantly longer, and I spent about half a year of daily coding to get an outcome I was happy with. I faced all kinds of new problems like momentum and detecting floors. But I did eventually get it done and shared, and with my knowledge of FPCs work now, I applied for my list platformer to be curated once again. I succeeded again, and this time my project boomed. I once again was fueled for my next big idea: my List Scrolling Platformer. I again went through basically the same process that I had for my last two projects, facing new challenges and problems. I again repeated this for my List Platformer Level Creator.

After this, the COVID pandemic was basically over, and life caught up to me. I ran dry on ideas and my account was dormant once again. I can see how this long, and recent dormant period can be a concern if you do choose to hand this guide over to me, but I assure you that not only am I active once again, but a handover would probably boost my activity. Also, you asked for experience writing long informational content as one of your qualifications, and I’m afraid I don’t have an example for that other than this incredibly long post. Lastly, my ideas on how to improve this guide. I personally have used this guide a lot in my coding life, and I always thought it would be nice to have a sort of “Frequently Asked For” section, where workarounds for the most asked for suggestions would be. Also, I would try to make a project with backpackable script for all of these. Another potential idea would be to add multiple workarounds of different “difficulties”, if possible, and I would probably add a few list-related workarounds from my experience of list coding. And needless to say, I would add more workarounds from the community as I receive them.

I feel that with all of these experiences, I would make a good candidate for this thread as I think outside the box (sometimes when I really don't need to), can stick to projects for long periods of time, and have a pretty good understanding of Scratch. That’s all, and I appreciate you taking the time to read this, and I would be honored to be selected to takeover and carry on this incredibly useful guide.

Please let me have more AI voices that can let me make my August 12th 2036 Heat death of the universe project

TRGreenSpaceman wrote:

Please let me have more AI voices that can let me make my August 12th 2036 Heat death of the universe project

Please make a new topic for this by going to the Suggestions forum, and clicking “New topic”.
Also, elaborate on your suggestion. Would this be for the TTS extension?

TRGreenSpaceman wrote:

Please let me have more AI voices that can let me make my August 12th 2036 Heat death of the universe project

Download the audio clip of loudward saying that then

Hi all! Thank you for the applications, 1080GBA and mitdk. Sorry for the radio silence on this thread for the last month or so. I took a break from Scratch while dealing with some personal safety issues, and unfortunately since those were related to my presence on Scratch, I wasn't able to engage with the site or forums or take the time to review applications.

If nothing wild comes up again, I'll be giving y'all's applications the thorough time I meant to previously over the next couple weeks. I'll share the selected approved application within the first few days of July. Thank you for your time and patience.

_nix wrote:

Hi all! Thank you for the applications, 1080GBA and mitdk. Sorry for the radio silence on this thread for the last month or so. I took a break from Scratch while dealing with some personal safety issues, and unfortunately since those were related to my presence on Scratch, I wasn't able to engage with the site or forums or take the time to review applications.

If nothing wild comes up again, I'll be giving y'all's applications the thorough time I meant to previously over the next couple weeks. I'll share the selected approved application within the first few days of July. Thank you for your time and patience.

Thanks

_nix wrote:

Hi all! Thank you for the applications, 1080GBA and mitdk. Sorry for the radio silence on this thread for the last month or so. I took a break from Scratch while dealing with some personal safety issues, and unfortunately since those were related to my presence on Scratch, I wasn't able to engage with the site or forums or take the time to review applications.

If nothing wild comes up again, I'll be giving y'all's applications the thorough time I meant to previously over the next couple weeks. I'll share the selected approved application within the first few days of July. Thank you for your time and patience.

No problem, and thank you!

Hi all!

I've decided to pass the next edition of this guide to @mitdk. This is thanks to a few things: your experience coding helps for sure, but I also got the sense that you're good at thinking outside the box; at not just working hard and being dedicated to whatever you are creating, but learning through that process, to get past your current obstacle… but also just to get a better understanding of Scratch and what you are creating! I appreciate that you've referred to this guide yourself, too (not a big deciding factor for me, but nice to have).

Thank you to 1080GBA and -RabbitWorld- both for your applications, as well. I didn't end up choosing either of yours, but they helped me to understand better what sort of person I would be looking for to take over this guide. If either of you end up still having interest in helping others with workarounds, then I'm sure mitdk will be happy to receive contributions, and I wish you luck with the next round if you want to run the thread yourself then.

And thanks a bunch to everyone who contributed workarounds and recommendations over the course of this thread!

mitdk, I don't immediately have concerns over your activity level because over the years I've been in a similar boat as you many times, certainly checking into Scratch regularly but not creating projects or participating much in the community unless inspiration strikes me. (At which point I might put myself into a project for months on end, haha.) I do feel I should recommend that if you find you aren't able to put much time or creativity into the guide anymore, though, that you consider passing it along. There are parts of me that wish I'd opened this thread up for takeover sooner, since I really didn't contribute much to it during its last few months, and I don't believe leaving it dormant and stagnant was a good thing. There's no shame in letting go of a project when you feel you have put all you have or want to offer into it — and even if whoever takes over the thread next makes some really radical changes, your own edition will still stick around, archived in Scratch forum history!

The last thing I have to bring up is the section on licensing credits and content reuse in the original takeover posting. To refresh your memory, please read it over again. The long and short of it is that while you don't need to credit me for any of my own (uncredited) workarounds in this thread, you do need to include, like I did, the same “thanks” and links to the original post for outside contributions. E.g, "thanks, @1080GBA!". You also need to ask people to continue to credit workarounds they reuse from your guide when you open it to takeovers. This is basically all just to make sure you and the forum community at large continue to respect both the creative commons license and the general virtue of crediting others and acknowledging the community effort that goes into a project like this. I don't think it's super controversial, but if you disagree and don't plan to credit anyone inside your thread, then please avoid referring to any specific workarounds from this guide, especially more complex ones, without asking their authors for permission directly (on their profile).

Let me know if you have any further questions! Please share a link to your thread here when you have it ready. No problem if that takes some time (I know getting this one started did for me) — after that point I'll close the thread down and refer visitors to yours, and I'm sure it'll get stickied shortly. Thank you!

For the repeat (n) seconds block, use the not less than workaround to greater than or equal to. Not too big of a change

_nix wrote:

Hi all!

Maybe now you could change the name so it doesn't say "[Takeover applications open!]" anymore.

k7e wrote:

_nix wrote:

Hi all!

Maybe now you could change the name so it doesn't say "[Takeover applications open!]" anymore.

Oh you're totally right, good catch. Thanks!

Has a new topic been made yet?

Some of the rejected blocks should be on here, like the cloud list workaround