Jump to content

Possible issue for Hardcore servers?

Not a Bug 2.3.4

KingSizeKevin
KingSizeKevin

Posted

I have been racking my brain trying to find the culprit of this error.  What happens is a player is playing fine for a few days, then he logs back in only to get these errors:
 

Quote

Primordial disconnecting: Exception (cs:130930): IndexOutOfRangeException: Index was outside the bounds of the array. BasePlayer.%2f432ae28de444bae52918894455d71a1260d0fe (BaseEntity+%757c3182a9e91503b262d89b8fcd3c9ffb1d21d8 %3db149c11149a37de83cc09e5a35741a3acd94da) (at <00000000000000000000000000000000>:0) BasePlayer.%06e5dd9d97a8285283af40b039a9299e70ef76e0 (BasePlayer %947b64fbeb9366563e9af517b6b098d8aae7c34f, System.UInt32 %28b4baff6009731534c7cf04af9cf2e53cf89f55, %68bbe2b5ef761edef45348d7aaa8de9c7b786f1f %3db149c11149a37de83cc09e5a35741a3acd94da) (at <00000000000000000000000000000000>:0) BaseEntity.%75793a1cf0d74564c7d0000f2471f0d970690285 (System.UInt32 %7432d615fd3d7bb25530281d6e3c955f66c38cf6, %68bbe2b5ef761edef45348d7aaa8de9c7b786f1f %51af613b0258a651fef5ce41cf742960f49ddd51) (at <00000000000000000000000000000000>:0) Client.%c7115bed6f2fc4e23d38be716247fd4c3c4cfcb6 (%68bbe2b5ef761edef45348d7aaa8de9c7b786f1f %4a64e2ab8e361835e1763395e109268ce4557818) (at <00000000000000000000000000000000>:0) Client.%269e089bd13271c548786f79ee0976351d554e99 (%68bbe2b5ef761edef45348d7aaa8de9c7b786f1f %4a64e2ab8e361835e1763395e109268ce4557818) (at <00000000000000000000000000000000>:0) %5b0254d3a7626868bc8529c15229ac755234e613.%3cd330e5b999ce6a5633ed9dec75130508e24fdd (%e32f3bbe7d723f441133b9228dc7a2fb74fa9d3a %4ef91c701b0310fc8cc5c3bedd8c58c7ec15bd90) (at <00000000000000000000000000000000>:0) %001b6b0b81cab7a6523b0abc3e40867c8c6b56dc.%79d34f87640b1d2c7a8e759a38069eab134cea2a () (at <00000000000000000000000000000000>:0) Client.Update () (at <00000000000000000000000000000000>:0) UnityEngine.Debug:LogException(Exception) BasePlayer:%06e5dd9d97a8285283af40b039a9299e70ef76e0(BasePlayer, UInt32, %68bbe2b5ef761edef45348d7aaa8de9c7b786f1f) BaseEntity:%75793a1cf0d74564c7d0000f2471f0d970690285(UInt32, %68bbe2b5ef761edef45348d7aaa8de9c7b786f1f) Client:%c7115bed6f2fc4e23d38be716247fd4c3c4cfcb6(%68bbe2b5ef761edef45348d7aaa8de9c7b786f1f) Client:%269e089bd13271c548786f79ee0976351d554e99(%68bbe2b5ef761edef45348d7aaa8de9c7b786f1f) %5b0254d3a7626868bc8529c15229ac755234e613:%3cd330e5b999ce6a5633ed9dec75130508e24fdd(%e32f3bbe7d723f441133b9228dc7a2fb74fa9d3a) %001b6b0b81cab7a6523b0abc3e40867c8c6b56dc:%79d34f87640b1d2c7a8e759a38069eab134cea2a() Client:Update()

 

If I kill the player in-game, and then they try to rejoin, the error shifts to this:

 

Quote

