Plutonium

Misumi'El Here's a quick GSC hot-fix for the flying. The paralyzer slow-mo is still broken, and the flying really only works for the player with the paralzyer. But still works well enough to be used.

1. Add these functions into your GSC file

paralzyer_flying()
{
    self endon("disconnect");
    level endon("end_game");
    
    self.flypower = 100;
    for(;;)
    {
        if(self.flypower < 100 && !isDefined(self.flying))
            self.flypower++;
        if(!isDefined(self.flying) && !self isOnGround())
            self.flying = true;
        else if(self isOnGround())
            self.flying = undefined;
        wait .05;
    }
}

paralzyer_check()
{
    self endon("disconnect");
    level endon("end_game");
    
    for(;;)
    {
        if(self getCurrentWeapon() == "slowgun_zm" || self getCurrentWeapon() == "slowgun_upgraded_zm")
        {
            if(self attackbuttonpressed())
            {
                foreach(player in level.players)
                {
                    if(distance(self.origin, player.origin) < 120 && isDefined(player.flying) && player.flypower > 0)
                    {
                        player.flypower--;
                        if(player getvelocity() [2] < 300)
                            player setvelocity(player getvelocity() + (0,0,41));
                    }
                }
            }
        }
        wait .05;
    }
}

2. Add the 2 function threads into your OnPlayerConnect function (like below)

onPlayerConnect()
{
    for(;;)
    {
        level waittill("connected", player);
        player thread paralzyer_flying(); //Add this line
	player thread paralzyer_check(); //And this line into your GSC
    }
}

shxttered
Read: New Anticheat Ban Policy

Regardless of how the anticheat got triggered, it happened. You're forced to wait unless you want extra time added to your ban time.

Having access to Plutonium isn't a god-given right. If the staff wanted to perma-ban you, they'd have every right to. It's best to just follow the guidelines that are posted by staff members and not act like an entitled kid

Note: Using ANY program to modify the memory within the game causes a ban.
(examples: cheat engine, GSC Injection, Class/Camo changer tool)

Boyd Your issue is covered in the Common Issues and Frequently Asked Questions thread. Solution is in there

moozzy The update for BO2 brought cheat detection.
Using the camo changer triggers the anti-cheat and causes a ban.

Solution: You must wait until your ban time is done.

Note: If you try to make another account, more time will be added as it is considered ban-evasion. (which is what happened already)

Please Read: NEW ANTICHEAT BAN POLICY

Sorex It's only a visual bug. seems unnecessary as it doesn't impact gameplay

MrMcyeet the default pap doesn't have enough textures in order to pull off the pink w115 texture.

The animated camos (cyborg, dragon, afterlife, w115, MOTD pap camo) all have more texture layers than regular camos.

And the regular pap camo is missing those extra textures
(no glow/heat texture)

haloha Known bug. No current fix. This is the closest to a "fix"
Secondary score display

@maraqui2007
It seems like you didn't even read the thread you linked.
A BO1 client already exists
http://getrektby.us/

AdrX003

broken168

healthPlayer()

{
	self endon("disconnect");
	self.healthText = createFontString("Objective" , 2); 
        self.healthText setPoint("CENTER", "BOTTOM", "CENTER", 3.5);
       self.healthText.label = &"^2HP:  ^7";
       while(true)
        {
		self.healthText setValue(self.health);
        wait 0.1;
     	}
}

Try replacing this function. (rewritten to use setValue instead of setText as setText can cause overflows)

leonemv1 Windows 7 is not supported as it is outdated.
Solution: Upgrade to Windows 10

FragsAreUs I ran into that same error when i was first trying out textures and I didn't install any windows service pack to fix it

EDIT: I literally can replicate the error don't @ me

@Zombeeezees It could just be from people leaving and joining frequently.
On console in normal lobbies (even custom games) players couldn't join mid-game like they can on a dedicated server.
Plus, there's at least 2 vanilla crashes that I have personally found on MOTD
(nothing that would happen too often, maybe once a week at most)

Rassel Tomb/Origins (survival maps version) is unfinished
Motd should be stable

Snuckyye DDS to IWI converter also needs to be on your C: drive if I'm not mistaken. Or it could be your file path being too long...
1 of those 2

Rassel If I'm not mistaken the Bonus Survival Maps have an overflow fix on them. Also, what map(s) are crashing?

I've ran the survival maps on a dedicated server for multiple days with no crash on Tranzit
The most recent version of MOTD maps should be stable (but I've never tested thoroughly enough to say for 100%).

And any other maps should be "vanilla" which also shouldn't cause crashes....

Rassel Looks like you're using the Bonus Survival Maps. Maybe try again with the latest release and add your scripts that you want 1 at a time until you can figure out what is causing the crashes.

Julie7688 These scripts are for BO2, not MW3

Rassel Sounds like you don't have an overflow fix inside your scripts. You can easily Google and fine a proper overflow fix with a tutorial

abukhalil WIN 7 not supported. update to WIN 10