MissingFieldException: Field 'ItemDefinition.displayName' not foundNot An Issue
(12:31:01) | Failed to call hook 'OnEntityDeath' on plugin 'Stats v1.2.6752' (MissingFieldException: Field 'ItemDefinition.displayName' not found.)
at Oxide.Core.Plugins.CSPlugin.OnCallHook (System.String name, System.Object[] args) [0x000fb] in <4452f821def6406d834e4149849fe7ea>:0
at Oxide.Core.Plugins.Plugin.CallHook (System.String hook, System.Object[] args) [0x00060] in <4452f821def6406d834e4149849fe7ea>:0
Sounds like you did not update Rust before Oxide.
Alright after updating rust again and updating umod, it seems to have stopped, thanks wulf, i could of sworn that i had updated it before updating umod.

Merged post

Yea i knew i had updated rust and umod correctly, im still getting.

(13:04:36) | Failed to call hook 'OnEntityDeath' on plugin 'Stats v1.2.6752' (MissingFieldException: Field 'ItemDefinition.displayName' not found.)

at Oxide.Core.Plugins.CSPlugin.OnCallHook (System.String name, System.Object[] args) [0x000fb] in <4452f821def6406d834e4149849fe7ea>:0

at Oxide.Core.Plugins.Plugin.CallHook (System.String hook, System.Object[] args) [0x00060] in <4452f821def6406d834e4149849fe7ea>:0

That would only show if not updated fully and are mixing Rust versions.
Weird, not sure how its not fully updated or i would be mixing Rust versions, ill try re-updating it again, and see what happens.

Merged post

Alright well is still spamming that and im pretty sure ive updated it to the latest version correctly, because ive been doing the updating the same way for over 3 years now, old version of oxide didn't do that only the latest oxide protocol update started spamming it.
5b6cd206b1b0e.jpg Pur3x
Weird, not sure how its not fully updated or i would be mixing Rust versions, ill try re-updating it again, and see what happens.

Merged post

Alright well is still spamming that and im pretty sure ive updated it to the latest version correctly, because ive been doing the updating the same way for over 3 years now, old version of oxide didn't do that only the latest oxide protocol update started spamming it.
The error doesn't really have anything to do with Oxide, the missing field is provided by Rust and the error means that something is trying to look for it but can't find it as the file where it is supposed to be doesn't exist... because the Rust files are mixed/old/etc.

Stop the server, update with Steam (with validate option), start the server, check the version, stop the server, install the latest Oxide build found on the Games page, start the server, check the version again, compare the versions and the build.
Locked automatically