never had any porblems at all. today went to vending to update and the option to edit is gone removed plugin reload all that nothing. 

Which vending machines do you have this issue with? Which monuments? Are the vending machines spawned by a plugin or vanilla?

 vanilla and all of them 2 servers.

Thanks for the info. That eliminates many potential root causes for investigation. In the future, please be even more specific. Instead of "vanilla", say precisely which monuments you tested, such and bandit camp, fishing village, outpost. Without being specific, it's not possible for me tell whether you did the due diligence in testing the various cases; thorough testing of issues often reveals data that can be insightful to the root cause.

Please verify that Monument Finder is working and has accurate bounds for the monuments: go to the monuments in game, stand next to one of the vending machines and run the command "/mf closest". Please verify it says in chat that you are at a monument (not just near one). Preferably share a screenshot of the result.

Please run "o.reload CustomVendingSetup" in the server console and verify that it prints a message that says the plugin was reloaded, shows the latest version of the plugin in that message, and shows no errors. Preferably share a screenshot of the result.

If all of these verifications pass, the only remaining suspect I can think of right now would be other plugins, or Oxide. The Oxide update a few days ago for the force wipe replaced the OnOpenVendingShop hook with OnVendingShopOpened hook. That should be fine, because the Oxide.Rust dll has an intercept for the new hook in order to call the old one for backwards compatibility. What process did you use to update Oxide after the force wipe? If you updated the Assembly-CSharp.dll but did not update the Oxide.Rust.dll, then that would 100% cause this issue. Given the timing of your post, this is most likely the cause. Please check the date modified of the Oxide.Rust.dll you have installed to see if it was created on Thursday. If older than that, update Oxide and the issue should be resolved. If you are not able to update Oxide right now, you can to into the plugin code and replace all occurrences of the word "OnOpenVendingShop" with "OnVendingShopOpened" which will also resolve the issue.

just did everything you said /mf closest said i was at compund 
o.reload CustomVendingSetup . did that first but also removed the plugin and all file 
server and Oxide always up to dat
just did this "OnOpenVendingShop" with "OnVendingShopOpened" which will also resolve the issue. 

last one fixed it my server and oxide are updated always are thx for fix 

Given that renaming the hook resolved your issue, that indicates that whatever process you used to update Oxide is faulty. If you are using the control panel of a server host to update Oxide in some sort of 1-click fashion, that host may be at fault.

That is very concerning because multiple users could be impacted and this could happen again when there is a future Oxide update. I suggest you run o.version in your server console and paste the output here. If that version is older than 2.0.5433, I suggest you send that information to your server host to investigate why they are installing Oxide incompletely.

WoW thank you for all the info super nice of you to take the time. > o.version
Server is running Oxide 2.0.5437 Rust 337 (2332.223.1)

If you report this issue to your server host, they will ask for some kind of evidence. I was hoping the version number would be sufficient, since it looks to be a part of the Oxide.Rust dll at a glance, but that version is sufficiently new, so it's not evidence of the problem. At this point, feel free to report it and simply point to this thread. I can try to provide more info if needed.

so you are saying the oxide is not updating right on the server side

SouthernGaming2X

so you are saying the oxide is not updating right on the server side

Correct. The Assembly-CSharp.dll that Oxide provides now calls the OnVendingShopOpened hook rather than OnOpenVendingShop. The Oxide.Rust.dll intercepts the new hook and calls the old one for backwards compatibility, allowing plugins to use either hook. Given that renaming the hook in the plugin to the new name worked, we can deduce that Assembly-CSharp.dll is up to date on your server since it is emitting the new hook (also, if it wasn't up to date, players likely wouldn't even be able to connect). Given that the old name no longer works on your server (works on mine though), that means the Oxide.Rust.dll which is supposed to call the old hook, is not calling it, which probably means that the Oxide.Rust.dll is out of date somehow.

When you download Oxide, it will provide a bundle with both dlls (and many others). My only guess is that whatever was responsible for copying those dlls over to your server didn't copy all of them.

very good sent this to host.