NotCracked I doubt that’s the case unless an antivirus program is closing it. If the client itself crashes, it would mostly make an error message pop up, those users are likely just not seeing the error because it appears in the background. If they check %localappdata%\Plutonium\crashdumps, they’ll likely see that some new files have been generated.

To avoid the 0x0054162C error, do the following before joining a server: open the party privacy menu, set the player limit to 1, then set it to the max value (18 for Multiplayer).

To avoid this problem, do the following before joining a server: open the party privacy menu, set the player limit to 1, then set it to the max value (18 for Multiplayer).

Might be caused by certain audio drivers/devices, especially if you have software that controls audio.
Things you could try:

1. Check this:

   if you're running into an issue with your mouse on Bo2 try this.

   Go to the game location (for example mine is "C:\Program Files (x86)\Steam\steamapps\common\Call of Duty Black Ops II")
   Find the exe files t6mp.exe, t6sp.exe, and t6zm.exe. Right-click each one and go to the compatibility tab and change the compatibility mode to: Windows XP (Service Pack 2).

   - by Faeotic

   If one compatibility mode option doesn’t work, try the other options.

2. Unplug/disable all audio devices from both recording and playback devices. Then, check Sound Control Panel and Device Manager for any leftover devices/drivers that haven’t been disabled:

   • Sound Control Panel can be accessed by navigating to Control Panel > Hardware and Sound > Sound. Disable the devices in both Playback and Recording.
   • Check Device Manager for any leftovers and disable them under Audio inputs and outputs and Sound, audio, and game controllers if it’s present.

   If this suggestion fixes the problem, then the cause of the problem is within the devices you have disabled. It could be caused by several devices, or it could be caused by just one. You will have to determine which ones are fine via trial and error.
   One method you could follow to determine which devices are problematic is enabling half of them at a time and seeing if the problem occurs. If the problem occurs, then disable half of the enabled devices which you haven’t yet determined to be not causing the problem, and check again for if the problem occurs. If the problem does not occur, then the current enabled devices are likely safe to be used, and you can move onto testing the other half. Repeat until you’ve tested all devices and have isolated which ones cause the problem.

MrHfwm if you notice your party size not saying (8 Max) at the top, do it.

To avoid this problem, do the following before joining a server: open the party privacy menu, set the player limit to 1, then set it to the max value (8 for Zombies).

If you know the codename of the stat, then yeah, using the following in the console:
statsetbyname <statname> <value>
In your case, you’d use it like this:
statsetbyname pers_max_round_reached 0

CodLan12 change the player limit to 1 then set it to 8 and try joining a server.

IKennyAgain if you mean disabling the entire HUD generated by the script, you could use pers_upgrades_live_tracker_chat_commands.gsc. If you mean disabling specific “<upgrade> awarded:” trackers, currently no, not without disabling the persistent upgrade itself or editing my script.

Update (2024/06/17)

Version 1.2.0 has added toggles to disable trackers of individual updates, not just their detailed trackers.

Before joining a server, open the party privacy menu, change the player limit to 1, then change it again and set it to the max value, which for Zombies is 8.

Edit

Added an additional step.

Mr_Noble54321 supposedly, fast_restart doesn’t properly reset everything. If you want to be safe, use map_restart.

Move plutonium.exe out of your Downloads folder.

__EFK__ your video doesn’t mention why the players appear invisible or why the functions can’t be read in the first place. I recall seeing one of the staff in Discord mentioning that the crash occurs when a corpse spawns. So, I’d imagine the information from your posts and your video are things the devs are already aware of, they just don’t know why it happens in the first place.

I’ve found a reliable way to reproduce the problem, and my clue was my discoveries in this post.

To reiterate from the linked post, players outside of the range of the player’s com_maxclients dvar value appear invisible to the player. The crash seems to occur when an invisible player is killed, but not when visible players are killed. The following video shows the steps I’ve followed to reproduce the crash with bots on a locally hosted server: https://youtu.be/8UffSeXjC8Q
Crashdump files link: https://mega.nz/folder/IxMwjQrT#j-lUr0ojV4GEiV-eDEHruA

IKennyAgain that’s normal because the completion is set to Maxis, and that part is only used for the Maxis side.

IKennyAgain none of the scripts you’re showing are made by me. You also don’t seem to have any mod which makes the Super Easter Egg not require 4 players.

As for some of the parts for the Gallows missing, that’s due to having the completion be set to Maxis. There’s no problem with that.

The Super Easter Egg tracker box shouldn’t be affected much by this bug. Could you show a screenshot of the progress on the super EE tracker box, as well as a screenshot of the list of scripts loaded after starting the map with the mods by searching the external console/terminal window for loaded successfully? Could you also provide a link to where you’ve obtained the solo mods?

NightWatch just opening the party options menu before joining a server and seeing the number at 8 should be enough to avoid the crash. As soon as you open the party options menu, it overrides the values of the max player limit dvars which the menu changes and sets them to whatever is currently shown on the menu. If you see on the lobby screen that it says (4 Max), or the number is set to anything lower than the player limit of the server you’re joining, then you’ll face the crash once an invisible player leaves.

This shows where you can find (# Max):

Edit

To avoid the crash, do the following before joining a server: open the party privacy menu, change the player limit to 1, then change it again and set it to the max value, which for Zombies is 8.

Consider reading the post I linked you when you asked about the problem earlier.

NightWatch refer to this: https://forum.plutonium.pw/topic/35965/t6-zombies-ezz-crashing-when-a-player-times-out/6