Title

Look up “scratchattach” or “scratchclient” and go from there. If you don't like reading documentation the function is your best friend.

cloud variables

50_scratch_tabs wrote:

Look up “scratchattach” or “scratchclient” and go from there. If you don't like reading documentation the

dir()

function is your best friend.

Hey, sigma. While this can work, you can do it without this! Simply use the requests module and send requests to the Scratch API! Then you can fanum tax all the information you want from the Scratch API, like Duke Dennis fanum taxing a new style of nonchalant dreads! For some more sigma documentation on the Scratch API, see here. Remember to maintain a 0.1 second wait between requests, otherwise you might get rate limited! And that's not sigma!

Mikael99109 wrote:

(#4)

50_scratch_tabs wrote:

Look up “scratchattach” or “scratchclient” and go from there. If you don't like reading documentation the

dir()

function is your best friend.

Hey, sigma. While this can work, you can do it without this! Simply use the requests module and send requests to the Scratch API! Then you can fanum tax all the information you want from the Scratch API, like Duke Dennis fanum taxing a new style of nonchalant dreads! For some more sigma documentation on the Scratch API, see here. Remember to maintain a 0.1 second wait between requests, otherwise you might get rate limited! And that's not sigma!

Geez, can you ease up on the slang? That's too much, even for me, and some of my classmates are obnoxious with their slang.

Getting off-topic. Anyways, it is better to use modules that are already built because they have information in an easier-to-use format. I find it easier. Personally, I think modules are better because they have the whole API right there and then you don't need to worry about casting, errors, and most importantly, updating your code when the Scratch API updates!