RPC Error in ReceiveFogOfWarImages: Index was outside the bounds of the array. at BasePlayer.%655e5d83be900064cb780124bc8d1adc64b7e230 (BaseEntity+%43881ca271bc2df20cb4d6bcd47e21366e52f671 %43c93bc914f3150d103554b3fb97a506b5fa7ec2) [0x00000] in <00000000000000000000000000000000>:0 at BasePlayer.%fbba0566ab7a0bd07c472a0faae9c57a63626088 (BasePlayer %41600dde11de3c72944dcefcfc30ede26cad2826, System.UInt32 %e9693808aa47da65b3f203352d5e33cea7cd7f08, %8a44066ca91924f75ac85f3b95c111b8a575da6a %43c93bc914f3150d103554b3fb97a506b5fa7ec2) [0x00000] in <00000000000000000000000000000000>:0 at BaseEntity.%57573d8b75eafe04855c32d611dc0dba0ad69f39 (System.UInt32 %d899a001fcabc4bf2943803b4e0392c0dc13bc61, %8a44066ca91924f75ac85f3b95c111b8a575da6a %6fb0a4ba7f6048403ff34c1573cc776f81f810fa) [0x00000] in <00000000000000000000000000000000>:0 at Client.%8dfe08af9b364388838609a7f8da634046f69dd5 (%8a44066ca91924f75ac85f3b95c111b8a575da6a %c1bd100d4b7932325694d913d6073b6d6cbcb66a) [0x00000] in <00000000000000000000000000000000>:0 at %947456ef1a0a467ca294b1d4004a13b8e256b623.%25c0db1e9c1d19949a2b808077b3e137f265847f (%6e62d84b8d7c1a0b0397aa4707683a0947dae5e0 %f513c48fbe7bb07ffe02d8a26b0b97a08f423351) [0x00000] in <00000000000000000000000000000000>:0 at %859aa2adea0f775ec132ef32475a000dd021b62d.%8426bdfb9ade8ad4bc5a6c97503424bfe50bcdd2 () [0x00000] in <00000000000000000000000000000000>:0 at Client.Update () [0x00000] in <00000000000000000000000000000000>:0


I removed the limit entities plugin, the server had a daily restart, and then the player could re-join the server again.

Am I right that Limit Entities is a possible culprit for this RPC error?

Thank you for your time.

MON@H

Posted

Limit Entities has nothing to do with errors you posted. 

MON@H

Posted

Changed Status from Pending to Not a Bug

KingSizeKevin

Posted

The limit entities plugin is causing this error on hardcore servers. I found another server admin who has the same issues.

I left the plugin removed from my server for 4 months and never had the issue.

I just put the plugin back on this month, and players are getting this error again.

Something with your plugin combined with Facepunch Hardcore mode does something unusual.  

MON@H

Posted

The “ReceiveFogOfWarImages / IndexOutOfRangeException” disconnect is not caused by Limit Entities.

That stack trace is a client-side exception in BasePlayer.ReceiveFogOfWarImages (Hardcore fog-of-war RPC).

Limit Entities does not touch fog-of-war, PlayerState.fogImages, map markers, or any RPC payloads. It only tracks/limits server-side entities (build/deploy) and may deny placement at build time.

On the server, the fog-of-war RPC is sent using the saved PlayerState.fogImages list. If that list is corrupted (not exactly 16 entries), the client can throw IndexOutOfRange and disconnect when it processes ReceiveFogOfWarImages.

So the likely root cause is a corrupted fogImages list in the player’s saved state, or another plugin modifying PlayerState/map/fog-of-war data. Limit Entities is not in that path.

If you still think Limit Entities is involved, please provide a server-side stack trace pointing into LimitEntities.cs, or reproduce on a clean server with only Limit Entities and no other plugins.

2.2m

Downloads

Total number of downloads.

10.1k

Customers

Total customers served.

147k

Files Sold

Total number of files sold.

3.1m

Payments Processed

Total payments processed.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.