A quick system I threw together to handle requests between a server and client(s). For now, all it does is send a message to the recipient if they are on the project at that time. If you send a message to the server, if whoever is acting as the server is also on this project, the server will reply with an ok message. Note: delays of up to 5 seconds may occur when sending requests if the last request any user made was not received. The clients wait 5 seconds before assuming that the previous message will never be received by the intended recipient and then deleting it. Otherwise, once one message failed to be received, no one else could send messages. This project was inspired by @jordan1060's comment on my profile about using a server communicating with clients to securely store information on Scratch. In such a system, clients can request information from the server using global variables. Some stuff takes half a second to update when you press the flag. This is just built-in delay for the project to check if you are the server. This delay would be fixed in a final version. Just don't click anything in the first half second and it will be fine. Also, variables take a second to disappear after pressing the stop button. This is intentional, and has to do with the way the timer works. I could make the variables disappear sooner, but that might cause some lag because the script would be continually resetting the timer while the project is running. Press 1 to stop being the server if you are currently the server. This sets the server to a nonexistent username (space, so as not to be confused with the empty string of logged out users), so requests to the server will not be received until someone becomes the server. Credits: @jordan1060 for the idea encode and decode procedures are made by me and are from another project I am working on
