Edit: This is a fixed version of PeZBOT mod. Fixes most pain in the ass problems with the PeZBOT mod. Also read the other text files in "Readme" folder so you know how to use this awesome mod ;)
This fix was uploaded to Youtube by pret 132 aka Peditor132. His video adressing this fix: https://www.youtube.com/watch?v=hFWDywHMHH8

NB!!!!!!!!!!!! DO NOT READ THIS README, IT IS ONLY HERE IF YOU WANT TO KNOW WHAT WAS FIXED EXACTLY,!!!!!!!!!!!
NB!!!!!!!!!!!! READ THE PEZBOT README INSTEAD ON HOW TO INSTALL AND USE THE MOD!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
 
NB!!!!!!!!!!!! DO NOT READ THIS README, IT IS ONLY HERE IF YOU WANT TO KNOW WHAT WAS FIXED EXACTLY,!!!!!!!!!!!
NB!!!!!!!!!!!! READ THE PEZBOT README INSTEAD ON HOW TO INSTALL AND USE THE MOD!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
 
NB!!!!!!!!!!!! DO NOT READ THIS README, IT IS ONLY HERE IF YOU WANT TO KNOW WHAT WAS FIXED EXACTLY,!!!!!!!!!!!
NB!!!!!!!!!!!! READ THE PEZBOT README INSTEAD ON HOW TO INSTALL AND USE THE MOD!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
 
NB!!!!!!!!!!!! DO NOT READ THIS README, IT IS ONLY HERE IF YOU WANT TO KNOW WHAT WAS FIXED EXACTLY,!!!!!!!!!!!
NB!!!!!!!!!!!! READ THE PEZBOT README INSTEAD ON HOW TO INSTALL AND USE THE MOD!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
 
NB!!!!!!!!!!!! DO NOT READ THIS README, IT IS ONLY HERE IF YOU WANT TO KNOW WHAT WAS FIXED EXACTLY,!!!!!!!!!!!
NB!!!!!!!!!!!! READ THE PEZBOT README INSTEAD ON HOW TO INSTALL AND USE THE MOD!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
 
NB!!!!!!!!!!!! DO NOT READ THIS README, IT IS ONLY HERE IF YOU WANT TO KNOW WHAT WAS FIXED EXACTLY,!!!!!!!!!!!
NB!!!!!!!!!!!! READ THE PEZBOT README INSTEAD ON HOW TO INSTALL AND USE THE MOD!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
 







In no way am I affiliated with PeZBOT or the PeZBOT-Team.
I’m just an incredible big FAN of this mod and I want to save you some time and energy
because applying these fixes is not without its hassles.

I have included the original “pezbot.iwd” v11p file and the “ATB-fixed” -FIXED one.
(You still need the mod (installed) for the other files of course!) 

-Installation (32bit) (CoD4 steam-version has other directory of course):
Overwrite the “pezbot.iwd” in your
“C:\Program Files\Activision\Call of Duty 4 - Modern Warfare\Mods\PeZBOT” folder
with the “ATB-fixed” one.

-Uninstall (32bit) (CoD4 steam-version has other directory of course):
Overwrite the “pezbot.iwd” in your
“C:\Program Files\Activision\Call of Duty 4 - Modern Warfare\Mods\PeZBOT” folder
with (your backup : )   or... )
the original “pezbot.iwd” v11p I have included in this file! 

I applied the directions of ATB (ex-PeZBOT Team Member) to the letter:
(See the post placed by; ATB Mar 21 2013, 12:21am.) on the summery thread of PeZBOTS:
http://www.moddb.com/mods/pezbot)

-----------------------------------------------------------------
FIX 1
-----------------------------------------------------------------
To fix the teleporting, open the svr\PeZBOT.gsc in a text editor and cut this (lines 1804-1824):
if (getdvar("svr_pezbots_playstyle") == "2")
{
if(randomInt(3) != 0)
{
self.botCrouchObj = 500;
self.botwalkspeed = 6.0;
self.botRunDist = 600;
}
else
{
self.botCrouchObj = 1200;
self.botwalkspeed = 5.5;
self.botRunDist = 2000;
}
}
else
{
self.botCrouchObj = level.botCrouchObj;
self.botwalkspeed = level.botwalkspeed;
self.botRunDist = level.botRunDist;
}
and paste it below this line (before cut 2506, after cut 2485):
self.iShouldCrouch = randomIntRange(0,2);
That should fix it... 

-----------------------------------------------------------------
FIX 2: Sabotage Bomb Glitch 
-----------------------------------------------------------------
When I tested 011p with the warp fix added I didn't get that glitch,
which seemed a bit odd given I'd witnessed it the other day in another 011p variation.
So I've tracked down the "On/Off switch" and it appears to be the console log.
Simply turn it off with: set logfile "0" and no more glitch...

But...

Just in case you are one of those people that plays Sabotage on your own (i.e. no friendly bots)
AND you also want to monitor the console_mp.log, here is a fix:

Line 3028:
tempObjectivePos = self.bestTarget.origin;

Line 3029:
if(isDefined(level.waypoints) && level.waypointCount > 0)

change to

Line 3028:
tempObjectivePos = protectTarget.origin;

Line 3029:
if(isDefined(level.waypoints) && level.waypointCount > 0 && isdefined(self.bestTarget))

(Note: If you have already edited your 011p with a previous alteration/update then the line numbers may be out,
so simply search for "if one of my team members has the bomb, shoot bad guys"
and the lines you are looking for are 6 lines below..).

Have Fun! 

-----------------------------------------------------------------

This solved the 1 round limitation for me, and the sabotage bomb glitch
Now I can play multiple rounds within the same match (ALSO Search & Destroy)!
without the PeZBOTS warping  / teleporting / glitching on me.

Godspeed,

The Errand Boy:
http://youtu.be/OTvmRkMy3UU

: )


