Plutonium

Bots ARE working but you need to initialize the bot system. This means that the bot configuration needs to be loaded. Xerxes can tell you more about it.

@SilverEagle1776 maybe

ninja636 said in Cheats who toggle uav hacks:

Rektinator if your anticheat works better than steams how come when they put it on its not picked up?

For one thing, Steam BO2 anti-cheat does nothing, it bans literally no one. Our anti-cheat detects all public hacks for BO2. If the user in question made his own cheat, then it might be possible that our anti-cheat does not pick it up yet. It could also be that the user is simply not cheating, but the server you played on is using a shitty mod which gives him an advantage. For that we need you to supply the proof. If we think the user in question is cheating, we will ban the user from the game and he will not be able to play on Plutonium ever again.

Detecting cheats is a cat-and-mouse game, if a user finds a new way to cheat, we will have to update our code to detect it. The user gets banned. A new user finds a way to cheat, we detect it, the user gets banned, and so on.

Besides that, server owners can always manually ban a player if they think the user is cheating. That way the problem can be countered too.

Like I said, we try our best to stop cheaters as much as possible, and I think we have done a really good job so far, especially compared to Steam BO2.

Finally, you have to understand that this is also a hobby project for us. We have our jobs in real-life which take up most of our time, I spend a lot of my free time every day to make Plutonium better.

TheYellowApple Please type net_port in your dedicated server. Are you connecting to localhost? If so, you probably did not specify the correct port in order to connect to the server.

Also, remove the serverkey you generated and generate a new one, because you posted your keys by accident. The screenshots are removed for the same reason.

GaryCraft In case you missed my reply on discord:

The actual error is displayed in your log file: "Unable to load binary into memory"
This is an error from Plutonium, it means it couldn't locate the game binaries.

This is caused by the fact that your working directory is wrong.

Set your working directory to /home/container/T6_Server/Plutonium
Then run wine bin/plutonium-bootstrapper-win32.exe t6mp /home/container/T6_Server/Server -dedicated +start_map_rotate +set key insertkey +set net_port 25559 +set sv_config dedicated.cfg

This should fix the problem.

@SilverEagle1776 Not sure what you're trying to say with that. We won't allow people to play the actual campaign on any of the SP games. If that's the goal, you can simply buy the game. That's our standpoint on supporting SP games.

Sounds like you tried to report a cheater in-game. The servers on Plutonium are not owned by us, we just make the client itself. Since the release of Plutonium, we have banned a total of 2318 users for cheating. These are all automated bans by the anti-cheat. On average, the anti-cheat bans about 30-40 cheaters per day.

If you think someone is hacking in-game, please make a report thread on the forum. We can't see reports you make in-game.

We're always working on improving the anti-cheat. If a new public hack pops up, we try to get it detected as soon as possible. Currently we are not aware of any public cheats that work on either MW3 or BO2.

Plaincard53 this is caused by incorrect cg_fov / cg_fov_default values, try setting both cg_fov and cg_fov_default to 65. Then adjust the dvars again to your likings. Your gun will be visible again.

sv_cheats 1 can be enabled by servers or while in a private match (with the map command from the private match menu). If its enabled on a server, everyone in that server will be able to use cheat commands.

Title doesn't say much actually

Thank you! We appreciate it a lot!

Bongo777 said in Zombies private lobby issue:

So I'm trying to play co-op zombies with my friends but we cannot connect to more than get more than 2 people to connect to the same lobby. Any ideas?

We are aware of the problem. A solution is coming soon.

We're working on a fix for scripting related bugs.

Shiver Yeah, I think it might be an issue on the latest update of Steam MW3 (which we are using). If thats the case, I will have to figure out what exactly is going wrong. Com_maxfps is also broken in this version of MW3.

Your claims do not match with the logs on the backend.

On Oct 16, 2020 @ 11:27 (the actual time might be different due to timezones.) you logged in to the game
You started playing a Private Match on T6 Zombies.
Few minutes later you injected something in your game, in the private match. This caused you to get banned.

This ban cannot be caused by anyone else. The IP address matches the range of your login history on the forum.

@GlitchesHD We need a console log and steps to reproduce this / a video in order to see whats going on. Just this screenshot is not helpful for resolving the issue.

toga Make sure you run the latest version on your dedicated server (r622 is the current version), it should resolve most of these issues.

No idea, try fullscreen / windowed mode. Try if you can reproduce the same on steam. Is com_maxfps set to 0?

Matty76 said in Banned While at Work? continuation! continuation!:

Could i atleast supply some evidence to support my case.

Best Regaurds

Matt

Go ahead, but consider your ban permanent if it turns out to be fake / inconsistent / whatever.

@Joan-OwO Emailed It's been reported and we currently have a task open to look into it.