Remote event not being received by client

Help and Feedback Scripting Support
#22

further i think the first variable sent with an event is always the player its firing for, both ways, so try putting as first variable in the localscript “player”, and then defining the other variables:

UIEvent.OnClientEvent:Connect(function(player,action,Terminal,Team,TermStatus)
1 Like
#23

The player only needs to be referenced in Client > Server remote event scripts, and is only necessary when the server needs to know which player sent the remote event.

1 Like
#24

Can you try copying your system into a new baseplate? Also, in unexpected scenarios like this, we can’t draw much conclusions other then to speculate possible causes, based on little evidence. I know you said nothings interfering, but you should you check your remotes existence when fireallclient is called. Possibly you might want to provide a place file, so we can better help.

1 Like
#25

Yep, everything has been copied and pasted identically from the testing game

1 Like
#26

I have checked the existence on both the client and the server as well as checking it has been fired from the server

1 Like
#27

Update:

I have since tried copying the system into another game. This still causes it to break

#28

don’t use the parent part of Instance.new. Instead, set the parent of the remote event manually using instance.Parent.

#29

I didn’t read all the replies but have you tried just making the RemoteEvent manually instead of relying on a script to create one?

If you can’t/already tried that, try this:

local UpdateUIEvent = Instance.new("RemoteEvent");
UpdateUIEvent.Parent = game:GetService("ReplicatedStorage");
UpdateUIEvent.Name = "RaidUI";

Also check on the client that the RemoteEvent is inside ReplicatedStorage when you join in.

#30

I have tried doing this already, the issue I am having is that the client does not appear to be receiving any information from the remote event at all when it is fired from the server

#31

I have tried this as well as just making the remote event manually and putting it in replicated storage but this still does not work

#32

We resolved this in a call together. The actual problem had nothing to do with this bit of code, the actual problem was a remote function in which the server infinitely yielded with no return. It is now resolved.

#33

Nice investigation I had the same cause also. You saved my life!

1 Like