triggerLatentClientEvent is bugged?

[GTX]

Hello. I'm trying to send a long string with triggerLatentClientEvent, but the other side doesn't recieve it. I realized that, when I use triggerLatentClientEvent once, I can't use triggerClientEvent any more. How did I test:

Resource1:

- Server

  
function co(a, b) 
    string = "very long string... I won't post it." 
    triggerLatentClientEvent(a, "startThis", 50000, false, root, string) 
end 
addCommandHandler("fny", co) 
  

Resource2:

- Client

  
function co2(string) 
    outputChatBox"asd" -- It did not output that. 
    -- Do the magic here. 
end 
addEvent("startThis", true) 
addEventHandler("startThis", root, co2) 
  

After I realized it did not work, I tried with triggerClientEvent and that did NOT work also. When I rebooted the VPS, triggerClientEvent worked. But when I used triggerLatentClientEvent again, both didn't work.

Weird...

I am using Linux, Debian 6.0 - 64bit. Is my VPS messed up, am I doing something wrong or is MTA/function bugged?

Thanks in advance.

[Renkon]

The most probable reason is that you were still triggering the latent client event when you restarted the resource so it may have been fine that you couldnt do anything.

Despite other stuff, I actually use triggerClientEvent and I pass 1 kilobyte in each trigger so it doesnt get saturated...

[GTX]

I fixed it. The problem was in my client-side code. Thanks for trying to help me!