Set Image Block Bug?

For people with a HS subscription:
In one of my projects, the new “set image” block sometimes won’t change the image, but other times it will. Has anyone else experienced this or know why this is happening?



I do not have a Hopscotch subscription, and I cannot afford one, so I was afraid that I do not have any experience with it.

1 Like

Ok, thanks anyway! :slightly_smiling_face:

I’ve no subscription but can you show a screenshot of your code? I know a few bugs with set text and they might be the same.

Anyways, do you care to enter my story contest? It’s in my “Story on the Forum” topic.

I just used the set image block as I normally do.

1 Like

Try getting rid of self and replace it with original object. 7 = 7 also works for clones… so.

How do I enter? :upside_down_face::smiley:

Where did I use “self”?

EDIT: Ohh I see now

You enter by voting for a story.

1 Like

You used it for the variable image. Try either original object or the actual object.

1 Like

@Madi_Hopscotch_, if you didn’t know there is a bug discovered by @Thinbuffalo that was alarming as a looped set text would cause a crash. It took about 60 seconds for the crash to occur. Earlier today, Awesomeonion had edited the code adding a small wait inbetween each frame calculation with the set text block (and I believe so with set image too) so frames are calculated slower so it is possible that due to the edit such codes like set text & set image are not appearing.

Here is another bug Report:

The Set Image block works for subscribers as well as non-subscribers.

Can you post a screenshot of some of your other code, where you set the Image variable?

1 Like

I doubt that. I saw her code and everything looks fine. I believe that it is the changes awesomeonion did to set text & set image, because I’ve seen other bug reports like this.

1 Like

I wonder if i can go to an archive of the hopscotch webplayer and inject it into hopscotch app

That’s probably not allowed. I only think THT can do that.

1 Like

if you do the json thing i think theres a webplayer js file so its only a local change

lol no i wouldnt hack something like this, on a global scale


1 Like

@BlastFusion so if it is because of awesomeonion’s change, Is there a way to fix the problem?


We should wait until Awesomeonion has fixed it. For now, you should try removing the loop somehow and it should work fine.


The problem is that most of my code in that project involves those loops… :joy:

1 Like