Repeating warning messages

The image shown what the plugins spamming

This happen when Bradley or Heli kill by player. It never happen before so i connect an AI to my live server to analyze what causing the warning

This what the result is:

 

This warning comes from BradleyDrops, not the UI plugins.

What happened:

Bradley Drop (Easy) fell below the map to about Y = -503.

The plugin spawned reward crates at that invalid position.

Rust destroyed those crates automatically.

Their built-in cratemarker objects were then killed again, producing 29 duplicate-destroy warnings.

The source uses the Bradley’s position without validating it in [BradleyDrops.cs (line 2830)](C:\\Users\\Owner\\Desktop\\RSM\\carbon\\plugins\\BradleyDrops.cs:2830), then spawns crates there at [line 2865 (line 2865)](C:\\Users\\Owner\\Desktop\\RSM\\carbon\\plugins\\BradleyDrops.cs:2865). The Easy profile is configured for four normal crates and one locked crate in [BradleyDrops.json (line 221)](C:\\Users\\Owner\\Desktop\\RSM\\carbon\\configs\\BradleyDrops.json:221).

It is not continuously repeating now and is not a fatal error, but it can cause short lag and will recur if another Bradley falls below the map.

The correct fix is to patch BradleyDrops so it validates the destruction position before spawning rewards, skips below-map drops, and safely clears its tracking data.

Hi, thanks for the report, you're AI report is not entirely accurate.

For starters, my plugin is not responsible for spawning Bradley crates, it merely sets the number of crates to spawn when it dies. The native Rust code spawns the crates.

You are correct, the crates are somehow falling below the map. This is happening depending on where the Bradley is spawned and the terrain around it. Native Rust Bradley only spawns in Launch Site, which is flat terrain. When the Bradley dies the crates spawn without issue on the flat ground.

You are not alone in seeing this happen, although it always used to be rare. In a future update I will take over the spawning of crates so that this cannot happen. It wont be out for a little while, but will be ASAP>

Changed Status from Pending to Work in Progress

Changed Fixed In to Next Version