Thank you man!
Take this guy's advice and go easy on me. I'm new at this, that's why I put no hate comments.
Did you read his post before or after the edit.
I was about to post the fix. I know where the issue was.
The issues. That we've explained to you. I'll explain it again. This isn't nice. This isn't mean. This is just what you're doing and why it's wrong. You cannot get better unless you understand your mistakes.
You're using a client.cs file. This is intended to be for use as a client only and should contain no code that directly affects a server.
You are declaring a package containing functions that don't already exist. This isn't exactly something that causes it to not work, it's just bad practice to do so.
You are declaring server sided commands in a client.cs file. This means that the server sided commands will only work when hosting a non-dedicated server, with no way for the average player to disable them without deleting the file.
You are calling client sided commands within server sided commands. This means that the server sided commands will only affect the host, no matter who is calling these commands.
You are referencing a variable that is never declared (%client). Typically, the '%client' arg should be declared as the first arg of a serverCmd. e.g. function serverCmdTestFunction(%client){
You are doing a chain of ifs that are completely unnecessary for the most part. When you are only using if, and then if again, there's the chance that multiple of them could be true and that the same function they're all calling will happen multiple times. Instead, you should be using if(condition1 || condition2 || condition3) etc.
You have released a backdoor exploit which allows any player to close a non-dedicated server hosted by a player that has this add-on. It's actually fortunate that this has syntax errors for this reason.
What you're trying to do anyway is functionally unrealisable. If you intended for it to be fully client-sided, then there's no need to have serverCmds or admin checks. Just call the command that the keybind/menu button normally calls. If you intended for this to be a server-sided add-on, then there's no way for you to tell a client to open their options menu, quit, etc, nor should there be, as that would be a reversed exploit.
This next part is mean... When's timescale tweaks coming out?