Search results

No problems here at all. Can you give us a plugin list? I'm having a feeling you are having something that is making your server sorta blew. We need all info we could get. Logs, screenshots, and you could even enable hooksspeed in the Fougerite.cfg to see if a plugin is actually causing the...

I did.

DreTaX updated DeathMSG with a new update entry: 1.1 Read the rest of this update entry...

Renamed BodyPart.ini to Bodies.ini to fix the reading error.

Doesn't have anything to do with ChangeOwner You are using /instakoall on a deployable object. That can only be used for structures. This will be fixed in 1.5.6

Can you show me your config?

You could have requested this, it doesnt matter if it has rustbuster or not.

No changes regards the foundation, but the player thing might be.

Something is null in the deathmsg plugin.

You are not giving us proofs at all buddy, sadly.

Uncoding is impossible, @xandeturf already gave me a notice what's wrong. Only smart people would think about It, but fix is on the way. :) If he gets HWID banned, there is no help 4 him tho.

EAC has protection for that, but I doubt 1.5.5 has to do anything with the wall loot or glitch. Wall loot was never possible, after a rust update.

Because you didnt update your assembly.

I will push out one more to fix those that salva reported.

Hooo. Alright,gonna test soon.

What did you use to remove them?

Damn. I will do something later, that if you dont have admin rights, it will skip the pinging. Anyway. Try this - turn UAC off (move the slider to "Never Notify") - log off and log on again to your administrative account. - Click "Start", type "cmd" into the search box BUT DON'T HIT ENTER -...

@McRustReloaded @salva @xandeturf Even better. I tested this fully with python plugin calls. Everything seems to be perfect. I changed NPCHurt, NPCKiled, PlayerHurt, EntityHurt, EntityDestroyed to the takedamage event hook, and that one method processes all of them. This should save a lot of...

@McRustReloaded This seems fine