caftingdead261 wrote:

CLOUD LOG ARE BACK THIS IS NOT A DRILL I REPEAT CLOUD LOGS ARE BACK THIS IS NOT A DRILL

wvzack wrote:

Good news everyone the logs just came back up

mas6y6 wrote:

THE CLOUD LOGS ARE BACK!!!!!!!@!

EpicCoderGamer1000 wrote:

mas6y6 wrote:

THE CLOUD LOGS ARE BACK!!!!!!!@!

We know

when green flag clicked
if <cloud_logs = back up> then 
say [yes!!]
  

else
sad
end

8_bit_pixel wrote:

Just found this, seeing how to import to CodeSandbox.

EpicCoderGamer1000 wrote:

mas6y6 wrote:

THE CLOUD LOGS ARE BACK!!!!!!!@!

We know

Eason_9 wrote:

I already installed scratchattach but it says I haven't. Can anyone help?

Picture here btw: https://u.cubeupload.com/eason_9_lol/Screenshot2024012015.png

(also cloud logs are up!!!! )

import scratchattach as scratch3

events = scratch3.CloudEvents(“project_id”)

@events.event
def on_set(event): #Called when a cloud var is set
print(f“{event.user} set the variable {event.var} to the value {event.value} at {event.timestamp}”)

@events.event #Called when the event listener is ready
def on_ready():
print(“Event listener ready!”)

events.start()

TheMobileGames wrote:

Hey, does anyone know of some problems that I could have made that results in a lot of data being lost? I am currently using cloud events such as this and I’m wondering if it’s lossless when the project is full of people and busy (constant cloud variable changes):

import scratchattach as scratch3

events = scratch3.CloudEvents(“project_id”)

@events.event
def on_set(event): #Called when a cloud var is set
print(f“{event.user} set the variable {event.var} to the value {event.value} at {event.timestamp}”)

@events.event #Called when the event listener is ready
def on_ready():
print(“Event listener ready!”)

events.start()

Also, from a single account, how fast can these variables be set with Scratchattach? Is it possible to set all 10 of them at max speed (10 per second, I think) while being completely lossless?

Lastly, does anyone have any tips for me to indeed make these things (events and setting cloud variables) lossless (or almost/close to lossless) while keeping the same speed? I would much rather resolve this without editing my Scratch code itself please.

import scratchattach as scratch3
session = scratch3.Session("sessionid", username="username")
conn1 = session.connect_cloud("projectid")
conn2 = session.connect_cloud("projectid")
conn1.set_var("var", "value") # Sets a cloud var using connection 1
conn2.set_var("var", "value") # Sets a cloud var using connection 2

RandomPerson13764 wrote:

bro, remove the module. delete it now. people are hacking with it like crazy!

wvzack wrote:

Air_heads wrote:

wvzack wrote:

Air_heads wrote:

wvzack wrote:

-ProXeeI wrote:

RandomPerson13764 wrote:

bro, remove the module. delete it now. people are hacking with it like crazy!

who ?

Check robot destructor people are abusing and I hope this won’t happen but I would not be surprised if the st gets rid of scratchattach projects

People can still do it without scratchattach -_-

True but it sure simplifies it and yes people use html and js but still the blame goes on scratch attach.

I still don’t get your argument as to why the blame should be on Scratchattach …
If the API is public, then anyone can utilize it, and if you’re talking about JavaScript, scratchattach is completely irrelevant as it is a python library.

The blame goes on scratch attach because it is known of and well people don’t know much more than the basic programming in scratch and they have no idea how everything else works. (Notevveryone of course)

TimMcCool wrote:

RandomPerson13764 wrote:

bro, remove the module. delete it now. people are hacking with it like crazy!

Just like every useful tool, scratchattach can be abused. However, deleting the library would harm Scratch's Python dev community while it wouldn't stop hackers at all: There are plenty of other libraries that support setting cloud variables (many of these existed before scratchattach). Hackers could just use one of these libraries instead.

TimMcCool wrote:

RandomPerson13764 wrote:

bro, remove the module. delete it now. people are hacking with it like crazy!

Just like every useful tool, scratchattach can be abused. However, deleting the library would harm Scratch's Python dev community while it wouldn't stop hackers at all: There are plenty of other libraries that support setting cloud variables (many of these existed before scratchattach). Hackers could just use one of these libraries instead.

TimMcCool wrote:

Cloud events should be lossless because they use the clouddata log to detect cloud activity.
Setting cloud variables is not garantueed to be lossless. You can reduce loss by reconnecting to the cloud regularly (close old connection and open new connection).
When setting cloud variables with scratchattach using a CloudConnection, there is a 0.1s cooldown between cloud variable sets. (You can only use the conn.set_var function 10 times per second.) However you can open multiple cloud connections to a project in order to set cloud variables more often (using only one session / one account):

import scratchattach as scratch3
session = scratch3.Session("sessionid", username="username")
conn1 = session.connect_cloud("projectid")
conn2 = session.connect_cloud("projectid")
conn1.set_var("var", "value") # Sets a cloud var using connection 1
conn2.set_var("var", "value") # Sets a cloud var using connection 2

import scratchattach as scratch3
session = scratch3.login("TheMobileGames", os.environ["PASSWORD"])
conn1 = session.connect_cloud("project_id")
events = scratch3.CloudEvents("project_id")
@events.event
def on_set(event):
    conn1.set_var("event.var", "0")
@events.event
def on_ready():
   print("Event listener ready!")
events.start()

EpicCoderGamer1000 wrote:

(#2268)

Eason_9 wrote:

I already installed scratchattach but it says I haven't. Can anyone help?

Picture here btw: https://u.cubeupload.com/eason_9_lol/Screenshot2024012015.png

(also cloud logs are up!!!! )

What are you using to code

Also you don't need to use the cloud emoji to set a var

TheMobileGames wrote:

…Am I really supposed to make 10 connections and a function that takes in “event.var” and sets it to the last used connection? If there isn’t one already, there should be a function in Scratchattach that can “just” handle setting 5-10 cloud variables with each being changed 10 times a second. Maybe there could be one that opens as many connections as it needs and automatically closes them, all internally, so all someone has to do is use it and it works even when it’s setting a lot quickly.

TheMobileGames wrote:

If there isn’t one already, there should be a function in Scratchattach that can “just” handle setting 5-10 cloud variables with each being changed 10 times a second.

import scratchattach as scratch3
session = scratch3.login("TheMobileGames", os.environ["PASSWORD"])
conn1 = session.connect_cloud("project_id")
events = scratch3.CloudEvents("project_id")
@events.event
def on_set(event):
    conn1.set_var("event.var", "0")
@events.event
def on_ready():
   print("Event listener ready!")
events.start()

    if str(event.value) != "0":
        ...