Message Passing: Sending only one message (SOLVED)

Questions
1

Hello I hope that everything is well.

I am trying to send a message when a collision is detected, but since the collision occurs for a prolonged period of time I only want the message to be sent once. How might I go about doing that?

I have the script set up like this:

elseif message_id == hash("collision_response") and not canenter then
	msg.post("printer2#printer_example2", "dialogue2")
end

How could I alter this?

Thanks,
V

2

What is canenter here??

Assuming it to be a local variable, a small alteration could be to store it self

elseif message_id == hash("collision_response") and not self.canenter then
	msg.post("printer2#printer_example2", "dialogue2")
end

-- reset self.canenter after a specific set of conditions have been 
-- fulfilled, like the printer has stopped printing the message

Another way could be to use a trigger response instead of a collision response and use message.enter, which is only sent once the player enters

if message_id == hash("trigger_response") then
   if message.enter then
	   msg.post("printer2#printer_example2", "dialogue2")
   end
end

But remember to change collision type of your door/ whatever it is that you are entering to trigger :wink:

2 Likes
3

Hmm, I really like the trigger response solution but something weird seems to be happening.

Whenever I use the arrow keys and try to move through the door, the dialogue box pops up, but goes away once I let go of the arrow keys. This leads me to believe that the message stops sending at some point. The weird thing is, if I try to do the same thing, but instead I use the mobile controls I made (which are on the screen and move the character via ‘messages_id’ rather than ‘input_id’) then the text box stays up just fine…

Do you know if I might have done something wrong?
Please let me know if I poorly explained myself.

Best,
V

4

It’s hard to tell like this what may be wrong here. Can you share your player script ?

5

Ok, here is the player script

script.txt (8.1 KB)

Thanks so much for your help!

6

Hey there!!!
I examined your player script and there doesn’t seem anything much off with it. Try printing message_id in the on_message function of your printer script to see what all message it is actually receiving?

7

Hey!

Everything on that end seems to be working normal, it is receiving dialogue2 just as it should.

The trigger_response message.enter is sending just fine, and the box appears. Strangely though, message.enter is called twice. This is causing for the printer to open then close and do a bit of a dance before finally not opening at all…

adventure game - UP TO DATE.zip (8.3 MB)

This is the game file incase I poorly explained myself. (So sorry for the atrociously sloppy code!)

For context: checkpoint.script is the door the player must travers through at the end of the level. printer2.gui_script is the script that opens up the printer.

Thanks so much for your help!

8 
if message_id == hash("trigger_response") then
		print("entering")
		msg.post("printer2#printer_example2", "dialogue2")
		
	else
		print("exiting")
		-- msg.post("player#player", "frozen")
		--go.delete()
	end

according to this script, whenever something enters the trigger region, it will keep sending the dialogue message to the printer, creating that weird effect you described.

Try changing the code to:

if message_id == hash("trigger_response") then
   if message.group == hash("player") and message.enter then 
		print("entering")
		msg.post("printer2#printer_example2", "dialogue2")	
   end
end

This should do the trick. :slight_smile:

4 Likes
9

Worked like a charm! Thanks so much!

1 Like