Players spawning in the sky and dying from fall damage

Are any one of u having this issue on your servers?
It starter after the last update...

 

I was using 8000, then got 7000 and the problem was solved 'til 1~2weeks ago. Tried to use 6000 and now its fine.

The issue happened with buildings that couldn't be built like the stability wasn't working as normal and the players started to spawn in the sky.

 

Hi,

first of all, THIS IS NOT AN OXIDE ISSUE, AND I'M NOT BLAMING OXIDE AT ALL...

Since the last update, when I first opened the server (still no Oxide build), I tried 4 different (manually inserted) seed/size combination, and EVERYBODY from the very start, spawned very high in the air, fallen and dead.

Then I tried just with the manual size (7071 for ≈50skm of world size), and IT WORKED WELL!! (or so I thought), I was very excited, as the Oxide build just came up, and I was the first spanish server updated (got almost 150 people playing, from my ≈50 daily average). It all went nice for about 2 hours, and then doors started failing (instabroken, or broken after a few minutes), a bit later it affected construction in general, and a bit later, THE "FLYING SPAWN" STARTED HAPPENING AGAIN... Connected people dropped to 70-80 in less than 20 minutes, and I restarted the server. It went nice for 5 minutes, and it all is happening again.

I understand, that at least the "flying" issue is Rust-related (not Oxide or its plugins at all), the other issues, we'll see...

I have many plugins, but not in excess (m-Godmode, playerlocation, playerlist, m-Compass, give, helptext, finder, m-Godmode, m-Time, 0-FriendsAPI, admin-door-unlocker, authlevel, Logger, kits, Cleanup, GatherRate, Polling, suicide, RustDB, spectatePlayer, suicide, Updater, Warp-system, and USUALLY enabled, but disabled right now: chathandler, EnhancedBanSystem, r-AntiCheat and r-AntiWallhack). All totally up-to-date (of course, for some/most of them the "last" update is older than the last Rust update)


Anyone has a solution, even a "least bad" option?
[DOUBLEPOST=1423524735][/DOUBLEPOST]

Why are you asking about having a world size over 6000? Do you know something useful? I don't have programming knowledge, but am an amateur sysadmin that loves to read about a lot of things, I think I will understand if you explain what you think would be happening

 

We belive the issue only manifest itself when the world size is larger than 6000

 

But is it experimentally gathered information, or do you have any theory on WHY it happens (don't get the caps in the wrong way ;D).

 

people without oxide also reported those problems

 

It started happening again, with a world size under 6000 (not by far: 5916x5916). I was kind of afraid of this because when I made the 7000x7000 world , it happened after some time of playing, rather than from the start like when I made the 8000x8000 world.

I guess it will always happen, given enough time (the smaller, the more time it takes).

 

Ya I had it start on a world size of 5500