[4/27/2015 7:43:26 PM] [Oxide] 7:43 PM [Info] [Death Notes v2.4.5] :: <font face="ravie"><i>DassekK trapped into a barricade.
they didnt show Color or smth like this its showing the Code Ingame
-
![[IMG]](proxy.php?image=http%3A%2F%2Fi.epvpimg.com%2FIL6Zc.png&hash=8dee70cf76f8d4c31b49e014095e1c3f)
Attached Files:
-
if you tell me how to do this then yes.....i downloaded the latest so i dont know why its glitched
@SkinN õ.Õ'.|.Last edited by a moderator: Apr 27, 2015 -
It is not planned, but who knows.
-
Wulf Community Admin
-
Thank you and I am aware of that by now, before anything, this is not actually an error but though I must be honest that I don't think it's good either, as it is tagged, should be just an warning.
I actually consider this a Rust issue, not Oxide's nor Death Notes, sort of.
Death Notes uses a small piece of code in the hook OnEntityTakeDamage to figure whether or not the player's last damage was from a fall before bleeding (when wounded), this is more of a work around since the wounded feature is in Rust, because at this point in the game even if you fall from the highest point of the sky you will never actually die of fall damage, you will be wounded and die of bleeding instead (So then Death Notes would trigger the Bleeding message instead of the Fall message). Theoretically this doesn't make much sense of course, why doesn't the player just die once he falls from a a really high altitude and gets wounded instead? So this is kinda what Death Notes is doing, he checks if the previous damage given to the player was fall damage, keeps this information, and uses it later when the player actually dies of bleeding, triggering then the Fall message instead of the bleeding message.
This is not good, I do know that, because LOTS and lots of entities are taking damage every time, so this means Death Notes is running this piece of code every time an entity takes damage, which may cause small lags spikes, but though should not be a big of a deal if your running a server with a map size minor or equal to 4000 and maybe less than 150 players all the time (I guess).
But anyway I might remove this part of the code eventually, at most to avoid people having troubles on their high pop servers.
And as always, thanks for reporting.
P.S Sorry about the large poem, but at least you get to know all the details.
-
Thank you to give me this sight behind the code and this detailed answer.
We only wondered about this message and thought you should know it
Its a great Plugin and we havent any problems with it. But we have only a small and verry new server with less than 50 Players and Slots so its fine even with map size of 6000^^ And the importants thing: Its running all fine even with the message.
