[BBG_Theory]

@ AlphaBlaster, does your admin_overrides.cfg look like this?

Overrides
{
 /**
  * By default, commands are registered with three pieces of information:
  * 1)Command Name   (for example, "csdm_enable")
  * 2)Command Group Name (for example, "CSDM")
  * 3)Command Level  (for example, "changemap")
  *
  * You can override the default flags assigned to individual commands or command groups in this way.
  * To override a group, use the "@" character before the name.  Example:
  * Examples:
  *  "@CSDM"   "b"    // Override the CSDM group to 'b' flag
  *   "csdm_enable" "bgi"   // Override the csdm_enable command to 'bgi' flags
  *
  * Note that for overrides, order is important.  In the above example, csdm_enable overwrites
  * any setting that csdm_enable previously had.
  *
  * You can make a command completely public by using an empty flag string.
  */
 "mvm_redblu_set_access"        "" 
  
}

overwrite and restart server?

[AlphaBlaster]

Originally Posted by BBG_Theory @ AlphaBlaster, does your admin_overrides.cfg look like this? Overrides { /** * By default, commands are registered with three pieces of information: * 1)Command Name (for example, "csdm_enable") * 2)Command Group Name (for example, "CSDM") * 3)Command Level (for example, "changemap") * * You can override the default flags assigned to individual commands or command groups in this way. * To override a group, use the "@" character before the name. Example: * Examples: * "@CSDM" "b" // Override the CSDM group to 'b' flag * "csdm_enable" "bgi" // Override the csdm_enable command to 'bgi' flags * * Note that for overrides, order is important. In the above example, csdm_enable overwrites * any setting that csdm_enable previously had. * * You can make a command completely public by using an empty flag string. */ "mvm_redblu_set_access" "" } overwrite and restart server?

Holy crap I thought it had to go underneath all that. Thank you.

[BBG_Theory]

@AlphaBlaster

a simplified one would be this

Overrides
{ 
  "mvm_redblu_set_access"        ""
}

but that would have tossed away the comments that show you various examples

[Benoist3012]

Originally Posted by AlphaBlaster Is there any way to get rid of the robot footsteps? The biggest turnoff for people who join are the footsteps because they're either too loud or for some reason they're convinced they're playing on the robot team and think it's one of those dumb servers that lets you play on the robot side.

Each server can let player play in blu, if they want a plugin for that they aren't "dumb" like you said, I'm the 2nd dev of Tf2bwr, and this sound who is played to player who are in "blu" is created by the gamemode mvm it's impossible to disable this sound I tried before it's impossible (or maybe there is a way but I think not).

[sigsegv__]

Based on looking at CTFPlayer::GetOverrideStepSound, I think it might be possible to disable to robot footstep sound.

If the client believes that the local player is a miniboss, then it won't override the footstep sound with "MvM.BotStep". But I don't know if making the server lie to the client about whether it's a miniboss would break other things, so this is probably a bit of a long shot.

That function also checks InCond(3) and won't override the footsteps in that case as well. But again, it's probably pretty unlikely that you'd be able to lie to the client about its condition state without having other side effects.

[BatyaMedic]

Originally Posted by sigsegv__ Based on looking at CTFPlayer::GetOverrideStepSound, I think it might be possible to disable to robot footstep sound. If the client believes that the local player is a miniboss, then it won't override the footstep sound with "MvM.BotStep". But I don't know if making the server lie to the client about whether it's a miniboss would break other things, so this is probably a bit of a long shot. That function also checks InCond(3) and won't override the footsteps in that case as well. But again, it's probably pretty unlikely that you'd be able to lie to the client about its condition state without having other side effects.

Can you test it?

[Michalplyoutube]

Setting miniboss and giving attribute 330 of value 1 should fix the problem

however the person with miniboss on blue team on mvm is immune to stun factors but not to the stun itself

[Oshizu]

Originally Posted by Michalplyoutube Setting miniboss and giving attribute 330 of value 1 should fix the problem however the person with miniboss on blue team on mvm is immune to stun factors but not to the stun itself

Rather than changing actual miniboss netprop using sendproxying to send clients false netprop could work

[Benoist3012]

Originally Posted by Oshizu Rather than changing actual miniboss netprop using sendproxying to send clients false netprop could work

Agree

[FlaminSarge]

That might work. Anybody wanna test?