Login

**PoosKi** · 16-06-2017/05:59 PM

(16-06-2017/05:54 PM)Forgotten Wrote: PoosKi care to explain?

I don't know the specifics, he just said he couldn't mute seen because it said he was already muted (according to PoosKi), I checked if he was and he wasn't, I tried muting him myself and it worked, I unmuted him then PoosKi muted him just fine afterwards. PoosKi will have to explain more.

Can confirm

effectively what happened is when I went to mute someone it said that they were already muted, but I could hear them loud and clear when they spoke. This has happened twice to me now. I called Forgotten on and he tried and it worked. No idea why.

**Sir Lagalot** · 16-06-2017/06:08 PM

Although it was probably changed on purpose you can no longer target players in self mute using @all, @ct, @t, etc. If this wasn't changed on purpose then I would appreciate being able to !sm @all again Tongue

**Byte** · 19-06-2017/10:07 PM

(16-06-2017/06:08 PM)Sir Lagalot Wrote: Although it was probably changed on purpose you can no longer target players in self mute using @all, @ct, @t, etc. If this wasn't changed on purpose then I would appreciate being able to !sm @all again

Sir Lagalot

Are you sure?
I just tested on 1v1 and it worked fine for me.
Checked the code and the targeting is done with server permissions (ignores immunity).

Can you try again? Should be sm_sm @all in console.
If it doesn't work, what do you get? An error response? Nothing?

**Sir Lagalot** · 19-06-2017/10:27 PM

Byte I just tested it again and it gives me the error message: "This command is blocked."

**Byte** · 20-06-2017/07:47 AM

(19-06-2017/10:27 PM)Sir Lagalot Wrote: Byte I just tested it again and it gives me the error message: "This command is blocked."

Found the issue.
Seemed to only be affecting Combat Surf.
Please confirm its fixed now.

Crona · 21-06-2017/07:03 AM

Byte I think the user was using a form of cheat or something because I could't lock onto his name even using the #"number" thing

**Byte** · 21-06-2017/07:15 AM

Sir Lagalot Did you try the thingy?

(21-06-2017/07:03 AM)Crona Wrote: Byte I think the user was using a form of cheat or something because I could't lock onto his name even using the #"number" thing

Hmm that sounds odd.
The # method should work for everybody though regardless of name.

Crona · 21-06-2017/07:24 AM

Byte yeah I wasn't sure if the text of his name wasn't the real text so I used that method but it also didn't work and when I asked him about he just laughed, I've been trying to research if it is possible to avoid the targeting system but could't find anything

**Sir Lagalot** · 21-06-2017/06:29 PM

Byte I tried it again on both 1v1 and surf and it came up with the same message of "This command is blocked."

**Byte** · 22-06-2017/04:58 AM

(21-06-2017/06:29 PM)Sir Lagalot Wrote: Byte I tried it again on both 1v1 and surf and it came up with the same message of "This command is blocked."

Okay I think I actually fixed it this time.
Can you please do a test on 1v1 and surf again?

Login
Username:
Password:	Lost Password?
	Remember me