admin eye

Hey Qbis,

I’ve noticed an issue with your Admin Eye plugin — it doesn’t seem to log every action properly.

In the example I’m attaching in the screenshots, you can see that one player killed another at 20:57, but this event doesn’t appear at all in Admin Eye’s logs.

It’s a bit annoying because that specific death at that exact time is the one I really needed to review.

Could you please take a look at this? Maybe it’s missing some kill or death events in certain situations.

Thanks a lot for your time and for your work on the plugin!

Hey

There is no error on my part, the plugin takes the UTC time (it can only be wrong if the time on the server is not configured correctly). 
There can be several reasons for the discrepancy
Like the fact that the time on the server and the time in discord are different. 
And also the message in discord could have arrived later (some failures in ds)
Discord also combines recent messages. 

But one thing I can say for sure, the plugin works correctly and it is used by quite a few administrators. The code in terms of "time" has not changed for a long time. And also if this was someone else, then I would have known a long time ago. If suddenly this error will appear in a couple of users, then I will deal
So far I can only advise to know if the time is set correctly on the server (not the game). Does not combine discord. Do messages come without delay

Hey,

Thanks for your answer. The server time is correctly configured, and I’m receiving Discord messages instantly — there’s no delay or issue with that part.

However, if you look closely at the screenshots I attached, even if there’s a small time offset, the death itself isn’t recorded in Admin Eye.

You can clearly see that the positions and the hits don’t match, meaning this specific death event is completely missing from the Admin Eye logs.

That’s why I’m sure it’s not just a timing issue — it’s really a missing death record.

Could you please check that part again?

Unfortunately, I was unable to reproduce this error, and all types of logs are being recorded correctly.

So we can’t do anything about it then? I just don’t want this to happen again, because the main reason I bought this plugin was to monitor these kinds of situations. Since it didn’t record properly this time, I can’t review what happened. Anyway, thank you for your reply and for taking the time to check it.