Wulf
That isn't what is causing it most likely, earlier in the log would be a better indication: CommunityEntity = Rust's CUI (community UI/custom UI)
New Oxide update fixed the issue?
Wulf
That isn't what is causing it most likely, earlier in the log would be a better indication: CommunityEntity = Rust's CUI (community UI/custom UI)
New Oxide update fixed the issue?
Can someone can confirmed that error is fixed with this new update ?
Merged poststill that same + this error:
HttpRequestException: 502 (Bad Gateway) System.Net.Http.HttpResponseMessage.EnsureSuccessStatusCode () (at <00000000000000000000000000000000>:0) ConVar.Chat+MuteList.get_IsGlobalMuted () (at <00000000000000000000000000000000>:0) System.Xml.Serialization.XmlSerializationFixupCallback.Invoke (System.Object fixup) (at <00000000000000000000000000000000>:0) System.Threading.ExecutionContext.RunInternal (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) (at <00000000000000000000000000000000>:0) System.Runtime.CompilerServices.AsyncMethodBuilderCore+MoveNextRunner.Run () (at <00000000000000000000000000000000>:0) System.Action.Invoke () (at <00000000000000000000000000000000>:0) System.Xml.Serialization.XmlSerializationFixupCallback.Invoke (System.Object fixup) (at <00000000000000000000000000000000>:0) UnityEngine.WaitUntil.get_keepWaiting () (at <00000000000000000000000000000000>:0) UnityEngine.UnitySynchronizationContext.Exec () (at <00000000000000000000000000000000>:0) --- End of stack trace from previous location where exception was thrown --- System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () (at <00000000000000000000000000000000>:0) System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) (at <00000000000000000000000000000000>:0) System.Runtime.CompilerServices.ConditionalWeakTable`2[TKey,TValue]..ctor () (at <00000000000000000000000000000000>:0) CommunityEntity+<LoadTextureFromWWW>d__16.System.Collections.IEnumerator.Reset () (at <00000000000000000000000000000000>:0) System.Xml.Serialization.XmlSerializationFixupCallback.Invoke (System.Object fixup) (at <00000000000000000000000000000000>:0) System.Threading.ExecutionContext.RunInternal (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) (at <00000000000000000000000000000000>:0) System.Runtime.CompilerServices.AsyncMethodBuilder you always say this :P and then you fix it in few minutes in update :DWulf
The only updates that Oxide has provided were for the IL/RPC error and kick. This doesn't appear to be an Oxide issue.