This project showcases a bug with the [broadcast [] and wait] block. Here, Alice and Bob use that block to ask each other questions and wait for the response. If the code worked properly, Alice and Bob would have this conversation: Alice: Hey Bob, what do you want to do today? Bob: I don't know Alice, what do you want to do today? Alice: I don't don't know, do you want to try spelunking? Bob: That sounds like a great idea! Alice: Awesome, let's go! Instead, as soon as Bob asks Alice a question with the "ask person" signal, Alice's ask person signal stops waiting and the code after that block executes, while Bob's script simply deactivates as if a [stop other scripts in this sprite] block were used. Of course, this is a rather silly way to use signals, since Alice and Bob are both sprites and there's no reason for them to have a local "name" variable, but what if Alice and Bob were clones of the same sprite? In that case, this could be a useful communication paradigm.