Hi,
I installed Oxide a few weeks ago on our 7DTD server in order for Tebex to run.
Tebex itself appears to be fine but we've had a pesky issue with in-chat command processing.
The issue is that when the /day7 command (used by the ServerTools Mod) is issued, the response comes back "Unknown command: day7".
Note that the response shows day7 (no slash prefix) but the command should have been echoed back with /day7 (with a slash prefix) and then the additional response generated by the command (provided by ServerTools).
In order to get around this, as a workaround, I set the prefix for the ServerTools commands to be # (eg. #day7). That worked for a while but some players are saying that it sometimes works and sometimes doesn't.
Long story short, after much testing by removing every 7DTD Mod on the server, including renaming the Tebex folder to stop their plugin from triggering, I took the plunge and completely uninstalled Oxide, and the problem is gone. ServerTools is now workign exactly as expected, using the slash prefix.
I looked in the SevenDaysCore.json in the Oxide folder tree and in there could see a line with "Unknown command: " in it which raised a flag and prompted me to do the Oxide uninstall process.
Has anyone else had this issue and found a better way round it instead of having to leave Oxide completely uninstalled ? The Tebex plugin will of course no longer run with Oxide not present which hamstrings our operating Tebex.
TIA.

The / is not part of the actual command processing in the game, it is only the prefix. What shows with the message is the actual command, not the prefix. Oxide intercepts all chat commands to handle custom ones, so if there is an issue with a native command not working, then there may be an issue with the handling in Oxide for this game. If that command isn't native and instead from another mod, I'm not sure we can support that if it doesn't follow normal handling.

Thanks for the reply Wulf.
Is there anywhere I can read up on the definition of "normal handling" ?
Is this something defined by The Fun Pimps for how in-game chat is to be handled ?
Seems a bit short-sighted to think that Oxides' allowed to intercept all in-game chat but doesn't want to consider co-existing with several other options out here that have been around for a while, by providing some sort of pass-through so that if what appeared in-chat is not for Oxide it CAN reach it's intended destination and is not actively blocked by Oxide.

Existing commands should be passed along to the game to handle... by intercepting I mean that Oxide would check if the command is a native command or not, and handle it itself if custom.

Thanks for clarifying that.
Is there a means within Oxide to add to the list of what is considered to be the native commands ? or does Oxide have a list supplied by TFP or generated from an unmodded game on which it bases its "native commands" ?

Like I mentioned previously, I'd have to look to see why that command and potentially others are showing as an unknown command.

I didn't want to take for granted that your comments meant you would be taking a look but appreciated. Thanks for that. I'll sit back and be patient :)

Seems to have just been a priorty thing. Allowed mods to process chat before Oxide, which should resolve the issue.

Test build when ready: https://ci.appveyor.com/project/oxidemod/oxide-sevendaystodie/builds/39440583/artifacts

Many thanks Wulf.

Merged post

Confirming, that the test Oxide has been installed on our server and ServerTools is still running exactly as it should, in that the / commands intended for ServerTools are working, and Oxide is not intercepting them. Thanks again Wulf.