Search results

  1. DreTaX

    Fougerite Official

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

    Fougerite Official

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

    RB Fog

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

    RB Fog

    I was talking about the screenshot not the code :p
  5. DreTaX

    Fougerite Official

    Thats probably a 1.5.6 pre release bug. Will fix.
  6. DreTaX

    Fougerite Official

    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
  7. DreTaX

    Fougerite Official

    @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.
  8. DreTaX

    Fougerite Official

    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...
  9. DreTaX

    RB Fog

    @salva might wanna do a show off?
  10. DreTaX

    Fougerite Official

    @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...
  11. DreTaX

    Fougerite Official

    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.
  12. DreTaX

    Fougerite Official

    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...
  13. DreTaX

    Fougerite Official

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

    Fougerite Official

    @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...
  15. DreTaX

    Fougerite Official

    No problems here at all. Can you give us a plugin list? I'm having a feeling you are having something that is making your server sorta blew. We need all info we could get. Logs, screenshots, and you could even enable hooksspeed in the Fougerite.cfg to see if a plugin is actually causing the...
  16. DreTaX

    Fougerite Official

    I did.
  17. DreTaX

    Approved DeathMSG

    DreTaX updated DeathMSG with a new update entry: 1.1 Read the rest of this update entry...
  18. DreTaX

    DeathMSG - 1.1

    Renamed BodyPart.ini to Bodies.ini to fix the reading error.
  19. DreTaX

    Approved ChangeOwner

    Doesn't have anything to do with ChangeOwner You are using /instakoall on a deployable object. That can only be used for structures. This will be fixed in 1.5.6
  20. DreTaX

    Approved DeathMSG

    Can you show me your config?