Search results

Fougerite Version? Errors?

You will know soon.

UnityEngine dll is a server file..

Sorry, doesn't really seem worthy. We have RustBuster for this.

It does work here..

Client Changes: Hooks class's GetPlayers() and LocalPlayer variables are now static, sorry for that. Some fixes Security Update

It will need the assembly, but i cannot test it without somebody. Yeah. Actually it doesnt matter

Can you test this and send me the debug logs please?

I was talking about the screenshot, not the code :P But doesn't matter now, thanks for sharing.

I was talking about the screenshot not the code :p

Thats probably a 1.5.6 pre release bug. Will fix.

Looks like this Uses the same variable that the method uses for getting the endpoint, hopefully It will work. Message tag syntax will look like this: [uLink Ignore] Ignored Socket from

@McRustReloaded Both codeparts patched. You will see it in the console and the logs with the red message popping up. Let us know if you got anything.

Multicore is sadly not supported in Rust Legacy. Don't ask why. That is the reason that using Threads are sometimes dangerous, such as UnityEngine.Object.Find...

@salva might wanna do a show off?

@McRustReloaded I will be posting you a uLink.dll that will have the message thing in It. It happens when there is something wrong with the connection's message. Second method: I will change the endpoint to public and that will allow me to print the IP Address out. We could test...

I will see if i can find the code in ulink, and atleast print the IP Address that causes this error. That would help us know if this is true or not. There isn't. I will be adding the code for that.

https://lab.facepunch.com/rust/bd96/nitrous_networks_ignored_number_of_socket_network_reset_errors_/post/24664518#post24664518 @McRustReloaded Something connected to ulink, don't exactly know. I will see if i can find the code in ulink, and atleast print the IP Address that causes this error...

According to this post It's a ulink attack, not an actual ddos thing, but similar to it.

@McRustReloaded (18:36:53) | 29214.813 (3/29/2017 7:37:31 PM): Ignored number of socket network reset errors: 1 (18:36:53) | 29214.859 (3/29/2017 7:37:31 PM): Ignored number of socket network reset errors: 7 (18:36:53) | 29214.875 (3/29/2017 7:37:31 PM): Ignored number of socket network reset...