Your glitches are probably related to Mac and Chrome and not related to Scratch.

footsocktoe wrote:

My browser / operating system: Windows 7, Microsoft Internet Explorer 11.0, Flash 26.0 (release 0)

My browser / operating system: MacOS Macintosh X 10.10.5, Chrome 59.0.3071.115, Flash 26.0 (release 0)

hmmm……

Code_Pi wrote:

footsocktoe wrote:

My browser / operating system: Windows 7, Microsoft Internet Explorer 11.0, Flash 26.0 (release 0)

My browser / operating system: MacOS Macintosh X 10.10.5, Chrome 59.0.3071.115, Flash 26.0 (release 0)

hmmm……

You might want to research Mac problems in Discuss Scratch. I see those topics from time to time but immediately forget them since I have Windows.

footsocktoe wrote:

Code_Pi wrote:

footsocktoe wrote:

My browser / operating system: Windows 7, Microsoft Internet Explorer 11.0, Flash 26.0 (release 0)

My browser / operating system: MacOS Macintosh X 10.10.5, Chrome 59.0.3071.115, Flash 26.0 (release 0)

hmmm……

You might want to research Mac problems in Discuss Scratch. I see those topics from time to time but immediately forget them since I have Windows.

I have windows, I just can't use it for a week or so. did you try the other glitch? also, where can I find this mac problem page?

Code_Pi wrote:

I have windows, I just can't use it for a week or so. did you try the other glitch? also, where can I find this mac problem page?

I tried googling
mac problems discuss scratch
but there were so many posts it's not practical to search for your problem that way, I guess.

Wait until you can use Windows again and see what happens. Then you will know for sure.

What's the other glitch?

footsocktoe wrote:

Code_Pi wrote:

I have windows, I just can't use it for a week or so. did you try the other glitch? also, where can I find this mac problem page?

I tried googling
mac problems discuss scratch
but there were so many posts it's not practical to search for your problem that way, I guess.

Wait until you can use Windows again and see what happens. Then you will know for sure.

What's the other glitch?

oh, the other example I put up there.

Yes, I see that glitch. It might be related to the use of lists inside define blocks. I just got through troubleshooting a project where lists in define blocks were a problem. Especially if any of them are nonrefresh, but even if they are not there can be problems. I don't know why.

I would do your movement keys on their own and not inside a define block. That might solve the second glitch. Although too thin a wall thickness can also cause that kind of a glitch. I didn't check to see if you were moving more pixels than the walls are thick.

footsocktoe wrote:

Yes, I see that glitch. It might be related to the use of lists inside define blocks. I just got through troubleshooting a project where lists in define blocks were a problem. Especially if any of them are nonrefresh, but even if they are not there can be problems. I don't know why.

I would do your movement keys on their own and not inside a define block. That might solve the second glitch. Although too thin a wall thickness can also cause that kind of a glitch. I didn't check to see if you were moving more pixels than the walls are thick.

the walls are very thick, the things you see are just the visual effects.

so the project works perfectly for you? aside from the second glitch…

Code_Pi wrote:

footsocktoe wrote:

Yes, I see that glitch. It might be related to the use of lists inside define blocks. I just got through troubleshooting a project where lists in define blocks were a problem. Especially if any of them are nonrefresh, but even if they are not there can be problems. I don't know why.

I would do your movement keys on their own and not inside a define block. That might solve the second glitch. Although too thin a wall thickness can also cause that kind of a glitch. I didn't check to see if you were moving more pixels than the walls are thick.

the walls are very thick, the things you see are just the visual effects.

so the project works perfectly for you? aside from the second glitch…

It's not the absolute value of the thickness, it's the thickness relative to how far the sprite can move in one move. For example, a sprite that can move 20 pixels in one move can go through any walls that are less than 20 pixels thick.

footsocktoe wrote:

Code_Pi wrote:

footsocktoe wrote:

Yes, I see that glitch. It might be related to the use of lists inside define blocks. I just got through troubleshooting a project where lists in define blocks were a problem. Especially if any of them are nonrefresh, but even if they are not there can be problems. I don't know why.

I would do your movement keys on their own and not inside a define block. That might solve the second glitch. Although too thin a wall thickness can also cause that kind of a glitch. I didn't check to see if you were moving more pixels than the walls are thick.

the walls are very thick, the things you see are just the visual effects.

so the project works perfectly for you? aside from the second glitch…

It's not the absolute value of the thickness, it's the thickness relative to how far the sprite can move in one move. For example, a sprite that can move 20 pixels in one move can go through any walls that are less than 20 pixels thick.

i know

I'm on my Mac currently. I'll try to see whether it works on Windows.

(O_O)

andyhanwu wrote:

I'm on my Mac currently. I'll try to see whether it works on Windows.

thx

Code_Pi wrote:

footsocktoe wrote:

My browser / operating system: Windows 7, Microsoft Internet Explorer 11.0, Flash 26.0 (release 0)

My browser / operating system: MacOS Macintosh X 10.10.5, Chrome 59.0.3071.115, Flash 26.0 (release 0)

hmmm……

I just got on with the same browser / os as you: My browser / operating system: Windows 7, Microsoft Internet Explorer 11.0, Flash 26.0 (release 0)

for some reason I still got the bug…

Code_Pi wrote:

Code_Pi wrote:

footsocktoe wrote:

My browser / operating system: Windows 7, Microsoft Internet Explorer 11.0, Flash 26.0 (release 0)

My browser / operating system: MacOS Macintosh X 10.10.5, Chrome 59.0.3071.115, Flash 26.0 (release 0)

hmmm……

I just got on with the same browser / os as you: My browser / operating system: Windows 7, Microsoft Internet Explorer 11.0, Flash 26.0 (release 0)

for some reason I still got the bug…

I also saw the second glitch. Maybe I don't understand what you think the first glitch is? Does it happen all the time? Because I had no trouble moving both sprites around whether one was against a wall or not. But maybe you meant it had to be stuck halfway through the wall?

footsocktoe wrote:

Code_Pi wrote:

Code_Pi wrote:

footsocktoe wrote:

My browser / operating system: Windows 7, Microsoft Internet Explorer 11.0, Flash 26.0 (release 0)

My browser / operating system: MacOS Macintosh X 10.10.5, Chrome 59.0.3071.115, Flash 26.0 (release 0)

hmmm……

I just got on with the same browser / os as you: My browser / operating system: Windows 7, Microsoft Internet Explorer 11.0, Flash 26.0 (release 0)

for some reason I still got the bug…

I also saw the second glitch. Maybe I don't understand what you think the first glitch is? Does it happen all the time? Because I had no trouble moving both sprites around whether one was against a wall or not. But maybe you meant it had to be stuck halfway through the wall?

you have to be running against the wall for the glitch to work

Sorry for a late reply! It seems like a glitch. I suggest re-doing the script for the players. I have a few questions. Is it multiplayer? Are they connected to each-other with any other script? It would be helpful if you could share the project so I could take a closer look.

ArrowlineDragon wrote:

Sorry for a late reply! It seems like a glitch. I suggest re-doing the script for the players. I have a few questions. Is it multiplayer? Are they connected to each other with any other script? It would be helpful if you could share the project so I could take a closer look.

oops… I unshared it.

Still unshared

had trouble sharing it. https://scratch.mit.edu/projects/169707528/

The Green Player is totally dysfunctional now.