Will Xredirect work again?

sammy · **Author**

Hey xOR, the new HLDS update prevents the execution of 'connect' to clients now.

It's going to say "Server tried to send invalid command: connect ____________________" now.

will this be fixed?
sammy

Mordekay · 05-20-2009 , 16:32 Re: Will Xredirect work again?

Ask Valve....

sammy · 05-20-2009 , 18:13 Re: Will Xredirect work again?

Quote:

Originally Posted by Mordekay

Ask Valve....

what a shame. this was my most valuable plugin!

Vet · *Last edited by Vet; 05-21-2009 at 00:37.*

I figured out that you can still force a redirect if the connect command is embedded in a multi-command statement.

raggy · 05-21-2009 , 02:38 Re: Will Xredirect work again?

Quote:

Originally Posted by Vet

I figured out that you can still force a redirect if the connect command is embedded in a multi-command statement.

Using latest xredirect-beta.sma (1.0.4)

changing this on row 1659

PHP Code:


			
client_cmd(id, "connect %s", sFullAddress)

to, for instance

PHP Code:


			
client_cmd(id, "echo Redirecting you to server ip %s;connect %s", sFullAddress, sFullAddress)

works

same needs to be done on line 1776...

Mordekay · 05-21-2009 , 03:53 Re: Will Xredirect work again?

Cool!

xOR · *Last edited by xOR; 05-21-2009 at 06:55.*

thanks for that fast investigation and fix, i will try to let that go into the official version at some time this day.

pretty funny that valve happened to show us once more how extremely sloppy they are working, things will probably never change. that implementation was just as unfinished and crude as the basic idea to block such commands by default. there was like zero complaints about a server being able to execute such commands, so they are "fixing" an issue that doesn't even really exist and raise hundred others at the same time. it reminds me much of the polititcs since 2001 where pseudo-security is established by removing freedom.
if they really need to add that feature, why don't they just ask the client?
"the server tried to execute the following command on your client: <connect> - do you want to allow that command? yes - no"

would still be "secure" but actually give users a chance to decide for themselves.

i think valve will notice that multi command workaround soon and block these too, from that day on xREDIRECT is factually dead. they will probably provide a command (or already have) which can be used by players to unlock these commands again but how do you explain that to the one million players using xREDIRECT manually...or worse...automatically.

to answer the initial topic question of that thread: it will work again with the fix i will provide, but only until valve releases the next update and stops our workaround from working again. from then on we probably won't have any chance to make it work again, only by every client who wants to use it changing a local setting.

Vet · 05-21-2009 , 07:50 Re: Will Xredirect work again?

I suppose they did it because having redirect servers skews their server stats a bit. But they should have never underestimated the resolve and imagination of the Amxmodx scripter.

Screw Valve.

xOR · 05-21-2009 , 09:25 Re: Will Xredirect work again?

Quote:

Originally Posted by Vet

I suppose they did it because having redirect servers skews their server stats a bit.

errm...what?

xOR · *Last edited by xOR; 05-21-2009 at 12:10.*

i released 1.0.3.1 stable which fixes the issue. i am not using multi commands to do that, i just put a simple space character in front of the command. well, i already said something about the diligence with which valve releases their updates.
besides, such changes aren't even mentioned in their update news (and the latest steam update news for Counter Strike within steam are for the version of april 22th or something).