ryden Posted April 10, 2008 Share Posted April 10, 2008 If you do server-side triggerClientEvent, the client won't queue the event call until the script is completely downloaded and started (onClientResourceStart), making that sometimes in the debug console it alerts that the server tried to call an unexistant event. Link to comment
Mr.Hankey Posted April 10, 2008 Share Posted April 10, 2008 If you do server-side triggerClientEvent, the client won't queue the event call until the script is completely downloaded and started (onClientResourceStart), making that sometimes in the debug console it alerts that the server tried to call an unexistant event. I can't see a bug in there. It's just logic that the event doesn't exist as long as the client script hasn't started Link to comment
ryden Posted April 10, 2008 Author Share Posted April 10, 2008 If you do server-side triggerClientEvent, the client won't queue the event call until the script is completely downloaded and started (onClientResourceStart), making that sometimes in the debug console it alerts that the server tried to call an unexistant event. I can't see a bug in there. It's just logic that the event doesn't exist as long as the client script hasn't started That's exactly the bug, that the event should be queued. Link to comment
Mr.Hankey Posted April 11, 2008 Share Posted April 11, 2008 That's exactly the bug, that the event should be queued. Um?! the event can't exist if the client hasn't downloaded the files completle because the .lua client script file where the event is added simply isn't complete on his pc. Link to comment
ryden Posted April 11, 2008 Author Share Posted April 11, 2008 That's exactly the bug, that the event should be queued. Um?! the event can't exist if the client hasn't downloaded the files completle because the .lua client script file where the event is added simply isn't complete on his pc. And that's why it should be queued until it's completely downloaded. To wait for the script to add the event handler so it can act in consequence. Link to comment
lil Toady Posted April 12, 2008 Share Posted April 12, 2008 If client'd be queueing every unexistant event it could work out not well i suppse. You can request the data from client when it's script has started, instead of sending it right on resource start. Link to comment
ryden Posted April 13, 2008 Author Share Posted April 13, 2008 If client'd be queueing every unexistant event it could work out not well i suppse. You can request the data from client when it's script has started, instead of sending it right on resource start. It's not queueing unexistant events. It's just waiting for the resource to be downloaded and started. After that, nothing is queued. Link to comment
darkdreamingdan Posted April 27, 2008 Share Posted April 27, 2008 This isnt going to happen. First argument is that the script doesnt exist so it doesnt make sense. Second is that an event doesnt necessarily belong to a specific resource. You're saying that all event triggers should be put on hold until the client has downloaded all scripts. This will surely break other scripts that require events. Link to comment
Recommended Posts