Search results

Interesting. How would the proper MainThreadID look like?

Yes a little more: [5/15/2016 3:31:08 PM] [Error] Error for Taryn System.NullReferenceException: Object reference not set to an instance of an object at Fougerite.Loom.QueueOnMainThread (System.Action action, Single time) [0x00000] in <filename unknown>:0 at Fougerite.Loom.QueueOnMainThread...

[5/15/2016 3:18:01 PM] [Error] [Fougerite Loom Error] System.NullReferenceException: Object reference not set to an instance of an object at Fougerite.Loom.QueueOnMainThread (System.Action action, Single time) [0x00000] in <filename unknown>:0

Teleporting can sometimes cause a Facepunch Violation Kick when your pc is slow or is laggy, thats why Dizzy gets triggered.

I would also suggest to not start the Dizzy Check /Timer when Owner of the Building equals the Player, because some seem to get Dizzy warnings when TPing back to their base, or after returning from the HungerGames.

[5/15/2016 1:44:00 PM] [Error] [Fougerite Loom Error] System.NullReferenceException: Object reference not set to an instance of an object at Fougerite.Loom.QueueOnMainThread (System.Action action, Single time) [0x00000] in <filename unknown>:0

Hmm maybe its because I'm calling Player.Disconnect from a thread and not by System.Timers? Or is EAC also using threading? I will test the nightly build.

public void Disconnect() { if (this.IsOnline) { //Logger.LogError("Same? " + Thread.CurrentThread.ManagedThreadId + " - " + Bootstrap.CurrentThread.ManagedThreadId); if (Thread.CurrentThread.ManagedThreadId != Bootstrap.CurrentThread.ManagedThreadId) { //Logger.LogError("Nope, invoking")...

I'm using inside a thread the pl.Disconnect() function since you mentioned in the wiki that Loom is automatically called at this method. Basically like: public void PlayerConnect(Player pl) { Thread t1 = new Thread(() => GeoInit(pl)); t1.Start(); } public void GeoInit(Player...

Getting this error: [Console] System.NullReferenceException: Object reference not set to an instance of an object at Fougerite.Loom.QueueOnMainThread (System.Action action, Single time) [0x00000] in <filename unknown>:0 at Fougerite.Loom.QueueOnMainThread (System.Action action) [0x00000] in...

Yes, will test it :)

tarynkelley submitted a new resource: Rust Legacy Server + Fougerite - Rust Legacy Server with Fougerite 1.4.2 Prepatched Read more about this resource...

Yes, but its too big :D Upload a File (Max 19.5 MB):

I made you fresh rust server package with already patched Fougerite 1.4.2. So you only need to install the plugins and start. Try any of these download mirrors: https://www.dropbox.com/s/6wt1rj9y9ryl7uy/rust_server_142.7z?dl=1...

What Fougerite version are you using?

I mentioned this problem at the beginning of the year already. http://fougerite.com/threads/rust-legacy-server-files-download-corrupt.823/ I contacted the Rust Support under http://support.facepunchstudios.com/ several times and got the answer they won't fix it because rust legacy is not more...

For me also only for player console commands like suicide.

I see that this plugin is still using System.Timers.Timer? Therfore I guess its still might crash the server? Or did you solve this problem?

I can really recommend to use only a Dedicated Server. Most VPS/VDS have a very bad CPU . 1 vCore CPU does not equal 1 Physical CPU core. What is your budget? Rust Legacy server only runs on 1 Core / thread that means you should have a CPU with good single threading performance. Keep in mind...

Its working perfect. Thanks a lot