Can't get custom hooks to patch
where can you get the current version of the patcher i tryed adding in some hooks but when i patch it it shows the file was moded i decompile the dll but the hook does not show up   the patcher i have is version 2.0.256 it does show in the patcher log that it added the hook.
It is available on our GitHub, but that won't solve your issue. Make sure you've set the correct path to the files to be patched, and that you are looking in that location.
i set the path correctly in the Rust.opj when i patch it opends to Assembly-CSharp_Original.dll  so its geting the correct location...

so to do this correctly i download the server place in oxide i booted the server once.. closed moved the Oxide.Core.dll to patcher folder i also moved UnityEngine.CoreModule because was complaining when viewing certain sections... edited the opend a section in the assembly clicked hook  viewed the after then patched.



Your patcher view above has all hooks flagged, which means you tried to patch an already patched DLL. Any flagged hook will not be added.
Ts3hosting
i set the path correctly in the Rust.opj when i patch it opends to Assembly-CSharp_Original.dll  so its geting the correct location...

so to do this correctly i download the server place in oxide i booted the server once.. closed moved the Oxide.Core.dll to patcher folder i also moved UnityEngine.CoreModule because was complaining when viewing certain sections... edited the opend a section in the assembly clicked hook  viewed the after then patched.

If you dont noticed that - you are trying to patch:
1. Virtual method that for sure will be overloaded, and if base.OnPointerClick will be not called - your hook will be not called
2. Its part from client-side code, are you sure it will work on server end?

im not sure thats why i was trying to see if the server called it because i would think the server would need to send the icon info somewhere to the client. when they click on it. idn.
Ts3hosting
im not sure thats why i was trying to see if the server called it because i would think the server would need to send the icon info somewhere to the client. when they click on it. idn.

Its not. Server sending you just `Item` or kind of that. Then on client its handeled own way