when I receive [ The entering]
set [ score] to [0]
switch costume to [ Start]
say [Pres your mouse or click space] for (2) secs
forever
if <<mouse down?> or <key [ space] pressed?>> then 
switch costume to [ Question]
 if authorised
switch costume to [ 3] 
wait (0.5) secs
switch costume to [ 2] 
wait (0.5) secs
switch costume to [ 1] 
wait (0.5) secs
hide
broadcast [ start]
else
wait (7) secs
switch costume to [ You don't get to play]
stop [ all]

now the problem is this, its that it doesn't give enough time to click space or mouse down

So why do you have the else block doing what it does? You'd be better using the timer and waiting for the start input (mouse or space) or timer > 2.

So

say [Press space or click mouse]
reset timer
wait until <<(timer) > [2]> or <<mouse down?> or <key [space v] pressed?>>
if <(timer) < [2]> then
start game
else
fail message
end

deck26 wrote:

So why do you have the else block doing what it does? You'd be better using the timer and waiting for the start input (mouse or space) or timer > 2.

So

say [Press space or click mouse]
reset timer
wait until <<(timer) > [2]> or <<mouse down?> or <key [space v] pressed?>>
if <(timer) < [2]> then
start game
else
fail message
end

Oh thanks!

deck26 wrote:

So why do you have the else block doing what it does? You'd be better using the timer and waiting for the start input (mouse or space) or timer > 2.

So

say [Press space or click mouse]
reset timer
wait until <<(timer) > [2]> or <<mouse down?> or <key [space v] pressed?>>
if <(timer) < [2]> then
start game
else
fail message
end

I would like to bring to your attention an issue that has arisen in my project. While I was able to successfully resolve the timer issue, there is now a problem where the audio does not play upon broadcasting start. I would appreciate any guidance or support you could provide in addressing this matter.

Share the project please. Are you sure you're not starting the sound in a loop?

deck26 wrote:

Share the project please. Are you sure you're not starting the sound in a loop?

Nah, I ain't.

https://scratch.mit.edu/projects/961877686/editor/

Why do you still have the forever loop in the script I already helped with? That's broadcasting start repeatedly as long as timer is less than 2 and then stopping the project. It should only run once after the wait until so the forever loop is not wanted.

deck26 wrote:

Why do you still have the forever loop in the script I already helped with? That's broadcasting start repeatedly as long as timer is less than 2 and then stopping the project. It should only run once after the wait until so the forever loop is not wanted.

Oh I do? Oh man that not how its supposed to be

lol me reading thru this be like

Aftons_fan913 wrote:

lol me reading thru this be like

Lol

deck26 wrote:

Why do you still have the forever loop in the script I already helped with? That's broadcasting start repeatedly as long as timer is less than 2 and then stopping the project. It should only run once after the wait until so the forever loop is not wanted.

I would like to bring to your attention that the ghost effect appears to be encountering some issues. The feature is not functioning as intended, and the root cause of the problem remains unclear.

@deck26

Cyethawne wrote:

deck26 wrote:

Why do you still have the forever loop in the script I already helped with? That's broadcasting start repeatedly as long as timer is less than 2 and then stopping the project. It should only run once after the wait until so the forever loop is not wanted.

I would like to bring to your attention that the ghost effect appears to be encountering some issues. The feature is not functioning as intended, and the root cause of the problem remains unclear.

So explain when it occurs and how to replicate it. Which scripts/sprites are involved?

Generally you're better asking new questions in a new topic.

deck26 wrote:

Cyethawne wrote:

deck26 wrote:

Why do you still have the forever loop in the script I already helped with? That's broadcasting start repeatedly as long as timer is less than 2 and then stopping the project. It should only run once after the wait until so the forever loop is not wanted.

I would like to bring to your attention that the ghost effect appears to be encountering some issues. The feature is not functioning as intended, and the root cause of the problem remains unclear.

So explain when it occurs and how to replicate it. Which scripts/sprites are involved?

Generally you're better asking new questions in a new topic.

The following text outlines an issue related to sprites in a programming context. The sprites in question are BORDER, Sprite1, Sprite2, Sprite3, and Sprite4. When the “start” command is received, the code is programmed to execute the following function:

when I receive [ start]
set [ ghost] effect to (100)

However, it appears that the ghost effect is not being set to 100 upon receipt of the “start” command.ffect is not being set to 100 upon receipt of the “start” command.

Seems to work for me. What are you expecting to see? Why are you waiting 28 seconds to go from a a hidden sprite to a ghosted sprite?

deck26 wrote:

Seems to work for me. What are you expecting to see? Why are you waiting 28 seconds to go from a a hidden sprite to a ghosted sprite?

Because there is first an audio that takes about that time but ill remove the wait and see if there's a difference.

Cyethawne wrote:

deck26 wrote:

Seems to work for me. What are you expecting to see? Why are you waiting 28 seconds to go from a a hidden sprite to a ghosted sprite?

Because there is first an audio that takes about that time but ill remove the wait and see if there's a difference.

You also have various stop all blocks so are you sure the project isn't stopping before the 28 second is up. You still haven't said what you expect to see.

deck26 wrote:

Cyethawne wrote:

deck26 wrote:

Seems to work for me. What are you expecting to see? Why are you waiting 28 seconds to go from a a hidden sprite to a ghosted sprite?

Because there is first an audio that takes about that time but ill remove the wait and see if there's a difference.

You also have various stop all blocks so are you sure the project isn't stopping before the 28 second is up. You still haven't said what you expect to see.

I am expecting not to see those certain sprites at all because the ghost effect is on? I was informed that's how it worked. No, I'm fairly sure it isn't stopping as other audios continue but that certain sprite may not work. That might be it. Possibly.

But why show and ghost when they were previously hidden anyway? The ghost effect is cancelled when the project stops but a hidden sprite won't show just because the project has stopped.

deck26 wrote:

But why show and ghost when they were previously hidden anyway? The ghost effect is cancelled when the project stops but a hidden sprite won't show just because the project has stopped.

they were previously hidden so that they wouldn't cover the start sprite then when the start sprite goes they will show. they need to show coz the fi touching has to work