C_talyst thingy

https://scratch.mit.edu/projects/191533753/ <iframe allowtransparency="true" width="485" height="402" src="//scratch.mit.edu/projects/embed/191533753/?autostart=false" frameborder="0" allowfullscreen></iframe>   1. I had A LOT of difficulties with bugs, and things that weren't supposed to do the things they weren't supposed to. I sort of fixed them by switching and changing some of the codes around, where if this is supposed to disappear and it doesn't do it, then I'll just make it disappear again. Also, the text box glitch when the opponent's pokemon faints, is almost impossible to fix, so it's left in the game. Some other things I had trouble with were just mixing things around with other codes, or accidentally leaving some code that wasn't supposed to be there on that code. For example, I left a code that stops everything on a separate script and that stopped the whole game, when I removed

https://drive.google.com/file/d/19zIDo_BngG7h2sQQP3j2rTE97q9kJOia/view

1. Some of the differences of big games and independent games are that the big games usually look "high budget" like it looks really good, it's made by multiple people, the art work and graphics are made by multiple teams and the style of the games are quite mainstream. However, in a independent game, you're free to do whatever, make whatever you want, the art style can be lazy, or cartoon-ish. But doing an independent game can be very difficult as it takes a long time to make by only yourself or a couple others. 2. Some of the things that the developers had to overcome was the fact that the game can be very glitchy, and it can ruin the game, or the fact that their fans wanted the game as soon as possible, or pleaded for the game to come out. Not only that but overcoming mental health as well, as some went through depression, and some might've gone through sleep deprivation. 3. The things that I would like about working on an indie game would be that I can mak

https://drive.google.com/file/d/1VIbBzdWwfvbOEddW6JqdWYWSVl1bdqF5/view