Fcvar_server_can_execute - Developers

You can't be serious. I can no longer use the 'say' command when working with a modified chatbox? Has anyone got a fix?

My custom chatbox is working just fine. It's weird because all my other mods like motd broke because of this issue.

did u update your server and game a 2nd time?

Garry did a hotfix, so update and check if its update 67.

[QUOTE=Disseminate;16248176]You can't be serious. I can no longer use the 'say' command when working with a modified chatbox? Has anyone got a fix?[/QUOTE] Are you one of those idiots on TnB? They use a chat box that sends a command to the server to send the say command to the client. That isn't garry's fault, it's your awful code.

[QUOTE=AzuiSleet;16249088]Are you one of those idiots on TnB? They use a chat box that sends a command to the server to send the say command to the client. That isn't garry's fault, it's your awful code.[/QUOTE] What? That's a long winded solution to an invisible problem right there.

[QUOTE=conman420;16249140]What? That's a long winded solution to an invisible problem right there.[/QUOTE] that sentence makes 0 sense

[QUOTE=AzuiSleet;16249088]Are you one of those idiots on TnB? They use a chat box that sends a command to the server to send the say command to the client. That isn't garry's fault, it's your awful code.[/QUOTE] No, it's Rick Darkaliono's awful coding. I've PMed you the fix, Disseminate

garry blocked the ability to run commands on players. ulx cexec is broken also

[QUOTE=mcd1992;16249362]garry blocked the ability to run commands on players. ulx cexec is broken also[/QUOTE] That was the entire point.

To bad it's easy as hell to get around.

There's no way around it, you don't know what you're talking about.

[QUOTE=blackops7799;16250275]To bad it's easy as hell to get around.[/QUOTE] Proof or it didn't happen.

AzuiSleet what was the point of blocking it anyway, i can understand it from adminges but what about legit scripts like stopsounds for all players if something bugs up or changing a users model or tool mode or something for them if they don't know how to?

So the server can't bind the client's keys to shit

Wasn't that already blocked anyway? Now we just have a fuck ton more of commands we can't use on the client. Why don't you just get rid of player.ConCommand() next?

You don't need to be running :ConCommands on commands that don't have FCVAR_SERVER_CAN_EXECUTE. There's no reason you need to concommand say. If you want to stopsounds, send a umsg or sendlua game.CleanUpMap(). findflags server_can_execute [code] "cl_playermodel" = "kleiner" ( def. "none" ) client archive server_can_execute - Default Player Model "gmod_toolmode" = "leafblower" ( def. "rope" ) server_can_execute clientcmd_can_execute [/code]

But why block it? Oh no, I can make you say things. No need to get all butthurt and block it.

Everything that doesn't have fcvar_server_can_execute is blocked, it's a whitelist not a blacklist.

custom chat boxes are for shit lords. Using FCVAR_SERVER_CAN_EXECUTE prevents all sorts of problems with so-called "viruses" that everyone whines about

[code]ba_cexec blackops "mat_texture_limit 1" [BAdmin] Admin BlackOps ran "mat_texture_limit 1" on player BlackOps! FCVAR_SERVER_CAN_EXECUTE prevented server running command: mat_texture_limit ba_cexec_test blackops "mat_texture_limit 1" [BAdmin] Admin BlackOps ran "mat_texture_limit 1" on player BlackOps [/code] My test command worked just fine.. So much for me not knowing anything..

If you really need to run say or any other friendly commands on a player.. [code]ply:SendLua([[LocalPlayer():ConCommand("say Hi")]])[/code] Or use usermessages like Azu suggested.

[QUOTE=blackops7799;16251851][code]ba_cexec blackops "mat_texture_limit 1" [BAdmin] Admin BlackOps ran "mat_texture_limit 1" on player BlackOps! FCVAR_SERVER_CAN_EXECUTE prevented server running command: mat_texture_limit ba_cexec_test blackops "mat_texture_limit 1" [BAdmin] Admin BlackOps ran "mat_texture_limit 1" on player BlackOps [/code] My test command worked just fine.. So much for me not knowing anything..[/QUOTE] Doesn't show much. I can do the same thing by copying and pasting, then doctoring it. Code is what we're looking for, son.

Hah, if you don't believe me come into my server. I'll make your screen black for you. It's the most simple thing in the world..

[QUOTE=blackops7799;16252004]Hah, if you don't believe me come into my server. I'll make your screen black for you. It's the most simple thing in the world..[/QUOTE] so is that, sendlua a black panel SetSize(ScrW(),ScrH())

Yeah, because adding a black panel across your screen fucks up your console text. :rolleyes:

[QUOTE=blackops7799;16252115]Yeah, because adding a black panel across your screen fucks up your console text. :rolleyes:[/QUOTE] touche

All you're doing is sending RunConsoleCommand to the client. That's not a bypass. The reason this exists is so you can't run bind on a player. The whitelist exists on the client, and there are blocks on the client from running bind.

Alright, suppose I was dumb for not thinking of usermessages or SendLua. Bring on the boxes.

[QUOTE=AzuiSleet;16252695]All you're doing is sending RunConsoleCommand to the client. That's not a bypass. The reason this exists is so you can't run bind on a player. The whitelist exists on the client, and there are blocks on the client from running bind.[/QUOTE] If the server wants to rebind your keys it should have a window pop up showing all proposed changes (maybe even letting you tweak them) and then have you hit OK or something. I get requests from players to have some sort of automated binder all the time. All I'm seeing from this change is that people are going to be using a lot more "ply:SendLua([[LocalPlayer():ConCommand("say Hi")]])" vs the old way, using slightly more bandwidth than before with no real change. I guess people who were using custom modules to try infect players will have a harder time, but watching infected players cry was one of my favorite pastimes.