Rust:IO: Error caught in '/loot.json' handleRequestCached~nextTickFixed
@dcode hello friend, just passing along this console error I'm seeing today after the July update today:

ust:IO> Error caught in '/loot.json' handleRequestCached~nextTick: Field 'StorageContainer.inventory' not found. at b.D+a.A () [0x00005] in <75822f83b7024bdc8e9b7d342222dc6c>:0
Getting this error after game update (and Rust IO update)

(16:18:53) | Rust:IO> Error caught in '/loot.json' handleRequestCached~nextTick: Field 'StorageContainer.inventory' not found.

at b.D+a.A () [0x00005] in <75822f83b7024bdc8e9b7d342222dc6c>:0

(16:47:44) | Oxide.Rust Version: 2.0.4654
No loot showing on map

RustIO v2.17.0'

same error also on my server and just wait
It is the same for me.
@dcode Hope everything is ok with you. Any idea when this issue will be fixed? Im grateful for your work.
same for me
Rust:IO> Error caught in '/loot.json' handleRequestCached~nextTick: Field 'StorageContainer.inventory' not found. at b.D+a.A () [0x00005] in <75822f83b7024bdc8e9b7d342222dc6c>:0
Same for me

Rust:IO> Error caught in '/loot.json' handleRequestCached~nextTick: Field 'StorageContainer.inventory' not found.

Same here.  Rust:IO> Error caught in '/loot.json' handleRequestCached~nextTick: Field 'StorageContainer.inventory' not found. at b.D+a.A () [0x00005] in <75822f83b7024bdc8e9b7d342222dc6c>:0
Hi

Actually I have the error in the console when I connect to rust io via steam
Same here
@dcode Are you able to offer any insight into this?
for my part I have the following error when I connect via steam

18:28:40) | Rust:IO> Error caught in '/loot.json' handleRequestCached~nextTick: Field 'StorageContainer.inventory' not found.

at b.D+a.A () [0x00005] in <75822f83b7024bdc8e9b7d342222dc6c>:0

FYI everyone who is watching this thread:

Rust:IO 2.17.0 auto-updated today from iteration 2.3.7425.2696 to 2.3.7501.33595 when my server restarted and this JSON error seems to now be remedied.

If your server has recently restarted, check today's log (/oxide/logs/oxide_2020-07-16.txt) for:
[Info] Updating Rust:IO ...
[Info] Rust:IO: Update complete
[Info] Rust:IO> Setting up Rust:IO 2.3.7501.33595 ...
If you see this, that should indicate you're good to go. If you still see 2.3.7425.2696 or below, restart your server to trigger the auto-update routine in Rust:IO.
5d11539dc102b.jpg quietconundrum
FYI everyone who is watching this thread:

Rust:IO 2.17.0 auto-updated today from iteration 2.3.7425.2696 to 2.3.7501.33595 when my server restarted and this JSON error seems to now be remedied.

If your server has recently restarted, check today's log (/oxide/logs/oxide_2020-07-16.txt) for:
[Info] Updating Rust:IO ...
[Info] Rust:IO: Update complete
[Info] Rust:IO> Setting up Rust:IO 2.3.7501.33595 ...
If you see this, that should indicate you're good to go. If you still see 2.3.7425.2696 or below, restart your server to trigger the auto-update routine in Rust:IO.

Thanks for that, working as normal now, can you mark it solved :)

Locked automatically