Missing Mule Kick?

[JordanTheDev]

RedxSkull Thanks, this was the only actually useful response.

[drlamb]

JordanTheDev Were you able to get this to work? As written it doesn't for me.

[drlamb]

Never mind. I just noticed it was active on one of my instances. Thank you!

[drlamb]

Edit 2: So it turns out even with the above script Mule Kick will still fail to show up every time.

I've currently got 7 BO1 instances with 4 of them featuring Kino in their map rotations.

Last night I noticed it working on one but this morning on that same instance (since restarted) it's gone.

My severs are docker images so they're all using the same base with the above script embedded. Mule kick on kino is just buggy.

[drlamb]

To provide additional context: These screenshots are taken 2 days apart on different instances using the same base docker image with a "Activate_Mulekick" gsc script embedded.

[Pistakilla]

drlamb it's a dvar set scr_zm_extra_perk_all 1 you can add this to your server cfg.

[drlamb]

Pistakilla Thank you for this.

I can confirm that option works without the previous GSC script being present in my container images. However, it does NOT work at first if the first map on the server is kino.

Much like the screen shots above show, the first time a server boots (starting at kino) there won't be mule kick. But if the server rotates BACK to kino the mule kick is present.

So it almost seems that this dvar isn't being read/processed on server initialization but is when a server is switching maps.

[Pistakilla]

drlamb Try adding the dvar into a gsc script. The script will always execute.

init(){setDvar("scr_zm_extra_perk_all", 1);}

This line is all you need to execute the dvar. Save it in scripts\sp\zom folder.

[drlamb]

Pistakilla Thank you for that as well but I'm still seeing the same behavior.

Absent on launch, present on the second rotation.

(I've verified the script is present and the variable isn't otherwise set in my server.cfg or launch command arguments)

[Pistakilla]

drlamb Yeah I will have to investigate this further I'll probably come up with a fix soon enough