BZFlag Cheat

Delayed Death after Getting Shot

2008-01-06T22:16:00.000-08:00

By: Lord Jesus

This cheat comes to us by way of an idea from blogger, person. Here is an excerpt of his comment to Super "Kill Me" on Demand in which he proposed the idea:

I have a suggestion... Maybe there could be a client side delay so that when the tank detects that it has been shot, it will let you live for just a little longer, giving you a short time in which you could kill your killer before you died. Like for example. I get in a fight with a shock waver. I wait for him to land, but am hit before he lands. Instead of exploding, I would have 2 seconds to kill him first.

The delayed death cheat can also be useful for cheaters with slow connections and/or moderate to high lag since the delay can possibly be attributed to lag. Some administrators, though, may kick players who lag or seem to lag until they are able to fix the problem especially if other players are complaining about it.

Being that I'm not a software developer, this may look a bit rough; however, it works. Suggestions to clean it up or to make it easier are always welcome.

Anyway, I found in my experiments that setting the delay to 2.0f seemed a little long. It would be easily noticed, and you would be singled out shortly for cheating. In this example, I use 1.0f which turns out to be a little closer to two seconds than it does one. You can adjust that value to suit your liking. Perhaps, you can shorten it to make it less noticeable yet still give you just enough time to pop off a shot or two at the player who shot you. Additionally, my idea was to have a countdown on the display. Being that the time is short, I decided to go simply with "Death imminent" as a quick warning for you to get your shot(s) off before you blow up.

I didn't include a delay for Thief. The idea is to shoot a person who actually shot you. I also didn't include a delay for Steamroller; however, implementing a delay for that as well wouldn't be difficult.

All of the changes that we will make will be in the file, playing.cxx.

At the beginning, of playing.cxx, you will see a section for "system includes":


// system includes
#ifdef _WIN32
#include 
#include 
#include 
#include 
#else
#include 
#include 
#include 
#include 
#include 
#endif
#include

At the end of that, add "int deathStart;" so that the section now reads like this:


// system includes
#ifdef _WIN32
#include 
#include 
#include 
#include 
#else
#include 
#include 
#include 
#include 
#include 
#endif
#include 
int deathStart;

Next, search for "destructCountdown" and you will find these lines:


float   pauseCountdown = 0.0f;
float   destructCountdown = 0.0f

Just below the "destructCountdown" line, add this new line:


float   deathCountdown = 0.0f;

The lines should now read like this:


float   pauseCountdown = 0.0f;
float   destructCountdown = 0.0f;
float   deathCountdown = 0.0f;

Search for "destructCountdown" again, and you will find this section:


static void  updateDestructCountdown(float dt)
{
  if (!myTank) {
    destructCountdown = 0.0f;
  }
  if (destructCountdown > 0.0f && !myTank->isAlive()) {
    destructCountdown = 0.0f;
    hud->setAlert(1, NULL, 0.0f, true);
  }
  if (destructCountdown > 0.0f) {
    const int oldDestructCountdown = (int)(destructCountdown + 0.99f);
    destructCountdown -= dt;
    if (destructCountdown <= 0.0f) {
      // now actually destruct
      gotBlowedUp( myTank, SelfDestruct, myTank->getId() );

      hud->setAlert(1, NULL, 0.0f, true);
    } else if ((int)(destructCountdown + 0.99f) != oldDestructCountdown) {
      // update countdown alert
      char msgBuf[40];
      sprintf(msgBuf, "Self Destructing in %d", (int)(destructCountdown + 0.99f));
      hud->setAlert(1, msgBuf, 1.0f, false);
    }
  }
  return;
}

Below that, add these lines:


static void  updateDeathCountdown(float dt)
{
  if (!myTank) {
    deathCountdown = 0.0f;
  }
  if (deathCountdown > 0.0f && !myTank->isAlive()) {
    deathCountdown = 0.0f;
    hud->setAlert(1, NULL, 0.0f, true);
  }
  if (deathCountdown > 0.0f) {
    const int oldDeathCountdown = (int)(deathCountdown + 0.99f);
    deathCountdown -= dt;
    if (deathCountdown <= 0.0f) {
      // blow up my tank and then reset
      // deathCountdown & deathStart back to zero
      gotBlowedUp(myTank,GotShot,deathStart);
      deathCountdown = 0.0f;
      deathStart = 0;

      hud->setAlert(1, NULL, 0.0f, true);
    } else if ((int)(deathCountdown + 0.99f) != oldDeathCountdown) {
      // update countdown alert
      char msgBuf[40];
      sprintf(msgBuf, "Death imminent");
      hud->setAlert(1, msgBuf, 1.0f, false);
    }
  }
  return;
}

Search for "destructCountdown" one more time, and you will find this section:


    // update the countdowns
    updatePauseCountdown(dt);
    updateDestructCountdown(dt);

Below that, add "updateDeathCountdown(dt);" so that the section now reads like this:


    // update the countdowns
    updatePauseCountdown(dt);
    updateDestructCountdown(dt);
    updateDeathCountdown(dt);

Now, search for "used later", and you will find this section:


  // used later
  float waterLevel = World::getWorld()->getWaterLevel();

  if (hit) {
    // i got shot!  terminate the shot that hit me and blow up.
    // force shot to terminate locally immediately (no server round trip);
    // this is to ensure that we don't get shot again by the same shot
    // after dropping our shield flag.
    if (hit->isStoppedByHit())
      serverLink->sendEndShot(hit->getPlayer(), hit->getShotId(), 1);

    FlagType* killerFlag = hit->getFlag();
    bool stopShot;

    if (killerFlag == Flags::Thief) {
      if (myTank->getFlag() != Flags::Null) {
 serverLink->sendTransferFlag(myTank->getId(), hit->getPlayer());
      }
      stopShot = true;
    }
    else {
      stopShot = gotBlowedUp(myTank, GotShot, hit->getPlayer(), hit);
    }

    if (stopShot || hit->isStoppedByHit()) {
      Player* hitter = lookupPlayer(hit->getPlayer());
      if (hitter) hitter->endShot(hit->getShotId());
    }
  }
  // if not dead yet, see if i'm sitting on death

Just after the comments at the beginning of the "if (hit)" section, add these lines:


    // skip this if the Death Counter is counting
    if (deathCountdown > 0.0f) return;

The section should now read like this:


  if (hit) {
    // i got shot!  terminate the shot that hit me and blow up.
    // force shot to terminate locally immediately (no server round trip);
    // this is to ensure that we don't get shot again by the same shot
    // after dropping our shield flag.

    // skip this if the Death Counter is counting
    if (deathCountdown > 0.0f) return;

Next, notice these lines in particular in the "if (hit)" section:


    else {
      stopShot = gotBlowedUp(myTank, GotShot, hit->getPlayer(), hit);
    }

Replace "stopShot = gotBlowedUp(myTank, GotShot, hit->getPlayer(), hit);" with these lines:


      deathCountdown = 1.0f;
      deathStart = hit->getPlayer();

      // imminent death alert
      char msgBuf[40];
      sprintf(msgBuf, "Death imminent");
      hud->setAlert(1, msgBuf, 1.0f, false);

The section should now read like this:


    else {
      deathCountdown = 1.0f;
      deathStart = hit->getPlayer();

      // imminent death alert
      char msgBuf[40];
      sprintf(msgBuf, "Death imminent");
      hud->setAlert(1, msgBuf, 1.0f, false);
    }

The entire section after your changes should now look like this:


  // used later
  float waterLevel = World::getWorld()->getWaterLevel();

  if (hit) {
    // i got shot!  terminate the shot that hit me and blow up.
    // force shot to terminate locally immediately (no server round trip);
    // this is to ensure that we don't get shot again by the same shot
    // after dropping our shield flag.

    // skip this if the Death Counter is counting
    if (deathCountdown > 0.0f) return;

    if (hit->isStoppedByHit())
      serverLink->sendEndShot(hit->getPlayer(), hit->getShotId(), 1);

    FlagType* killerFlag = hit->getFlag();
    bool stopShot;

    if (killerFlag == Flags::Thief) {
      if (myTank->getFlag() != Flags::Null) {
 serverLink->sendTransferFlag(myTank->getId(), hit->getPlayer());
      }
      stopShot = true;
    }
    else {
      deathCountdown = 1.0f;
      deathStart = hit->getPlayer();

      // imminent death alert
      char msgBuf[40];
      sprintf(msgBuf, "Death imminent");
      hud->setAlert(1, msgBuf, 1.0f, false);
    }

    if (stopShot || hit->isStoppedByHit()) {
      Player* hitter = lookupPlayer(hit->getPlayer());
      if (hitter) hitter->endShot(hit->getShotId());
    }
  }
  // if not dead yet, see if i'm sitting on death

I realize that the HUD alert is redundant. I noticed that there was a delay in the alert so I added it in the above section, as well, so that it would display more quickly.

What we've established so far is the creation of a couple of values, deathCountdown and deathStart, which we will use for our countdown, and we set their defaults (e.g., deathCountdown = 0.0f). We also added the the code for the actual countdown and time keeping. Next, we initiate the countdown when we get shot by setting deathCountdown to 1.0f, and we display an alert for "Death imminent". We also retain the identity of the player who initially shot us and started the countdown by setting the value of deathStart to represent the identity of that player so that we can use it later for blowing up when the countdown completes. We skip the "if (hit)" section if there is already a countdown in progress so that we don't start a new countdown for each shot that hits us once a countdown has already started (i.e., we ignore all other shots that may hit us after the countdown begins). When the countdown finishes, we blow up (and as a result lose a point, and the killer gets his or her point), and the countdown values, deathCountdown and deathStart, are then set back to 0.0f and 0, respectively.

Notice that we use "return" to skip the "if (hit)" section. We do that since using a line such as "stopShot = true" when deathCountdown > 0.0f will get us kicked for wrong end shot detections. Essentially, the server will kick us if we are ending other players' shots that hit us without our tank blowing up. That technique of avoiding getting blown up was utilized by cheaters of yore, and it was known as end shot cheating. I know that because I, myself, used to be one of the culprits long ago. Anyway, it is better to ignore a shot altogether rather than try to end it without blowing up. That's why god mode cheating works and end shot cheating no longer does.

This next part is left over from when I was experimenting with a previous revision of this cheat. The idea was to bypass blowing up until a countdown had finished. It may not be necessary (I haven't tried it without it); but, this cheat works with it in place. So, if it ain't broke, don't fix it :P If anyone wants to experiment with it, let us know how it worked.

Search for "tank && (tank->getTeam() == ObserverTeam" and you will find this section:


static bool  gotBlowedUp(BaseLocalPlayer* tank,
        BlowedUpReason reason,
        PlayerId killer,
        const ShotPath* hit, int phydrv)
{
  if (tank && (tank->getTeam() == ObserverTeam || !tank->isAlive()))
    return false;

Change "(tank && (tank->getTeam() == ObserverTeam || !tank->isAlive()))" to this:


((tank && (tank->getTeam() == ObserverTeam || !tank->isAlive()) || deathCountdown > 0.0f))

Yeah, I know it's "fugly". Anyway, the section should now read like this:


static bool  gotBlowedUp(BaseLocalPlayer* tank,
        BlowedUpReason reason,
        PlayerId killer,
        const ShotPath* hit, int phydrv)
{
  if ((tank && (tank->getTeam() == ObserverTeam || !tank->isAlive()) || deathCountdown > 0.0f))
    return false;

Save the file, compile your new client, and you're finished. Thank you to blogger, person, for bringing this idea to us.

As always...

Have fun!

>:)

**********

Related posts:

Instant Self Destruct
Ultimate Pausing

Using God Mode with Choose Who Kills You

2008-01-03T15:13:00.000-08:00

By: Lord Jesus

With Choose Who Kills You and Super "Kill Me" on Demand, you could not use god mode if you had either or both cheats enabled. Here's a simple edit that will now allow you to have the best of both worlds. You can drive around in god mode and only blow up when you initiate killMe (Choose Who Kills You) or SuperkillMe (Super "Kill Me" on Demand). I was considering making this an additional update to Super "Kill Me" on Demand; however, I decided to make it a separate entry for the benefit of those who choose not to use god mode.

First, let's revisit Classic God Mode. In the God Mode cheat, we added this line in several locations within playing.cxx:


      // skip this if i'm alive
      if (myTank->isAlive()) return;

So that it will not interfere with killMe and/or SuperkillMe, we change it to this:


      // skip this if i'm alive and we have not initiated getting killed
      if (myTank->isAlive() && killMe == 0 && SuperkillMe == 0) return;

If you do not use both dead-on-demand cheats, you can edit the above to match which cheat you are using. Basically, we skip the check to see if we should be dead if we are alive AND killMe and SuperkillMe are zero (i.e., we haven't selected to be killed by someone). If we have initiated a "Kill Me", then we continue with the checks and we are allowed to blow up.

When you've completed your edits, save your file, compile your client, and ...

Have fun!

**********

Related posts:

Classic God Mode
Choose Who Kills You
Super "Kill Me" on Demand

Jump Fix for DUB Pillbox

2008-01-03T04:55:00.001-08:00

By: Lord Jesus

Some of you may have noticed that you can no longer cheat on DUB Pillbox by jumping on the no-jumping server (see Flying Without Wings for information about jumping on no-jump servers). In addition to updating to a newer version server which prevents sending flags to teammates (or someone on the other team, for that matter) or observers, jump velocity was set to zero. The fix for that is to use a custom value if the server value is set to zero or less. Here, we use 19. You can experiment to find a value that most suits your liking.

To do that, let's go to LocalPlayer.cxx. Search for "newVelocity[2] = BZDB.eval(StateDatabase::BZDB_JUMPVELOCITY)", and you will find this section:


  // add jump velocity (actually, set the vertical component since you
  // can only jump if resting on something)
  const float* oldVelocity = getVelocity();
  float newVelocity[3];
  newVelocity[0] = oldVelocity[0];
  newVelocity[1] = oldVelocity[1];
  if (flag == Flags::Wings) {
    newVelocity[2] = BZDB.eval(StateDatabase::BZDB_WINGSJUMPVELOCITY);
  } else if (flag == Flags::Bouncy) {
    const float factor = 0.25f + ((float)bzfrand() * 0.75f);
    newVelocity[2] = factor * BZDB.eval(StateDatabase::BZDB_JUMPVELOCITY);
  }  else {
    newVelocity[2] = BZDB.eval(StateDatabase::BZDB_JUMPVELOCITY);
  }

In particular, look at these lines:


  }  else {
     newVelocity[2] = BZDB.eval(StateDatabase::BZDB_JUMPVELOCITY);
  }

Just below "} else {", add this line:


if(BZDB.eval(StateDatabase::BZDB_JUMPVELOCITY) <=0 ) BZDB.setFloat(StateDatabase::BZDB_JUMPVELOCITY, 19);

The edited section should now read like this:


  }  else {
     if(BZDB.eval(StateDatabase::BZDB_JUMPVELOCITY) <=0 ) BZDB.setFloat(StateDatabase::BZDB_JUMPVELOCITY, 19);
     newVelocity[2] = BZDB.eval(StateDatabase::BZDB_JUMPVELOCITY);
  }

Save the file, compile your client, and you're ready once more to raise hell on DUB Pillbox. Yes, now you can start dropping flags on towers again. For added laughs, be sure to check out Flying Without Wings and Guided Bullets ;) Also be sure to check out Teleport Behind Somebody (handy when someone on the other team has your flag).

I wouldn't be surprised if DUB Pillbox and/or other servers tweak various other server values in attempts to thwart cheating. We'll update here as necessary, so stay tuned ;)

Again...

dj28: "Have fun pissing people off and ruining their fun."

>:)

**********

Related posts:

Wings Gravity Fix for BloodBath
Flying Without Wings
Guided Bullets
Teleport Behind Somebody
Teleport in FRONT of your opponent.

Super "Kill Me" on Demand

2008-01-01T13:37:00.000-08:00

By: Lord Jesus

Got an annoying teammate that needs to be kicked (if the server kicks for team kills)? Perhaps that annoying teammate simply needs calibration with a point reduction... Or, how would you like to be able to hook up your buddies with some mad points?

Here's a modification to Choose Who Kills You brought to you by a collaboration between blogger,Someone, and BZFlag Cheat's newest team member, NightMare.

With "Choose Who Kills You", you enter in your command to be killed by another player on demand (e.g., "/k"). The getting killed ends after you blow up and the point is transferred. Let's say, though, that you would like to do it over and over again without having to enter the command manually each and every time. One way might be to set up a macro such as ctrl+k to enter "." + /k + [Enter] to facilitate rapid keystroke entries. Another way might be to set up a key command and select victims similar to the way in which one uses "k" to silence or "unsilence" other players. There are a variety of ways which are possible. After all, there are usually more than one way to skin a cat, as the old saying goes.

The technique that we will use here is to set up a command for it. A separate command is used to terminate the automatic suicide, as it were. Additionally, this particular method works separately from killMe, so you can use either one without conflict. The example that we use here will show lines of code for both. The single killMe is optional, of course, but highly recommended :)

Before we begin, let's review some limitations. This method described here (as well as single killMe) will NOT work if you:

UPDATE

Using God Mode with Choose Who Kills You

Respawn Instantly

Additionally, I have noticed that commonly at least one player on a server is not affected by either killMe or Super killMe. So, if you go to try it out and it doesn't work on the first victim, try some others just to be sure. Also, if a victim leaves the server during the automatic Super killMe (e.g., getting kicked for team killing, just simply leaving, and so on), then the killed message will reflect that you have been killed by the server. This occurs when you are killed by an unknown player (a player who has signed off is a player that no longer exists).

playing.cxx

Let's begin now by going back to playing.cxx. Do you remember where we added "int killMe"? Let's add another one so that the section looks like this (from the beginning of the file):


/* bzflag
 * Copyright (c) 1993 - 2006 Tim Riker
 *
 * This package is free software;  you can redistribute it and/or
 * modify it under the terms of the license found in the file
 * named COPYING that should have accompanied this file.
 *
 * THIS PACKAGE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR
 * IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED
 * WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
 */

// interface header
#include "playing.h"

// system includes
#ifdef _WIN32
#include 
#include 
#include 
#include 
#else
#include 
#include 
#include 
#include 
#include 
#endif
#include 
int killMe;
int SuperkillMe;

Next, search for "used later", and you will find this section:


  // used later
  float waterLevel = World::getWorld()->getWaterLevel();

  if (hit) {
    // i got shot!  terminate the shot that hit me and blow up.

Look at the second line:


  float waterLevel = World::getWorld()->getWaterLevel();

Below that, let's add our lines of code:


  if (killMe)
  {
  gotBlowedUp(myTank,GotShot,killMe);
  killMe = 0;
  }

  if (SuperkillMe)
  {
  gotBlowedUp(myTank,GotShot,SuperkillMe);
  }

Look at the line below the addition above:


if (message.length() > 0) {

Add "else" at teh beginning of the line so that it now reads like this:


else if (message.length() > 0) {

The edited section should now look like this:


  // used later
  float waterLevel = World::getWorld()->getWaterLevel();

  if (killMe)
  {
  gotBlowedUp(myTank,GotShot,killMe);
  killMe = 0;
  }

  if (SuperkillMe)
  {
  gotBlowedUp(myTank,GotShot,SuperkillMe);
  }
 else if (message.length() > 0) {
  
  if (hit) {
    // i got shot!  terminate the shot that hit me and blow up.

Notice that in the killMe section you see "killMe=0" but SuperkillMe does not have a corresponding line. The line resets killMe so that the process of getting blown up doesn't keep going and going. This allows you to have single use killMe. Since we want the automatic killMe (i.e., SuperkillMe) to keep going, there is no line resetting that value back to 0.

UPDATE: As mentioned previously, this cheat would continue the SuperkillMe even after the player signs off or gets kicked. Thus, the killer is then unknown and the killed message is "Killed by the server", and you would have to use your command to end it (such as /ks) to stop the SuperkillMe. Here's a simple fix to end the SuperkillMe automatically when the player no longer on the server.

Let's continue with playing.cxx and search for "Killed by the server". You will will find this section:


    } else {
      // 1-4 are messages sent when the player dies because of someone else
      if (reason >= GotShot && reason <= GenocideEffect) {
        Player *killerPlayer = lookupPlayer(killer);
        if (!killerPlayer) {
          blowedUpNotice = "Killed by the server";
        } else {

Notice this line: blowedUpNotice = "Killed by the server";

After that line, add this line:


          SuperkillMe = 0;

The section should now look like this:


    } else {
      // 1-4 are messages sent when the player dies because of someone else
      if (reason >= GotShot && reason <= GenocideEffect) {
        Player *killerPlayer = lookupPlayer(killer);
        if (!killerPlayer) {
          blowedUpNotice = "Killed by the server";
          SuperkillMe = 0;
        } else {

At this point, we are finished with editing playing.cxx.

ComposeDefaultKey.cxx

Next, let's go to setting up the actual commands. For this we go to ComposeDefaultKey.cxx. Do you recall where we put "extern int killMe;"? Search for "MAX_MESSAGE_HISTORY (20)", and you will come to this section:


#define MAX_MESSAGE_HISTORY (20)

MessageQueue messageHistory;
unsigned int messageHistoryIndex = 0;


static bool isWordCompletion(const BzfKeyEvent& key)

Notice the line "unsigned int messageHistoryIndex = 0;". Below that, we will add our lines of code:


extern int killMe;
extern int SuperkillMe;

The edited section should look like this:


#define MAX_MESSAGE_HISTORY (20)

MessageQueue messageHistory;
unsigned int messageHistoryIndex = 0;
extern int killMe;
extern int SuperkillMe;

static bool isWordCompletion(const BzfKeyEvent& key)

Next, let's set up our commands. Here, we use "/k" for a single killMe, and we use "/kk" for SuperkillMe. Keep in mind that you are free to use any command that you desire. For example, if you prefer /killme over /k, then edit that line accordingly. Search for "if (sendIt) {", and you will see this section:


  if (sendIt) {
    std::string message = hud->getComposeString();
    if (message.length() > 0) {
      const char* cmd = message.c_str();
      if (LocalCommand::execute(cmd)) {
        ;
      } else if (serverLink) {

Notice the line "std::string message = hud->getComposeString();". Below that, we will add our lines of code:


    if(message=="/kk") {
       const Player *someOther = LocalPlayer::getMyTank()->getRecipient();
       if (someOther)
       {
 SuperkillMe = someOther->getId();
       }
     }

    else if(message=="/ks") {
 SuperkillMe = 0;
     }

    else if(message=="/k") {
       const Player *Other = LocalPlayer::getMyTank()->getRecipient();
       if(Other)
       {
 killMe = Other->getId();
       }
     }

The next line after our addition is "if (message.length() > 0) {". Let's add "else" in front of that so that the line now reads like this:


    else if (message.length() > 0) {

The section after our change should now read like this:


  if (sendIt) {
    std::string message = hud->getComposeString();

    if(message=="/kk") {
       const Player *someOther = LocalPlayer::getMyTank()->getRecipient();
       if (someOther)
       {
 SuperkillMe = someOther->getId();
       }
     }

    else if(message=="/ks") {
 SuperkillMe = 0;
     }

    else if(message=="/k") {
       const Player *Other = LocalPlayer::getMyTank()->getRecipient();
       if(Other)
       {
 killMe = Other->getId();
       }
     }

    else if (message.length() > 0) {
      const char* cmd = message.c_str();
      if (LocalCommand::execute(cmd)) {
        ;
      } else if (serverLink) {
 char messageBuffer[MessageLen];

In the example above, we used "/ks" as the command to terminate the automatic getting killed on demand, or SuperkillMe. When we enter the command "/ks", SuperkillMe is set to 0, and automatic getting killed is over until we initiate it again.

After you make your changes, save your files, compile your new client, and you're done. Watching dead or paused players rack up points or team kills can be quite amusing... as well as observers going on killing sprees :P

In the immortal words of dj28:

"Have fun pissing people off and ruining their fun."

>:)

**********

Related posts:

Choose Who Kills You
Using God Mode with Choose Who Kills You

Guided Bullets

2007-12-31T00:24:00.001-08:00

Ok this code is pretty nice, just lock onto your opponent and it shoots in the direction they're going or right at them pretty accurately. I didn't create this code, but I'm not sure who gave it to me but here it is:

You might have trouble if you have guided lasers.

In src/bzflag/playing.cxx find:

// see if it's inside lock-on angle (if we're trying to lock-on)
if (a <>getFlag() == Flags::GuidedMissile) // am i locking on?
tankHasShotType(myTank, Flags::GuidedMissile)) &&
player[i]->getFlag() != Flags::Stealth && // can't lock on stealth
!player[i]->isPaused() && // can't lock on paused
!player[i]->isNotResponding() && // can't lock on not responding
d < besttarget =" player[i];" bestdistance =" d;" lockedon =" true;">getFlag() == Flags::GuidedMissile) // am i locking on?

To:

(1 // am i locking on?

In src/bzflag/LocalPlayer.cxx find:

// Set _shotsKeepVerticalVelocity on the server if you want shots
// to have the same vertical velocity as the tank when fired.
// keeping shots moving horizontally makes the game more playable.
firingInfo.shot.vel[2] = 0.0f;

Add this after it:

if (getTarget()) {
const Player * targ = getTarget();
double myx = LocalPlayer::getMyTank()->getPosition()[0];
double myy = LocalPlayer::getMyTank()->getPosition()[1];
double myz = LocalPlayer::getMyTank()->getPosition()[2] +
LocalPlayer::getMyTank()->getMuzzleHeight();
double hisx = targ->getPosition()[0];
double hisy = targ->getPosition()[1];
double hisz = targ->getPosition()[2] + targ->getMuzzleHeight();
double hisvx = targ->getVelocity()[0];
double hisvy = targ->getVelocity()[1];
double hisvz = targ->getVelocity()[2];
double deltax = hisx - myx;
double deltay = hisy - myy;
double distance = hypotf(deltax,deltay)- BZDBCache::tankRadius;
// - BZDB.eval(StateDatabase::BZDB_MUZZLEFRONT);
if (distance <= 0) distance = 0; double shotspeed = BZDB.eval(StateDatabase::BZDB_SHOTSPEED)*( LocalPlayer::getMyTank()->getFlag() == Flags::Laser ?
BZDB.eval(StateDatabase::BZDB_LASERADVEL) :
LocalPlayer::getMyTank()->getFlag() == Flags::RapidFire ?
BZDB.eval(StateDatabase::BZDB_RFIREADVEL) :
LocalPlayer::getMyTank()->getFlag() == Flags::MachineGun ?
BZDB.eval(StateDatabase::BZDB_MGUNADVEL) : 1);
double errdistance = 1.0;
float tx, ty, tz;
for (int tries=0 ; errdistance > 0.05 && tries < t =" (float)distance" omega="fabs(targ-">getAngularVelocity());
double sx,sy;
if ((targ->getStatus() & PlayerState::Falling) fabs(omega)
< sx="t*hisvx;" sy="t*hisvy;" hisspeed =" hypotf(hisvx," alfa =" omega" r =" hisspeed" dx =" r" dy2 =" r" beta =" atan2(dy2,">getAngularVelocity() >
0 ? 1 : -1);
double gamma = atan2(hisvy, hisvx);
double rho = gamma+beta;
sx = hisspeed * t * cos(rho);
sy = hisspeed * t * sin(rho);
}
tx=(float)hisx+(float)sx;
ty=(float)hisy+(float)sy;
tz=(float)hisz+(float)hisvz*t;
if (targ->getStatus() & PlayerState::Falling)
tz += 0.5f * BZDBCache::gravity * t * t;
if (tz < 0) tz = 0;
double distance2 = hypotf(tx - myx, ty - myy);
errdistance = fabs(distance2-distance) / (distance + ZERO_TOLERANCE);
distance = distance2;
}
float projpos[3];
projpos[0] = tx; projpos[1] = ty; projpos[2] = tz;
float heading = atan2f(projpos[1] - myy, projpos[0] - myx);
firingInfo.shot.vel[0] = cosf(heading) *
BZDB.eval(StateDatabase::BZDB_SHOTSPEED);
firingInfo.shot.vel[1] = sinf(heading) *
BZDB.eval(StateDatabase::BZDB_SHOTSPEED);
firingInfo.shot.vel[2] = sinf(atan2f(projpos[2]-myz,
hypotf(projpos[1]-myy,
projpos[0]-myx)))*BZDB.eval(StateDatabase::BZDB_SHOTSPEED);
firingInfo.shot.pos[0] = myx;
firingInfo.shot.pos[1] = myy;
firingInfo.shot.pos[2] = myz;
}

There you go.

-NightMare

Choose your tank size

2007-12-31T00:16:00.000-08:00

Ok this is posted in a comment by "person" but "someone" is the one who came up with this cheat I just think it should be posted so more people can see it and don't have to go looking through comments to find it so here it is.

At top of src/bzflag/CommandsImplementation.cxx:

extern float sizeCheat;
class SizeCommand : LocalCommand {
public:
SizeCommand();
bool operator() (const char *commandLine);
};
static SizeCommand sizeCommand;
SizeCommand::SizeCommand() : LocalCommand("/size") {}
bool SizeCommand::operator() (const char *commandLine)
{
sizeCheat = atof(commandLine+6);
return true;
}

At top of src/bzflag/Player.cxx:

#include "LocalPlayer.h"
float sizeCheat = 1.0f;
Find:
else if (effectFlag == Flags::Narrow) {
dimensionsTarget[1] = 0.001f;
}

Add this after:

if (id == LocalPlayer::getMyTank()->getId())
{
dimensionsTarget[0] *= sizeCheat;
dimensionsTarget[1] *= sizeCheat;
}

And that should be it. Now just type /size .1 to /size 1. You must either be killed or pick up or drop a flag for the size to change. Sizes range from 0.0 (Can't be shot by a bullot) to 1.0 (Normal tank size). Sometimes just a /size .7 is nice to give yourself an "edge" =].

-NightMare

Teleport in FRONT of your opponent.

2007-12-31T00:09:00.001-08:00

This is just like the /behind code down below where you teleport behind them, only with this code you will teleport in front of them. Kind of a dumb code but fun to mess with people.
Open src/bzflag/composeDefaultKey.cxx:
Find your /behind cheat that you have. It should Look like this:

else if(message=="/behind") {
const Player *Other = LocalPlayer::getMyTank()->getRecipient();
if(Other)
{
LocalPlayer::getMyTank()->setStatus(LocalPlayer::getMyTank()->getStatus() int(PlayerState::Teleporting));
const float* pos = Other->getPosition();
const float* dir = Other->getForward();
const float* vel = Other->getVelocity();
float newpos[3];
float newvel[3];
newpos[0] = pos[0] - 10 * dir[0];
newpos[1] = pos[1] - 10 * dir[1];
newpos[2] = pos[2] + 0.01;
newvel[0] = vel[0];
newvel[1] = vel[1];
newvel[2] = vel[2];
LocalPlayer::getMyTank()->move(newpos, Other->getAngle());
LocalPlayer::getMyTank()->setStatus(LocalPlayer::getMyTank()->getStatus() & ~int(PlayerState::Teleporting));
}
}

Then directly below that add this:

else if(message=="/front") {
const Player *Other = LocalPlayer::getMyTank()->getRecipient();
if(Other)
{
LocalPlayer::getMyTank()->setStatus(LocalPlayer::getMyTank()->getStatus() int(PlayerState::Teleporting));
const float* pos = Other->getPosition();
const float* dir = Other->getForward();
const float* vel = Other->getVelocity();
float newpos[3];
float newvel[3];
newpos[0] = pos[0] + 10 * dir[0];
newpos[1] = pos[1] + 10 * dir[1];
newpos[2] = pos[2] + 0.01;
newvel[0] = vel[0];
newvel[1] = vel[1];
newvel[2] = vel[2];
LocalPlayer::getMyTank()->move(newpos, TargetingUtils::getTargetAzimuth(newpos , pos ));
}
LocalPlayer::getMyTank()->setStatus(LocalPlayer::getMyTank()->getStatus() & ~int(PlayerState::Teleporting));
}

And that is all. Like I said, it is stupid but fun to mess with people when you teleport behind then in front back in forth. Credit for this goes to Phaz =].

-NightMare

Shot prediction.

2007-12-31T00:02:00.000-08:00

This will draw a line on your radar to predict where your shots will go. Its almost exactly perfect. It doesn't work on all servers for some reason, but it should work on most. It is very helpful for 3 shot no jump servers. This code was found through a chat between mrmolez and someone else. So here it is for everyone else to see lol.

Open RadarRenderer.cxx
Find:

//draw world weapon shots

Add this right before it:

FiringInfo myInfo(*myTank, 0);
if (myInfo.flagType != Flags::ShockWave) {
if (!BZDB.isTrue(StateDatabase::BZDB_SHOTSKEEPVERTICALV))
myInfo.shot.vel[2] = 0.0f;
myInfo.flagType = Flags::Laser;
myInfo.lifetime /= 100;
const float cs = colorScale(myInfo.shot.pos[2], muzzleHeight);
glColor3f(1.0f * cs, 1.0f * cs, 1.0f * cs);
LocalShotPath myPath(myInfo);
myPath.radarRender();
}

Let me know how this works for you guys. If you don't like it just take it out lol.

-NightMare

Choose Who Kills You

2007-12-30T23:50:00.000-08:00

Ok this is a very very powerful cheat. With this cheat you send a PM to the player saying "/kill" and you will instantly be killed by that person. It is very useful and funny when you do it to teammates and they get booted for TKing or their score drops immedietly.
In src/bzflag/playing.cxx:
Add to top:

int killMe;

Find:

// used later
float waterLevel = World::getWorld()->getWaterLevel();

Add this after:

if (killMe)
{
gotBlowedUp(myTank,GotShot,killMe);
killMe = 0;
}

In src/bzflag/composeDefaultKey.cxx:
Add to top:

extern int killMe;

Find:

else if (message.length() > 0) {

Add this before that:

else if(message=="/kill") {
const Player *Other = LocalPlayer::getMyTank()->getRecipient();
if(Other)
{ killMe = Other->getId();
}
}

And that is it. Now type /kill in a messege to someone and you will be killed by them. Make sure you do NOT have god mode on when you try to do this otherwise it won't work. Also there is usually 1 random player everytime you log into a server that the code doesn't work against. But other than that one player it should work against everyone else. Let me know if this code works for you guys.

-NightMare

Clientquery spoofing

2007-09-24T21:10:00.000-07:00

Here's something somebody showed me a long time ago, but I haven't put it up until now. Do people keep recognizing your client as a cheat client because of the "clientquery" command? This will make your client appear to be the same as others, or you can make it say whatever you want.

In buildDate.cxx find these lines of code:

#ifdef HAVE_SDL
appVersionStream << "-SDL";
#endif
appVersion = appVersionStream.str();

and put this line of code right after it:

appVersion = "2.0.8.20060513-MAINT-W32VC71";

This makes your client look like the regular, Windows 2.0.8 version. Of course, you could even change appVersion to be anything you want, like "A BZFLAG CHEAT CLIENT, PUNK!" and if I remember correctly, it may not filter out swear words.
So that's the cheat. So stop bugging me Nightmare.
-phasmophage

No Gravity

2007-09-17T01:28:00.001-07:00

By: Phasmophage
Okay, this is a very useless cheat, but because randomdude wants it, I thought I'd post it. =]

We definitely want this cheat to be toggleable. So in playing.cxx, add a line near the beginning (it doesn't matter where, as long as it's not in a function or anything) that says this:

bool bCheatGravity = false;

Now, open LocalPlayer.cxx and put this line of code near the top.

extern bool bCheatGravity;

This will let us use the variable we declared in playing.cxx.

Now, also in LocalPlayer.cxx find these lines:

newVelocity[2] += BZDB.eval(StateDatabase::BZDB_WINGSGRAVITY) * dt;
lastSpeed = speed;
} else {
newVelocity[2] += BZDBCache::gravity * dt;

And replace them with this:

if(bCheatGravity && oldVelocity[2] <= 0.0)newVelocity[2] = 0;
else newVelocity[2] += BZDB.eval(StateDatabase::BZDB_WINGSGRAVITY) * dt;
lastSpeed = speed;
} else {
//newVelocity[2] += BZDBCache::gravity * dt;
if(bCheatGravity && oldVelocity[2] <= 0.0 )newVelocity[2] = 0;
else newVelocity[2] += BZDBCache::gravity * dt;

Now, to add the toggle function, open up ComposeDefaultKey.cxx and add this line near the top:

extern bool bCheatGravity;

And add these lines where your other commands are:

if(message=="/gravity")
{
bCheatGravity = !bCheatGravity;
LocalPlayer *myTank = LocalPlayer::getMyTank();
const float * oldVel = myTank->getVelocity();
float newVelocity[3];
newVelocity[0] = oldVel[0];
newVelocity[1] = oldVel[0];
newVelocity[2] = 0;
myTank->setVelocity(newVelocity);
}

If you don't know where to put this, look for these lines and put it above it:

if (message.length() > 0) {
const char* cmd = message.c_str();
if (LocalCommand::execute(cmd)) {
;
} else if (serverLink) {

and put an "else" in front of " if (message.length() > 0) {"

That's all there is to it. It's pretty useless, I know. But it is funny to see a tank in midair not moving. Which reminds me, you'll need your wings cheat working if you want to drive around in the air.
Hope this is what you were looking for randomdude. ;)
-phaz

Super Jump

2007-09-16T15:42:00.000-07:00

By: Phasmophage
In winged fights, it's hard to catch up with people that are above you, and are continuously jumping. So here's a cheat that will amplify your jump speed by a factor of 8 (or whatever you want it to be, just change it) if you type "/jump".
Add these lines of code in composeDefaultKey.cxx before other commands (See "Quick Guide to Toggling Cheats and Wallwalking"):

if (message=="/jump"){
LocalPlayer *myTank = LocalPlayer::getMyTank();
const float* oldVelocity = myTank->getVelocity();
float newVelocity[3];
newVelocity[0] = oldVelocity[0];
newVelocity[1] = oldVelocity[1];
newVelocity[2] = BZDB.eval(StateDatabase::BZDB_WINGSJUMPVELOCITY);
newVelocity[2] *= 8;
myTank->setVelocity(newVelocity);
}

You will probably want to have your wings cheat turned on when you use this, as you may continue to soar until you are kicked. If you're going too fast, make sure you have you're wings cheat turned on and jump. This will slow you down to regular jump speed.
Questions? Is this working for you? Leave a comment.
-Phasmophage

Protect against "/send"

2007-09-16T15:37:00.000-07:00

By: Phasmophage
"/send" is fun, but it can be horrible if it is used against you. So here's a cheat that will send the flag right back to the person who sent it to you.
In playing.cxx, find these lines of code:

static void handleFlagTransferred( Player *fromTank, Player *toTank, int flagIndex)
{
Flag f = world->getFlag(flagIndex);

fromTank->setFlag(Flags::Null);
toTank->setFlag(f.type);

if ((fromTank == myTank) || (toTank == myTank))
updateFlag(myTank->getFlag());

and put this line of code right under it to send the flag back:

if(toTank == myTank)
serverLink->sendTransferFlag(myTank->getId(), fromTank->getId());

Or you can add this line instead to immediately drop it:
if(toTank == myTank)
serverLink->sendDropFlag(myTank->getPosition());

You'll probably want to make this cheat toggleable (see "Quick Guide to Toggling Cheats and Wallwalking").
-Phaz

Send a flag

2007-09-16T14:57:00.000-07:00

By: Someone (but I had this one too, before ^_^)
What this cheat will do is simulate your flag being stolen by someone and thus sent to them, causing them to drop their flag, and pick up yours. You can send people bad flags, or OO and force them inside buildings with this cheat.
To do this, edit composeDefaultKey.cxx and add these lines of code:

if(message=="/send") {
const Player *Other = LocalPlayer::getMyTank()->getRecipient();
if(Other)
{
serverLink->sendTransferFlag(LocalPlayer::getMyTank()->getId(),Other->getId());
}
}

In front of your other slash commands. (See previous tutorials)
And that's it. PM "/send" to anybody to send them the flag.

Teleport Behind Somebody

2007-09-10T15:33:00.000-07:00

By:Phasmophage
Okay then, this is my first original post in quite a while. Most of the new cheats have been posted by Someone.

Are you tired of having to catch up with others to get a good shot at them? Do you wish that you could just appear behind someone (not the contributor Someone), and automatically aim at them? Well now you can! What this cheat will allow you to do is teleport behind somebody (Kind of like what I heard Agent Smith used to be able to do) by sending them a special private message (Using the period key) like "/behind" or "/b".
To do this, we will need to edit the "composeDefaultKey.cxx" in the directory "/src/bzflag/". Now what you'll need to do is find this line of code:

if (message.length() > 0) {

and change it to this:

else if (message.length() > 0) {

and put this above it:

if(message=="/behind") {
const Player *Other = LocalPlayer::getMyTank()->getRecipient();
if(Other)
{
LocalPlayer::getMyTank()->setStatus(LocalPlayer::getMyTank()->getStatus() | int(PlayerState::Teleporting));
const float* pos = Other->getPosition();
const float* dir = Other->getForward();
const float* vel = Other->getVelocity();
float newpos[3];
float newvel[3];
newpos[0] = pos[0] - 10 * dir[0];
newpos[1] = pos[1] - 10 * dir[1];
newpos[2] = pos[2] + 0.01;
newvel[0] = vel[0];
newvel[1] = vel[1];
newvel[2] = vel[2];
LocalPlayer::getMyTank()->move(newpos, Other->getAngle());
LocalPlayer::getMyTank()->setStatus(LocalPlayer::getMyTank()->getStatus() & ~int(PlayerState::Teleporting));
}
}

You can change the command "/behind" to anything you want. You may want to make it shorter. I also don't think that the "setStatus" functions really do anything important, so you may want to get rid of those, but they don't do any harm anyway.

If you're really into coding, what you can do, like I've done, is instead of having the "Other" player be the recipient of a message, you can make it the closest enemy through using the "findBestTarget()" function in TargetingUtils. You may also want to bind this action to a key, making it quicker to use. I won't go into the details on this, but for one method of binding keys, see Someone's comment on "Quick Guide to Toggling Cheats and Wallwalking". This method doesn't work for me, so I replace some commands I don't use, like "w" for "toggle console".

Questions? Comments? If I missed anything, or if you have any ideas on improvement *cough* Someone *cough*, post a comment.
Have fun with this one.
-phasmophage
aka phaz

GM Multi-Lock

2007-09-09T21:11:00.000-07:00

By: Someone
"Someone" has an improvement on the previously posted "GMWontUnlock" what this cheat will do is allow individual Guided Missiles to track individual targets, instead of all Guided Missiles following one target.
To do this, open GuidedMissileStrategy.cxx and find these lines of code:

LocalPlayer* myTank = LocalPlayer::getMyTank();
if (myTank)
target = myTank->getTarget();

And replace them with:
if (lastTarget == NoPlayer) {
setTarget();
LocalPlayer* myTank = LocalPlayer::getMyTank();
if (myTank)
target = myTank->getTarget();
} else {
target = lookupPlayer(lastTarget);
}

You can thank "Someone" for this post, see his comment for the post "GMWontUnlock."

"GuidedMissileWontUnlock"

2007-09-08T22:23:00.000-07:00

Here's an old one that I believe Mr_Molez had on a private site, but I haven't seen it anywhere else so I'll post it here.

Normally, when one dies after shooting a guided missile, the missile no longer tracks the target. This cheat is listed as one of the "Subtle Cheats" of BZFlag, and what it does is it continues to track the target, even after dying. Here's how to do it.

In LocalPlayer.cxx, find this line:
target = NULL; // lose lock when dead

And delete it.

Reduce laser reload

2007-08-20T18:05:00.000-07:00

By: Someone
(Copied straight off his comment from "Wings Gravity Fix for Bloodbath.")
Laser fast-reload

In src/bzflag/SegmentedShotStrategy.cxx, find:
---
setReloadTime(_path->getReloadTime()
/ BZDB.eval(StateDatabase::BZDB_LASERADRATE));
---
Replace with:
---
setReloadTime(_path->getReloadTime()
* BZDB.eval(StateDatabase::BZDB_LASERADLIFE))

Enable Autopilot all the time

2007-08-20T18:03:00.000-07:00

By: Someone
(Copied straight off his comment from "Wings Gravity Fix for Bloodbath.")
Want to use autopilot on maps that disable it?

In src/bzflag/clientCommands.cxx, find:
---
if (BZDB.isTrue(StateDatabase::BZDB_DISABLEBOTS)) {
hud->setAlert(0, "autopilot not allowed on this server", 1.0f, true);
return std::string();
}
---
Remove it.

Auto Apologizer

2007-08-20T18:02:00.001-07:00

By: Someone
(Copied straight off his comment from "Wings Gravity Fix for Bloodbath.")
Do you ever tire of saying 'sry' to people you tk?

In src/bzflag/playing.cxx find:
---
if (myTank->isAutoPilot()) {
char meaculpa[MessageLen];
memset(meaculpa, 0, MessageLen);
strncpy(meaculpa,
"sorry, i'm just a silly machine",
MessageLen);
---
Replace it with:
---
if (myTank->isAutoPilot() || 1) {
char meaculpa[MessageLen];
memset(meaculpa, 0, MessageLen);
strncpy(meaculpa,
"sry",
MessageLen);

Find geno flag

2007-08-20T18:00:00.000-07:00

By: Someone
This is how to find a geno flag with the top of your mousebox. Only works if phantom zone spoof is off.

Geno/other team flag finder: You know that there is a marker for your own team flag, and antidotes above the targeting square, so why not have one for geno, and other team flags?

In src/bzflag/playing.cxx, find:
---
static void prepareTheHUD()
{
// prep the HUD
if (myTank) {
const float* myPos = myTank->getPosition();
hud->setHeading(myTank->getAngle());
hud->setAltitude(myPos[2]);
if (world->allowTeamFlags()) {
const float* myTeamColor = Team::getTankColor(myTank->getTeam());
// markers for my team flag
for (int i = 0; i < numFlags; i++) {
Flag& flag = world->getFlag(i);
if ((flag.type->flagTeam == myTank->getTeam())
&& ((flag.status != FlagOnTank) ||
(flag.owner != myTank->getId()))) {
const float* flagPos = flag.position;
float heading = atan2f(flagPos[1] - myPos[1],flagPos[0] - myPos[0]);
hud->addMarker(heading, myTeamColor);
}
}
}
if (myTank->getAntidoteLocation()) {
// marker for my antidote flag
const GLfloat* antidotePos = myTank->getAntidoteLocation();
float heading = atan2f(antidotePos[1] - myPos[1],
antidotePos[0] - myPos[0]);
const float antidoteColor[] = {1.0f, 1.0f, 0.0f};
hud->addMarker(heading, antidoteColor);
}
}
return;
}
---
Replace it with:
---
static void prepareTheHUD()
{
// prep the HUD
if (myTank) {
const float* myPos = myTank->getPosition();
hud->setHeading(myTank->getAngle());
hud->setAltitude(myPos[2]);
if (world->allowTeamFlags()) {
// markers for my team flag
for (int i = 0; i < numFlags; i++) {
Flag& flag = world->getFlag(i);
if (flag.type->flagTeam != NoTeam) {
const float* flagPos = flag.position;
float heading = atan2f(flagPos[1] - myPos[1],flagPos[0] - myPos[0]);
hud->addMarker(heading, Team::getTankColor(flag.type->flagTeam));
}
}
}
if (myTank->getAntidoteLocation()) {
// marker for my antidote flag
const GLfloat* antidotePos = myTank->getAntidoteLocation();
float heading = atan2f(antidotePos[1] - myPos[1],
antidotePos[0] - myPos[0]);
const float antidoteColor[] = {1.0f, 1.0f, 0.0f};
hud->addMarker(heading, antidoteColor);
}
for (int i = 0; i < numFlags; i++) {
Flag& flag = world->getFlag(i);
if (flag.type == Flags::Genocide) {
const float* flagPos = flag.position;
float heading = atan2f(flagPos[1] - myPos[1],flagPos[0] - myPos[0]);
hud->addMarker(heading, flag.type->getColor());
}
}
}
return;
}
---

See his post on "Wings gravity fix for bloodbath"

Shoot Normal Bullets in PZ

2007-08-20T17:58:00.000-07:00

By: Someone
(Sorry to take so long posting these, usually Lord Jesus posts other peoples' cheats. This is basically just copied exactly from someone's comment.)

In src/bzflag/ShotPath.cxx find:

if (tank.getFlag() == Flags::PhantomZone && !tank.isFlagActive()){

Replace it with:

if (tank.getFlag() == Flags::PhantomZone){

Wings Gravity Fix for BloodBath

2007-08-12T17:46:00.001-07:00

You may have noticed that if you tried to use the wings cheat in BloodBath, you'll start to fly away until you get autokicked. The problem lies in the fact that there are two separate gravity values: one for normal jumps and the other for wings. Normally, the value of gravity is negative (usually around -9.8) causing you to go downwards. However, when this value is set to a positive value, you start to shoot upwards. BloodBath set the wings gravity to 100, so you will shoot upwards. So here's a quick, one-liner fix so you can you the wings cheat on their server again.
For this cheat, you will need to edit LocalPlayer.cxx and find this line:

newVelocity[2] += BZDB.eval(StateDatabase::BZDB_WINGSGRAVITY) * dt;

And add this line of code right before it:
if(BZDB.eval(StateDatabase::BZDB_WINGSGRAVITY) >= 0)BZDB.setFloat(StateDatabase::BZDB_WINGSGRAVITY, BZDB.eval(StateDatabase::BZDB_GRAVITY));

So your code should look like this, in the end:
if(BZDB.eval(StateDatabase::BZDB_WINGSGRAVITY) >=0 )BZDB.setFloat(StateDatabase::BZDB_WINGSGRAVITY, BZDB.eval(StateDatabase::BZDB_GRAVITY));
newVelocity[2] += BZDB.eval(StateDatabase::BZDB_WINGSGRAVITY) * dt;

What this will do is check to see if wings gravity is set to a positive number, and if so, change it to the value of normal gravity.
Did I miss something? Was this helpful? Leave a comment.

Have fun. ;)
-Phaz

Quick Guide to Toggling Cheats and Wallwalking

2007-08-08T21:23:00.000-07:00

By: Phasmophage

Many of you have asked how to toggle cheats. It is one of the most important things cheaters should know how to do. Having a phase cheat is pretty frustrating without being able to turn it off to land on buildings. It's also nice to turn off the wings cheat on servers like Bloodbath, where they reversed wings gravity to make cheaters with wings shoot up into the air until they are autokicked. So here's a non-specific guide on cheat toggling.
Now, the method I use for toggling toggles cheats when you say certain commands by pressing "z", "n", "m", "," or "." So, for example, to toggle god mode I would say "/god" to my teammates, or whoever. The program then recognizes "/god" as a keyword, toggles the cheat, and prevents "/god" from actually being sent. The file that controls sending messages to others is "ComposeDefaultKey.cxx". My personal ComposeDefaultKey.cxx is probably two times bigger than the original.

So let's get started, shall we? Open up "ComposeDefaultKey.cxx" and find these lines of code:
if (sendIt) {
std::string message = hud->getComposeString();
if (message.length() > 0) {
const char* cmd = message.c_str();
if (LocalCommand::execute(cmd)) {
;
} else if (serverLink) {

Let's focus on this line, for a second:
std::string message = hud->getComposeString();

"message" is our message (duh) that we're about to send out, so the "message" string is going to be very important to us later. But first, let me explain boolean variables. Boolean variables, or the "bool" type in C++ (the language used to create BZFlag) can only be true or false. This is the data type we will use to turn our cheats off and on. Now to access these variables from other files, (For example, we need to switch the variable in ComposeDefaultKey.cxx but perhaps the actual cheat is in playing.cxx) we need to declare a variable "extern" in some files.
Argh, I'm bad at explaining, so here's an example:
Open up playing.cxx and find these lines of code:

#ifdef ROBOT
static void handleMyTankKilled(int reason);
static ServerLink* robotServer[MAX_ROBOTS];
#endif

Right after those lines, put this:

bool bCheatOO = false;

That variable is our on and off switch that will let us walk through walls. The b is for "boolean" and the OO is for Oscillation Overthruster, and the "cheat" because we're cheating. You can name it whatever you want.

Now to access it in another file, like ComposeDefaultKey.cxx, find these lines of code:

#define MAX_MESSAGE_HISTORY (20)

MessageQueue messageHistory;
unsigned int messageHistoryIndex = 0;

and put this right after:
extern bool bCheatOO;

"Extern" tells us that this variable is defined elsewhere, but allows us to use it.
Now let's go back to these lines of code:

if (sendIt) {
std::string message = hud->getComposeString();
if (message.length() > 0) {
const char* cmd = message.c_str();
if (LocalCommand::execute(cmd)) {
;
} else if (serverLink) {

And change it to this:

if (sendIt) {
std::string message = hud->getComposeString();
if (message.length() > 0) {
const char* cmd = message.c_str();
if(message=="/oo")bCheatOO = !bCheatOO; //We added this line, which toggles bCheatOO
else if (LocalCommand::execute(cmd)) { //And put an "else" before "if"
;
} else if (serverLink) {

So if you enter "/oo" you'll switch the cheat to its opposite state.

Now, since the actual Oscillation Overthruster stuff is in LocalPlayer.cxx, let's open that up and find these lines of code:

/* local implementation headers */
#include "World.h"
#include "sound.h"
#include "ForceFeedback.h"
#include "effectsRenderer.h"

and put this right after:
extern bool bCheatOO;

Now for the real cheats. Find these lines of code:
// phased means we can pass through buildings
const bool phased = ((location == Dead) || (location == Exploding) ||
(getFlag() == Flags::OscillationOverthruster) ||
isPhantomZoned());

and change it to this:
const bool phased = ((location == Dead) || (location == Exploding) ||
(getFlag() == Flags::OscillationOverthruster) ||
isPhantomZoned() || bCheatOO);

See how we added "|| bCheatOO" to the end? This means if we have Oscillation Overthruster, Phantom Zone, OR if bCheatOO is turned on, then we can pass through buildings.

Find this line of code:
if (location == InBuilding && getFlag() == Flags::OscillationOverthruster) {

And change it to this:
if (location == InBuilding && (getFlag() == Flags::OscillationOverthruster || bCheatOO)) {

Actually, that line isn't too important, it just shows the the weird effects when you're crossing a wall.

Now find this:
if (expelled && phased)
expelled = (obstacle->getType() == WallObstacle::getClassName() ||
obstacle->getType() == Teleporter::getClassName() ||
(getFlag() == Flags::OscillationOverthruster && desiredSpeed < 0.0f &&
p[2] == 0.0f));

and change it to this:
if (expelled && phased)
expelled = (obstacle->getType() == WallObstacle::getClassName() ||
obstacle->getType() == Teleporter::getClassName() ||
(getFlag() == Flags::OscillationOverthruster && !bCheatOO && desiredSpeed < 0.0f &&
p[2] == 0.0f));

This time, we added "&& !bCheatOO" meaning "And bCheatOO is NOT turned on" because what these lines of code do is make sure that we can't back up in buildings. And we do want to.
Find these lines of code:

expelled = (obstacle != NULL);
if (expelled && phased)
expelled = (obstacle->getType() == WallObstacle::getClassName() ||
obstacle->getType() == Teleporter::getClassName() ||
(hasOOflag && desiredSpeed < 0.0f && p[2] == 0.0f));

And change it to this:
expelled = (obstacle != NULL);
if (expelled && phased)
expelled = (obstacle->getType() == WallObstacle::getClassName() ||
(!bCheatOO && obstacle->getType() == Teleporter::getClassName()) ||
(hasOOflag && desiredSpeed < 0.0f && !bCheatOO && p[2] == 0.0f));

Find these lines of code:
// oscillation overthruster tank in building can't back up
if (fracOfMaxSpeed < 0.0f && getLocation() == InBuilding &&
flag == Flags::OscillationOverthruster) {
fracOfMaxSpeed = 0.0f;
}

And change it to this:
// oscillation overthruster tank in building can't back up
if (fracOfMaxSpeed < 0.0f && getLocation() == InBuilding &&
flag == Flags::OscillationOverthruster && !bCheatOO) {
fracOfMaxSpeed = 0.0f;
}

Find this line of code:
if (! (firingStatus == Ready || firingStatus == Zoned))
return false;

Which doesn't let us fire if we we're sealed, and change it to this:
if (! (firingStatus == Ready || bCheatOO || firingStatus == Zoned))
return false;

Also find this:
// make sure we're allowed to shoot
if (!isAlive() || isPaused() ||
((location == InBuilding) && !isPhantomZoned())) {
return false;
}

And change it to this:
// make sure we're allowed to shoot
if (!isAlive() || isPaused() ||
((location == InBuilding) && !isPhantomZoned() && !bCheatOO)) {
return false;
}

And that's all of it. I think. If this doesn't work, let me know. Hopefully, this will teach you how to toggle your cheats. Again, every cheater needs to know how to do this. Seriously. Have fun with this! And if you have any ideas, critiques, or if you enjoyed this not-so-quick cheat guide: Please, leave a comment. ;)
And I am out!
-Phaz

No Blindness

2007-08-08T21:13:00.000-07:00

Another, really easy cheat. So you can see out the window.

Open playing.cxx and find this line of code:

if (bestTarget->isHunted() && myTank->getFlag() != Flags::Blindness &&

And change it to this

if (bestTarget->isHunted() &&

Then find these lines of code:
sceneRenderer->setBlank(myTank && (myTank->isPaused() ||
myTank->getFlag() == Flags::Blindness));
And change it to this:

sceneRenderer->setBlank(myTank && (myTank->isPaused()));

Or just delete it altogether.

And that's pretty much it. If I forgot anything, leave a comment.
-Phaz

No Jamming

2007-08-08T21:05:00.000-07:00

Jamming is one annoying flag. Actually, I wouldn't know because whenever I had the jamming flag, I had this cheat preventing the effects. This is a really simple and subtle cheat that every cheater needs. I can't believe this wasn't posted yet.

For this cheat, open playing.cxx and find this line of code:
radar->setJammed(flag == Flags::Jamming);

and change it to this:
radar->setJammed(false);

And that's pretty much it. Hope I didn't forget anything.
-Phaz

Avoid Picking Up Bad Flags

2007-08-05T03:49:00.000-07:00

Brought to you by: Someone

You may recall that we have posted some techniques for minimizing the impact of bad flags:

1. Drop Bad Flags Instantly.
2. Drop Bad Flags Like Regular Flags.

We now bring you yet another technique: avoid picking them up altogether. With this edit, if a flag is bad, you will simply drive over it without picking it up.

For this, we're going to playing.cxx in /src/bzflag/ of the extracted source. Search for "if (world->getFlag(i).type == Flags::Null ||", and you will find this section:


        if (world->getFlag(i).type == Flags::Null || world->getFlag(i).status != FlagOnGround)
          continue;

Notice the second line. After the "!= FlagOnGround", we are going to add this:

|| world->getFlag(i).type->flagQuality == FlagBad

The section should now read like this:


        if (world->getFlag(i).type == Flags::Null || world->getFlag(i).status != FlagOnGround ||
            world->getFlag(i).type->flagQuality == FlagBad)
          continue;

Save the file, compile your client, and you're done. To see Someone's original instructions for this tip, read his comment to "Stealth Tanks Blink on Radar". As always...

Have fun!

Immunity from Team Kill and Self Kill Shots

2007-08-05T03:15:00.000-07:00

Brought to you by: Someone

Have you ever been chasing down an enemy only to be killed by a teammate shooting at the same enemy? Have you ever been killed by your own shots? Here's a tip that prevent shots from teammates and yourself from killing you.

For this edit, we're going to playing.cxx in /src/bzflag/ of the extracted source. Search for " myTank->checkHit(myTank, hit, minTime);", and you will find this section:


  float minTime = Infinity;

  myTank->checkHit(myTank, hit, minTime);
  int i;
  for (i = 0; i < curMaxPlayers; i++)
    if (player[i])
      myTank->checkHit(player[i], hit, minTime);

Let's remove the line "myTank->checkHit(myTank, hit, minTime);" so that the section now reads like this:


  float minTime = Infinity;

  int i;
  for (i = 0; i < curMaxPlayers; i++)
    if (player[i])
      myTank->checkHit(player[i], hit, minTime);

Next, we are going to add a new line immediately below "if (player[i])":


    if (player[i]->getTeam() != myTank->getTeam() || myTank->getTeam() == RogueTeam)

The section should now read like this:


  float minTime = Infinity;

  int i;
  for (i = 0; i < curMaxPlayers; i++)
    if (player[i])
    if (player[i]->getTeam() != myTank->getTeam() || myTank->getTeam() == RogueTeam)
    myTank->checkHit(player[i], hit, minTime);

Save the file, compile your new client, and you're done. To see Someone's original instructions, read his comment "Stealth Tanks Blink on Radar". As always...

Have fun!

Guided Lasers

2007-08-04T23:45:00.000-07:00

By: Phasmophage
Okay, I was originally planning to keep this in reserve due to its immense power. But, due to popular demand (namely randomdude), I have decided to post it.

Guided lasers allow you to lock on to an opponent's position and have perfect accuracy when shooting at them. To do this, we will need to edit two source files: playing.cxx and LocalPlayer.cxx.

The reason we will be editing playing.cxx is to allow us to lock on with lasers. So, find these lines of code:

// see if it's inside lock-on angle (if we're trying to lock-on)
if (a < BZDB.eval(StateDatabase::BZDB_LOCKONANGLE) && // about 8.5 degrees
((myTank->getFlag() == Flags::GuidedMissile) || // am i locking on?
tankHasShotType(myTank, Flags::GuidedMissile)) &&
player[i]->getFlag() != Flags::Stealth && // can't lock on stealth
!player[i]->isPaused() && // can't lock on paused
!player[i]->isNotResponding() && // can't lock on not responding
d < bestDistance) {
bestTarget = player[i];
bestDistance = d;
lockedOn = true;
}

and change this line:
((myTank->getFlag() == Flags::GuidedMissile) || // am i locking on?

to this:
((myTank->getFlag() == Flags::GuidedMissile) || (myTank->getFlag() == Flags::Laser) || // am i locking on?

You will also find these lines, very similar to the lines before:
if (a < BZDB.eval(StateDatabase::BZDB_LOCKONANGLE) && // about 8.5 degrees
myTank->getFlag() == Flags::GuidedMissile && // am i locking on?
player[i]->getFlag() != Flags::Stealth && // can't lock on stealth
!player[i]->isPaused() && // can't lock on paused
!player[i]->isNotResponding() && // can't lock on not responding
d < bestDistance) { // is it better?
bestTarget = player[i];
bestDistance = d;
lockedOn = true;
}

Now change this line:
myTank->getFlag() == Flags::GuidedMissile && // am i locking on?

To this:
(myTank->getFlag() == Flags::GuidedMissile || myTank->getFlag() == Flags::Laser) && // am i locking on?

That's all the edits for playing.cxx

We will now edit LocalPlayer.cxx and find these lines of code:
else {
// apply any handicap advantage to shot speed
if (handicap > 0.0f) {
const float speedAd = 1.0f + (handicap * (BZDB.eval(StateDatabase::BZDB_HANDICAPSHOTAD) - 1.0f));
const float* dir = getForward();
const float* tankVel = getVelocity();
const float shotSpeed = speedAd * BZDB.eval(StateDatabase::BZDB_SHOTSPEED);
firingInfo.shot.vel[0] = tankVel[0] + shotSpeed * dir[0];
firingInfo.shot.vel[1] = tankVel[1] + shotSpeed * dir[1];
firingInfo.shot.vel[2] = tankVel[2] + shotSpeed * dir[2];
}

Now add these lines of code after it: (Wrote it myself, so it's pretty cruddy looking)
bool LockedOn = false;
const Player * target = getTarget();
if(target){
//const float* tankVel = getVelocity();
const float shotSpeed = BZDB.eval(StateDatabase::BZDB_SHOTSPEED);
float newAz = TargetingUtils::getTargetAzimuth( getPosition(), target->getPosition() );
float newPos[3];
const float * tarPos = target->getPosition();
float enemyPos[3];
const float *tv = target->getVelocity();
enemyPos[0] = tarPos[0] + (0.3f * tv[0]); //Lag adjustment
enemyPos[1] = tarPos[1] + (0.3f * tv[1]);
enemyPos[2] = tarPos[2] + (0.3f * tv[2]);
const float * myPos = getPosition();
const float * myDir = getForward();
newPos[0] = enemyPos[0] - ( myPos[0] + (myDir[0] * 0.1)); //Muzzlefront?
newPos[1] = enemyPos[1] - ( myPos[1] + (myDir[1] * 0.1)); //Muzzlefront?
newPos[2] = enemyPos[2] - myPos[2];
//newPos[2] += target->getMuzzleHeight(); // right between the eyes
float newElevation = atan2f(newPos[2], hypotf(newPos[1], newPos[0]));
float newDir[3] = {cosf(newAz), sinf(newAz), sinf(newElevation)};
firingInfo.shot.vel[0] = /*tankVel[0] +*/ shotSpeed * newDir[0];
firingInfo.shot.vel[1] = /*tankVel[1] +*/ shotSpeed * newDir[1];
firingInfo.shot.vel[2] = /*tankVel[2] +*/ shotSpeed * newDir[2];
LockedOn = true;
}

// Set _shotsKeepVerticalVelocity on the server if you want shots
// to have the same vertical velocity as the tank when fired.
// keeping shots moving horizontally makes the game more playable.
if (!LockedOn && !BZDB.isTrue(StateDatabase::BZDB_SHOTSKEEPVERTICALV)) firingInfo.shot.vel[2] = 0.0f;

Oh yeah, forgot, the last four lines should replace these lines:

// Set _shotsKeepVerticalVelocity on the server if you want shots
// to have the same vertical velocity as the tank when fired.
// keeping shots moving horizontally makes the game more playable.
if (!BZDB.isTrue(StateDatabase::BZDB_SHOTSKEEPVERTICALV)) firingInfo.shot.vel[2] = 0.0f;

This will allow your lasers to shoot down or up at people, so this cheat sticks out like a sore thumb.

Oh yeah, forgot again. You'll need to put
#include "TargetingUtils.h"
after this line:
#include "effectsRenderer.h"

And that's basically it. This powerful cheat written by phasmophage (aka "Phaz" or me) and brought to you exclusively by bzfcheat.blogspot.com.
If there is anything I might have forgotten, bad math, bad implementation, or if you actually really like it, comments are greatly appreciated.

Have fun!
-Phaz
;)

Stealth Tanks Blink on Radar

2007-08-03T13:32:00.000-07:00

By: Phasmophage
This post assumes that you have already taken out the code that blocks you from seeing stealth tanks on your radar. If you haven't already done so, follow the directions in the post titled "See STEALTH Tanks on Radar."

Here is a great way for you not to blow your cover as a cheater. If you have Super Bullet, you don't want to hit a stealthed tank behind a wall. To make sure you know which tanks are stealthed so you can approach them with caution and not blow your cover, we will make them blink.

This quick and easy edit requires that you open RadarRenderer.cxx and find these lines of code:

if (flashTank.isOn()) {
if (!toggleTank) {
float flashcolor[3];
flashcolor[0] = 0.0f;
flashcolor[1] = 0.8f;
flashcolor[2] = 0.9f;
glColor3fv(flashcolor);
}
} else {
toggleTank = !toggleTank;
flashTank.setClock(0.2f);
}
}

Now, just put this right after it:
//Start stealth flash
if ((player->getFlag() == Flags::Stealth)) {
static TimeKeeper lastTime = TimeKeeper::getCurrent();
static bool flash = false;
const float elapsed = float(TimeKeeper::getCurrent() - lastTime);
if(elapsed < 0.3f){
if(!flash)
{
float flashcolor[3];
flashcolor[0] = 0.5f; //This controls the color of the flash.
flashcolor[1] = 0.5f;
flashcolor[2] = 0.5f;
glColor3fv(flashcolor);
}
}
else
{
flash = !flash;
lastTime = TimeKeeper::getCurrent();
}
}
//End stealth flash

This will make stealthed tanks blink a gray color on your radar. If you want it to blink faster, change 0.3 to a smaller number, or a bigger number to blink more slowly. You can edit the 0.5f's to fit your tastes in color.

Don't blow your cover,
-Phaz ;)

Flag Coloring and Identify

2007-07-28T22:30:00.000-07:00

By: Phasmophage (me)
I first read up about Flag Coloring on BZWiki and thought it was a great idea. It is a simple cheat that allows you to mark special flags (Like Laser, GM, SW, etc) with a special color. The coloring allows you to spot a special flag from a distance, and it is even colored on the radar. Imagine always being able to get a guided missile, laser, shock wave, geno, or any flag you want.
Are you drooling yet? I know I would be.
So, this edit lies in the file Flag.cxx where we will find these lines of code:

const float* FlagType::getColor() const
{
if (flagTeam == NoTeam)
return superColor;
else
return Team::getTankColor(flagTeam);
}

We will basically replace the above lines of code with the following:

const float* FlagType::getColor() const
{
static const float superColor[3] = { 1.0, 1.0, 1.0 };
static const float LaserColor[3] = { 0.8, 0.2, 0.0 };
static const float ShockColor[3] = { 0.0, 0.5, 0.5 };
static const float GuideColor[3] = { 0.5, 0.5, 0.0 };
static const float GenoCColor[3] = { 0.2, 0.8, 0.2 };
static const float BadFlColor[3] = { 0.0, 0.0, 0.0 };
if(this==Flags::Laser)return LaserColor;
else if(this==Flags::ShockWave)return ShockColor;
else if(this==Flags::GuidedMissile)return GuideColor;
else if(this==Flags::Genocide)return GenoCColor;
else if(endurance==FlagSticky)return BadFlColor;
else if (flagTeam == NoTeam)
return superColor;
else
return Team::getTankColor(flagTeam);
}

This colors laser flags red, SW blue, GM yellow, Geno green, and bad flags black. You can also change the colors, or add more flags if you like.

To identify flags we haven't colored, we will switch identify to be permanently on. To do this, open the file playing.cxx and find these lines of code:

else if (flagd == Flags::Identify) {
// identify closest flag

and oh-so-simply replace it with this:

if (1 || flagd == Flags::Identify) {
// identify closest flag

Note: Many servers have caught on to this cheat, and have disguised all flags as Phantom Zone. But then again, some haven't, and these cheats are insanely handy. Not to mention, they are pretty subtle.
If you like this cheat, want to critique it, or if these cheats have saved your marriage, leave a comment!

Have fun with this one.
-Phaz

Instant Self Destruct

2007-07-28T22:15:00.000-07:00

By: Phasmophage
So, you're in a corner and a guy is about to shoot you. Or maybe he's locked on to you with Guided Missile. Maybe your in range of a Shock Wave. Either way, this guy's about to kill you, and you know it. So here's a great way to kill yourself instantly and not give that little punk the point, (and totally piss him off while your at it): Instant Self Destruct!

This is a really simple edit, so open up playing.cxx and find these lines:

if (destructCountdown > 0.0f) {
const int oldDestructCountdown = (int)(destructCountdown + 0.99f);
destructCountdown -= dt;
if (destructCountdown <= 0.0f) {
// now actually destruct

Edit it so it looks like this:

if (destructCountdown > 0.0f) {
const int oldDestructCountdown = (int)(destructCountdown + 0.99f);
destructCountdown -= dt;
if (1 || destructCountdown <= 0.0f) { destructCountdown = 0.0f; // now actually destruct

And now you can die with dignity!
Alright, so this is one of my more stupid "cheats" but it still has its advantage.
Enjoy it!
-Phaz

Ultimate Pausing

2007-07-28T21:44:00.000-07:00

By: Phasmophage

Alright now, this is my first real post as a contributor.

Anyhoo, most of you know that it takes five seconds to pause, and you have to be on the ground or on a building, or else your pause will cancel. Also, after you pause your radar and your HUD (Heads Up Display) go completely blank, not to mention you have no sound. This leaves you vulnerable to being shot by some dude that has been waiting right behind you. Well, no more! With this cheat, you will be able to pause anywhere instantly, and be able to see what's around you. (And it's also really funny to pause in the air right in front of somebody, they'll be thinking "Why is that dude frozen in the air with a bubble around him?")

First, you'll need to open clientCommands.cxx and find these lines:

} else if (myTank->getLocation() == LocalPlayer::InBuilding) {
// custom message when trying to pause while in a building
// (could get stuck on un-pause if flag is taken)
hud->setAlert(1, "Can't pause while inside a building", 1.0f, false);

} else if (myTank->getLocation() == LocalPlayer::InAir) {
// custom message when trying to pause when jumping/falling
hud->setAlert(1, "Can't pause when you are in the air", 1.0f, false);

} else if (myTank->getLocation() != LocalPlayer::OnGround &&
myTank->getLocation() != LocalPlayer::OnBuilding) {
// catch-all message when trying to pause when you should not
hud->setAlert(1, "Unable to pause right now", 1.0f, false);

What these lines do is make sure you're in a valid spot to begin the pause countdown. We don't want that, so what you should do is put a "0 &&" to skip checking, so your code looks like this:

} else if (0 && myTank->getLocation() == LocalPlayer::InBuilding) {
// custom message when trying to pause while in a building
// (could get stuck on un-pause if flag is taken)
hud->setAlert(1, "Can't pause while inside a building", 1.0f, false);

} else if (0 && myTank->getLocation() == LocalPlayer::InAir) {
// custom message when trying to pause when jumping/falling
hud->setAlert(1, "Can't pause when you are in the air", 1.0f, false);

} else if (0 && myTank->getLocation() != LocalPlayer::OnGround &&
myTank->getLocation() != LocalPlayer::OnBuilding) {
// catch-all message when trying to pause when you should not
hud->setAlert(1, "Unable to pause right now", 1.0f, false);

Now we will make edits to LocalPlayer.cxx

Find these lines:
// if paused then boost the reload times by dt (so that, effectively,
// reloading isn't performed)
int i;
if (isPaused()) {
for (i = 0; i <>
if (shots[i]) {
shots[i]->boostReloadTime(dt);
}
}

and add a "0 &&" before the isPaused() so the line looks like this:

if (0 && isPaused()) {

This allows you to reload while paused.

Now we need to make edits in playing.cxx

Find these lines in the updatePauseCountdown function:

if (pauseCountdown <= 0.0f) {
pauseCountdown = 0.0f;

We will change this to:

if (1 || pauseCountdown <= 0.0f) {
pauseCountdown = 0.0f;

Below these lines you will find some code similar to the ones we edited in clientCommands.cxx:

if (myTank->getLocation() == LocalPlayer::InBuilding) {
// custom message when trying to pause while in a building
// (could get stuck on un-pause if flag is taken/lost)
hud->setAlert(1, "Can't pause while inside a building", 1.0f, false);

} else if (myTank->getLocation() == LocalPlayer::InAir) {
// custom message when trying to pause when jumping/falling
hud->setAlert(1, "Can't pause when you are in the air", 1.0f, false);

} else if (myTank->getLocation() != LocalPlayer::OnGround &&
myTank->getLocation() != LocalPlayer::OnBuilding) {
// catch-all message when trying to pause when you should not
hud->setAlert(1, "Unable to pause right now", 1.0f, false);

} else if (myTank->isPhantomZoned() ) {
// custom message when trying to pause while zoned
hud->setAlert(1, "Can't pause when you are in the phantom zone", 1.0f, false);

after all the "if(" parts we will add "0 && " to skip the checks. (WARNING: Make sure you don't pause in a building with OO or PZ because you will lose the flag, and you may be stuck. Make sure you have the proper cheats to get out of it.) The edited code should look like this:

if (0 && myTank->getLocation() == LocalPlayer::InBuilding) {
// custom message when trying to pause while in a building
// (could get stuck on un-pause if flag is taken/lost)
hud->setAlert(1, "Can't pause while inside a building", 1.0f, false);

} else if (0 && myTank->getLocation() == LocalPlayer::InAir) {
// custom message when trying to pause when jumping/falling
hud->setAlert(1, "Can't pause when you are in the air", 1.0f, false);

} else if (0 && myTank->getLocation() != LocalPlayer::OnGround &&
myTank->getLocation() != LocalPlayer::OnBuilding) {
// catch-all message when trying to pause when you should not
hud->setAlert(1, "Unable to pause right now", 1.0f, false);

} else if (0 && myTank->isPhantomZoned() ) {
// custom message when trying to pause while zoned
hud->setAlert(1, "Can't pause when you are in the phantom zone", 1.0f, false);

You'll also find these lines, which turn off the sound:

// turn off the sound
if (savedVolume == -1) {
savedVolume = getSoundVolume();
setSoundVolume(0);
}

You can basically delete it or comment it out so it looks like this:
// turn off the sound
/*if (savedVolume == -1) {
savedVolume = getSoundVolume();
setSoundVolume(0);
}*/

Now, to see the radar while paused, find these lines:

if (radar) {
const bool showBlankRadar = !myTank || (myTank && myTank->isPaused());
const bool observer = myTank && (myTank->getTeam() == ObserverTeam);
radar->render(*sceneRenderer, showBlankRadar, observer);
}

And edit the second line so it looks like this:
const bool showBlankRadar = !myTank;

Finally, to see out the HUD while paused, find these lines:
// turn blanking and inversion on/off as appropriate
sceneRenderer->setBlank(myTank && (myTank->isPaused() ||
myTank->getFlag() == Flags::Blindness));

And you can delete it or comment it out, so it looks like this:
// turn blanking and inversion on/off as appropriate
// sceneRenderer->setBlank(myTank && (myTank->isPaused() ||
// myTank->getFlag() == Flags::Blindness));

And this should let you pause anywhere instantly and see out the radar, the HUD, hear sounds while paused.

Tell me what you think,
-Phaz
Have fun!

View Radar on Maps without Radar

2007-07-27T23:11:00.000-07:00

By: Phasmophage (aka "Phaz")

Here's a sweet little number that you won't want to pass up... How would you like radar on those maps without radar? Now you can have an advantage over with tanks by having access to your radar on maps that don't allow it! As Phaz tells us:

"On maps with no radar, the radar limit is set to 0 or a negative number. This will fix it to the correct number, the size of the world. So now no more hide and seek!"

For this, we visit RadarRenderer.cxx in /src/bzflag/ of the extracted source. Start by searching for "void RadarRenderer::render(SceneRenderer&" and you will come to this section:


void RadarRenderer::render(SceneRenderer& renderer, bool blank, bool observer)
{
  RenderNode::resetTriangleCount();

  const float radarLimit = BZDBCache::radarLimit;
  if (!BZDB.isTrue("displayRadar") || (radarLimit <= 0.0f)) {
    triangleCount = 0;
    return;

First, look at this line from above:


  const float radarLimit = BZDBCache::radarLimit;

Change that line to this:


  float test = BZDBCache::radarLimit;

Below that, you will see this line:


  if (!BZDB.isTrue("displayRadar") || (radarLimit <= 0.0f)) {

Change that line to this:


  if(test<=0.0) {

Next, you will see this line:


    triangleCount = 0;

Change that line to this:


    test = BZDB.eval(StateDatabase::BZDB_WORLDSIZE);

The next line you see is this:


    return;

Change it to this (all one, single line):


    BZDB.setFloat(StateDatabase::BZDB_RADARLIMIT, BZDB.eval(StateDatabase::BZDB_WORLDSIZE));

On the next line, you will see this:

Directly below the "}" (vertically aligned), add this line:


  const float radarLimit = test;

So that the two lines together look like this:


  } 
  const float radarLimit = test;

The entire edit should like this:


void RadarRenderer::render(SceneRenderer& renderer, bool blank, bool observer)
{
  RenderNode::resetTriangleCount();

  float test = BZDBCache::radarLimit;
  if(test<=0.0) {
    test = BZDB.eval(StateDatabase::BZDB_WORLDSIZE);
    BZDB.setFloat(StateDatabase::BZDB_RADARLIMIT, BZDB.eval(StateDatabase::BZDB_WORLDSIZE));
  }
  const float radarLimit = test;
  // render the frame

Save the file, compile your client, and you're done. To view Phasmophage's original instructions, read his comment to "HOWTO: See Invisible Bullets and Actual Colors on Radar" at the blog Cheating BZFlag.

As always...

Have fun!

See Invisible Bullets and Actual Colors on Radar

2007-07-27T22:38:00.000-07:00

By: Phasmophage

You may recall our previous post about being able to see Stealth tanks on radar. That's useful, we can do more to make ouur radar even more powerful. With this tip from Phasmophage, we can add the ability to see Invisible Bullets and see the actual tank colors of tanks when we have the Colorblindness flag.

For this, we're revisiting RadarRenderer.cxx in /src/bzflag/ of the extracted source. Search for "if (shot && (shot->getFlag() !=" and you will find this line:


        if (shot && (shot->getFlag() != Flags::InvisibleBullet || iSeeAll)) {

Remove "&& (shot->getFlag() != Flags::InvisibleBullet || iSeeAll)" so that the edited line looks like this:


        if (shot) {

Look at this entire section now (includes edited line from above):


        if (shot) {
          const float *shotcolor;
          if (coloredShot) {
            if (myTank->getFlag() == Flags::Colorblindness)
              shotcolor = Team::getRadarColor(RogueTeam,rabbitMode);
            else
              shotcolor = Team::getRadarColor(player->getTeam(),rabbitMode);
            const float cs = colorScale(shot->getPosition()[2], muzzleHeight);

Notice the fourth line in particular:


            if (myTank->getFlag() == Flags::Colorblindness)

Let's remove the "== Flags::Colorblindness" so that the line now reads like this:


            if (myTank->getFlag())

Next, remove this line:


              shotcolor = Team::getRadarColor(RogueTeam,rabbitMode);

... and this:


            else

... so that the modified section should now read like this:


        if (shot) {
          const float *shotcolor;
          if (coloredShot) {
            if (myTank->getFlag())
              shotcolor = Team::getRadarColor(player->getTeam(),rabbitMode);
            const float cs = colorScale(shot->getPosition()[2], muzzleHeight);

Save the file, compile your client, and you're done! To view Phasmophage's original instructions, take a look at his comment to "HOWTO: Reverse While Sealed with Oscillation Overthruster" at the blog Cheating BZFlag as well as the update comment to the post, "HOWTO: See Invisible Bullets and Actual Colors on Radar".

As always...

Have fun!

Always See Actual Tank Colors

2007-07-27T22:08:00.000-07:00

By: Phasmophage

Here's an edit that will allow you to see the actual tank color of players even if they have Masquerade and/or if you have Colorblindness. For this, we will go to playing.cxx in /src/bzflag/ of the extracted source. Search for "const bool colorblind = (myTank->getFlag()", and you will come to this section:


          const bool colorblind = (myTank->getFlag() == Flags::Colorblindness);
          player[i]->addShots(scene, colorblind);

          TeamColor effectiveTeam = RogueTeam;
          if (!colorblind){
            if ((player[i]->getFlag() == Flags::Masquerade)
                && (myTank->getFlag() != Flags::Seer)
                && (myTank->getTeam() != ObserverTeam)) {
              effectiveTeam = myTank->getTeam();
            }
            else {
              effectiveTeam = player[i]->getTeam();
            }
          }

          const bool inCockpt  = ROAM.isRoaming() && !devDriving &&

Look at the first line. Replace "(myTank->getFlag() == Flags::Colorblindness);
player[i]->addShots(scene, colorblind)" with "false" so that the edited line looks like this:


          const bool colorblind = false;

Next, look at the line "TeamColor effectiveTeam = RogueTeam;". Replace "RogueTeam" with "player[i]->getTeam()" so that the edited line looks like this:


          TeamColor effectiveTeam = player[i]->getTeam();

Remove the lines between the line above and "const bool inCockpt = ROAM.isRoaming() && !devDriving &&" so that the section will look like this:


          TeamColor effectiveTeam = player[i]->getTeam();
   
          const bool inCockpt  = ROAM.isRoaming() && !devDriving &&

The entire edited section should now look like this:


          const bool colorblind = false;
          player[i]->addShots(scene, colorblind);

          TeamColor effectiveTeam = player[i]->getTeam();
   
          const bool inCockpt  = ROAM.isRoaming() && !devDriving &&

As Phasmophage said it, "This should color masqueraded tanks correctly, and take out some of the effects of colorblindness."

Save the file, compile your new client, and you're done. To view Phasmophage's original instructions, read his comment to "HOWTO: Reverse While Sealed with Oscillation Overthruster" from the blog Cheating BZFlag.

And,...

Have fun!

Reverse While Sealed with Oscillation Overthruster

2007-07-27T21:08:00.000-07:00

By: Phaz

Tired of not being able to reverse into a building with your Oscillation Overthruster (OO) flag? If you poke out of a building to take a shot, can only back into the building by jumping backward which leaves you vulnerable. Or, let's say that you are sealed in a thin wall. If you want to backtrack, you will have to leave the safety of the building to turn around.

No longer!

Thanks to this tip from Phaz, you can back up while sealed with OO! Now you can pull out, snipe your shot, and simply back up into the safety of the building (or other obstacle where you can be sealed). That is, you are no longer limited to driving only in the forward direction.

For this edit, we are going to open LocalPlayer.cxx in /src/bzflag/ of the extracted source. First let's edit the sections that prevent us from being able to back up while sealed. Search for "if (expelled && phased)", and you will this section:


  if (expelled && phased)
    expelled = (obstacle->getType() == WallObstacle::getClassName() ||
  obstacle->getType() == Teleporter::getClassName() ||
  (getFlag() == Flags::OscillationOverthruster && desiredSpeed < 0.0f &&
   p[2] == 0.0f));
  return obstacle;

Remove The following from above:

                                                                
                                                                  ||
  (getFlag() == Flags::OscillationOverthruster && desiredSpeed < 0.0f &&
   p[2] == 0.0f));

The section should now read like this:


  if (expelled && phased)
    expelled = (obstacle->getType() == WallObstacle::getClassName() ||
  obstacle->getType() == Teleporter::getClassName());
  return obstacle;

Next, search for "if (expelled && phased)" again, and you will find this section:


  if (expelled && phased)
    expelled = (obstacle->getType() == WallObstacle::getClassName() ||
  obstacle->getType() == Teleporter::getClassName() ||
  (hasOOflag && desiredSpeed < 0.0f && p[2] == 0.0f));

  if (obstacle != NULL) {

Remove the following from above:


                                                                 ||
  (hasOOflag && desiredSpeed < 0.0f && p[2] == 0.0f));

The section should now read like this:


if (expelled && phased)
  expelled = (obstacle->getType() == WallObstacle::getClassName() ||
              obstacle->getType() == Teleporter::getClassName());

if (obstacle != NULL) {

Lastly, search for "oscillation overthruster tank in building can't" and you will find this section:


  else if (fracOfMaxSpeed < -0.5f) fracOfMaxSpeed = -0.5f;

  // oscillation overthruster tank in building can't back up
  if (fracOfMaxSpeed < 0.0f && getLocation() == InBuilding &&
      flag == Flags::OscillationOverthruster) {
    fracOfMaxSpeed = 0.0f;
  }

  // boost speed for certain flags

Let's remove the portion about not being able to back up in a building so that the edited section now reads like this:


  else if (fracOfMaxSpeed < -0.5f) fracOfMaxSpeed = -0.5f;

  // boost speed for certain flags

Save the file, compile your new client, and you're done! For Phaz's original instructions, see his comment to "HOWTO: Drop Bad Flags Instantly"at Cheating BZFlag.

Keep these tips rolling in! And as always...

Have fun!

Respawn Instantly

2007-07-27T20:27:00.000-07:00

Brought to you by blogger, Someone

Someone actually brought this to us a while back, and I apologize for taking so long to post it. Anyway, here's a tip that will allow you to respawn instantly after exploding. In LocalPlayer.cxx (in /src/bzflag/ of the extracted source), search for "else if (location == Exploding)" and you will find this section:


    } else if (location == Exploding) {
      // see if explosing time has expired
      if (lastTime - getExplodeTime() >= BZDB.eval(StateDatabase::BZDB_EXPLODETIME)) {
        dt -= float((lastTime - getExplodeTime()) - BZDB.eval(StateDatabase::BZDB_EXPLODETIME));
        if (dt < 0.0f) {
          dt = 0.0f;
        }
        setStatus(PlayerState::DeadStatus);
        location = Dead;
        if (isAutoPilot()) {
          CMDMGR.run("restart");
        }
      }

      // can't control explosion motion
      newVelocity[2] += BZDBCache::gravity * dt;
      newAngVel = 0.0f; // or oldAngVel to spin while exploding
    } else if ((location == OnGround) || (location == OnBuilding) ||

First, let's look at the first through tenth lines from above:


    } else if (location == Exploding) {
      // see if explosing time has expired
      if (lastTime - getExplodeTime() >= BZDB.eval(StateDatabase::BZDB_EXPLODETIME)) {
        dt -= float((lastTime - getExplodeTime()) - BZDB.eval(StateDatabase::BZDB_EXPLODETIME));
        if (dt < 0.0f) {
          dt = 0.0f;
        }
        setStatus(PlayerState::DeadStatus);

Let's remove the second through seventh lines so that it now reads like this:


    } else if (location == Exploding) {
      setStatus(PlayerState::DeadStatus);

Next, notice this section:


 setStatus(PlayerState::DeadStatus);
 location = Dead;
 if (isAutoPilot()) {
   CMDMGR.run("restart");

Let's remove "location = Dead;" and "if (isAutoPilot()) {". Below the line "location = Dead;", add the following:


      LocalPlayer *myTank = LocalPlayer::getMyTank();

Below that line, add this line:


      myTank->setJumpPressed(false);

The above edits should now read like this:


      setStatus(PlayerState::DeadStatus);
      LocalPlayer *myTank = LocalPlayer::getMyTank();
      myTank->setJumpPressed(false);      
      CMDMGR.run("restart");

Next, notice this section:


          CMDMGR.run("restart");
        }
      }

      // can't control explosion motion
      newVelocity[2] += BZDBCache::gravity * dt;
      newAngVel = 0.0f; // or oldAngVel to spin while exploding
    } else if ((location == OnGround) || (location == OnBuilding) ||

Let's remove the lines between "CMDMGR.run("restart");" and " } else if ((location == OnGround) || (location == OnBuilding) ||" so that the section now reads like this:


      CMDMGR.run("restart");
    } else if ((location == OnGround) || (location == OnBuilding) ||

All of the above edits should now look like this:


    } else if (location == Exploding) {
      setStatus(PlayerState::DeadStatus);
      LocalPlayer *myTank = LocalPlayer::getMyTank();
      myTank->setJumpPressed(false);      
      CMDMGR.run("restart");
    } else if ((location == OnGround) || (location == OnBuilding) ||

When you are finished, compile your client and you're done. To view Someone's original instructions, read his comment to "HOWTO: Drop Bad Flags Instantly" at the original blog, Cheating BZFlag.

As always...

Have fun!

Drop Bad Flags Like Regular Flags

2007-07-27T18:47:00.000-07:00

By: Phaz

You may recall our earlier post about how to how to drop bad flags instantly. With that edit, you drop a bad flag as soon as you pick it up. You may not always want to do that especially on servers that do not allow players to drop bad flags since you may bring suspicion to yourself.

TIP: If you are not interested in cheating... On servers where dropping bad flags is not allowed, you can usually take advantage of the drop flag after pausing feature of BZFlag to drop your bad flag. Simply pause, and your flag will drop after a few seconds.

As an alternative to dropping bad flags instantly, Phaz has a simple edit for us that will allow a player to drop a bad flag like a regular flag. For this, we are going to edit clientCommands.cxx in /src/bzflag of the extracted source. Search for "flag->endurance != FlagSticky" and you will find this section:


    if ((flag != Flags::Null) && !myTank->isPaused() &&
        (flag->endurance != FlagSticky) && !myTank->isPhantomZoned() &&
        !(flag == Flags::OscillationOverthruster &&
          myTank->getLocation() == LocalPlayer::InBuilding)) {
      serverLink->sendDropFlag(myTank->getPosition());

In particular, notice the second line:


        (flag->endurance != FlagSticky) && !myTank->isPhantomZoned() &&

Remove "(flag->endurance != FlagSticky) &&" so that the line now reads like this:


        !myTank->isPhantomZoned() &&

Save the file, compile the client, and you're done! To see Phaz's original instructions, read his comment to HOWTO: Drop Bad Flags Instantly at Cheating BZFlag. As always...

Have fun!

Drop Bad Flags Instantly

2007-07-27T18:29:00.000-07:00

By: Lord Jesus

Bad flags are annoying, are they not? This is especially true in situations such as grabbing Jamming when your opponent has Cloaking. And those time limits! On servers with bad flag drop such as 15 seconds or more, waiting can be ever so dull. Wide Angle isn't so awfully bad if you get used being able to utilize it; but, let's face it; there are certainly other more desirable flags.

Here's an edit that will allow you to drop bad flags instantly even on servers that do not allow dropping of bad flags (an added bonus). Most players probably won't notice; however, there is a chance that the more experienced players might very well notice -- even if after a while -- as well as administrators especially if they're already monitoring you out of suspicion.

Open LocalPlayer.cxx in the /src/bzflag/ directory of the extracted source, and find the following lines:


  // drop bad flag if timeout has expired
  if (!isPaused() && dt > 0.0f && World::getWorld()->allowShakeTimeout() &&
      getFlag() != Flags::Null && getFlag()->endurance == FlagSticky &&
      flagShakingTime > 0.0f) {
    flagShakingTime -= dt;
    if (flagShakingTime <= 0.0f) {
      flagShakingTime = 0.0f;
      server->sendDropFlag(getPosition());

First, look at the second line:


  if (!isPaused() && dt > 0.0f && World::getWorld()->allowShakeTimeout() &&

Let's remove "World::getWorld()->allowShakeTimeout() &&" so that it reads like this:


  if (!isPaused() && dt > 0.0f &&

Next, let's look at the fifth line:


    flagShakingTime -= dt;

Let's change "-= dt" to "= 0.0f" so that the line reads like this:


    flagShakingTime = 0.0f;

The above will allow you to drop bad flags instantly on servers that allow for dropping of bad flags. To be able to drop flags on servers that don't allow dropping, we need to edit elsewhere. Take note, however, that experienced players will most likely notice your dropping bad flags if you are playing on a server that doesn't allow it. To add the ability, find the following lines:


  // if it's bad then reset countdowns and set antidote flag
  if (getFlag() != Flags::Null && getFlag()->endurance == FlagSticky) {
    if (World::getWorld()->allowShakeTimeout())
      flagShakingTime = World::getWorld()->getFlagShakeTimeout();

Look at the third line:


    if (World::getWorld()->allowShakeTimeout())

Remove "->allowShakeTimeout()" so that it reads like this:


    if (World::getWorld())

Next, let's look at the fourth line:


      flagShakingTime = World::getWorld()->getFlagShakeTimeout();

Replace "= World::getWorld()->getFlagShakeTimeout();" with "= 0.05f;" so that it reads like this:


      flagShakingTime = 0.05f;

I originally tried the number to "0.0f". When I tested it on my server not allowing bad flag dropping, and no win limit, it didn't work; I picked up a bad flag and it didn't drop. So, 0.05f "works". All of this tip works even if there are easier and/or more efficient ways of accomplishing the same ends :)

When you're finished, save your file, compile your new client, and...

Have fun!

Speed Hacking

2007-07-27T02:38:00.000-07:00

Brought to you by: Felipe

Here are some tips that will allow you to get the most of your tank's speed without having to depend on the high speed flag. You can optionally add quick turn to your tank, as well. Even without extreme speed, and handful of servers may kick you. Most won't at the time of this post. A few more servers may kick you for extreme speed. Nevertheless, you will enjoy always being able to chase down other tanks...

Open LocalPlayer.cxx in /src/bzflag/ of the extracted source. With your favorite text editor, find the following lines:


 // boost speed for certain flags
 if (flag == Flags::Velocity) {
   fracOfMaxSpeed *= BZDB.eval(StateDatabase::BZDB_VELOCITYAD);

Look at the first line. Remove the "== Flags::Velocity" so that this section reads like this:


 // boost speed for certain flags
 if (flag) {
   fracOfMaxSpeed *= BZDB.eval(StateDatabase::BZDB_VELOCITYAD);

This will give you high speed regardless of flag save Thief and Burrow. Additionally, you will see further down these lines:


  } else if ((flag == Flags::Burrow) && (getPosition()[2] < 0.0f)) {
    fracOfMaxSpeed *= BZDB.eval(StateDatabase::BZDB_BURROWSPEEDAD);

You can change "BZDB_BURROWSPEEDAD" to "BZDB_VELOCITYAD" so that the lines read like this:


  } else if ((flag == Flags::Burrow) && (getPosition()[2] < 0.0f)) {
    fracOfMaxSpeed *= BZDB.eval(StateDatabase::BZDB_VELOCITYAD);

This will give you high speed with Burrow. You can also play around some of these variables. For example, I substituted "BZDB_BURROWSPEEDAD" and "BZDB_VELOCITYAD" with "BZDB_THIEFVELAD" so that I could drive at the speed of Thief on my own server. Some servers will undoubtedly kick you for driving too fast when you drive at Thief speed without Thief... but then, some won't :)

For EXTREME speed, find the following lines:


 // can't go faster forward than at top speed, and backward at half speed
 if (fracOfMaxSpeed > 1.0f) fracOfMaxSpeed = 1.0f;
 else if (fracOfMaxSpeed < -0.5f) fracOfMaxSpeed = -0.5f;

Change the numbers so that the section now reads like this:


 // can't go faster forward than at top speed, and backward at half speed
 if (fracOfMaxSpeed > 0.0f) fracOfMaxSpeed = 9.0f;
 else if (fracOfMaxSpeed < 0.0f) fracOfMaxSpeed = -9.0f;

Again, play around with the numbers to find a speed that you like. Naturally, you will stick out like a sore thumb when you drive so unbelievably faster than everyone else. Hehehe...

For the original instructions, see Felipe's comments to Flying Without Wings & Extended Jumping at the original Cheating BZFlag blog. When you're finished, save the file, compile your new client, and ...

Have fun!

Quick Turn Always

2007-07-27T02:22:00.000-07:00

Brought to you by: Felipe

Here's a simple edit that will allow you to have Quick Turn at all times without the Quick Turn Flag. Find the following lines of LocalPlayer.cxx in the /src/bzflag/ directory of the extracted source:


  // boost turn speed for other flags
  if (flag == Flags::QuickTurn) {

Remove "== Flags::QuickTurn" so that the lines read like this:


  // boost turn speed for other flags
  if (flag) {

For the original instructions, see Felipe's comments to Flying Without Wings & Extended Jumping at the original Cheating BZFlag blog. When you're finished, save the file, compile your new client, and ...

Have fun!

Fly Without Wings & Improved Jumping

2007-07-27T01:50:00.000-07:00

Brought to you by: Felipe

Scenario: You and another tank are jumping and shooting at one another. Wouldn't it be nice to be able to slide in one more jump in mid air? Now you can! You can 1-up those annoying players who keep coming at you with Wings. What's cool is that you are not limited to any number of jumps, and this can be especially useful on servers with Wings flap limits ;) But, this tip doesn't stop there...

You can jump no matter what -- regardless of whether or not the server allows jumping (the good folks at Hepcat will love you for it, hehehe...), or if you have the Burrow flag, or even if you have the No Jumping flag! When Burrowed, the jump isn't instantaneous, so you will need to press and hold jump to get airborne. And, it doesn't matter if you are sealed in a building with Oscillation Overthruster. Now, you can jump from inside a building to pick off players who think that they are safe by staying top of your building . Muwahahahaha! >:)

Not only all of that, but you can also control your tank in the air while jumping. And, you can fly regardless of what flag you have! Imagine being able to fly high to target a Winged tank with your guided missile... or shockwave in air. Or, on a CTF server with no jumping allowed, you can place your team's flag on top of a pillar since the other team won't be able to jump up to get it >:) The possibilities are practically endless... See the comments to this post to see how this was updated.

We're going back to LocalPlayer.cxx for this. You can find it in /src/bzflag/ after you have extracted the source. Use your favorite text editor's search function to locate "can't jump while burrowed". You will come across this section:


  FlagType* flag = getFlag();

  // can't jump while burrowed
  if (getPosition()[2] < 0.0f) {
    return;
  }

  if (flag == Flags::Wings) {
    if (wingsFlapCount <= 0) {
      return;
    }
    wingsFlapCount--;
  } else if ((location != OnGround) && (location != OnBuilding)) {
    // can't jump unless on the ground or a building
    if (flag != Flags::Wings)
      return;
    if (wingsFlapCount <= 0)
      return;
    wingsFlapCount--;
  } else if ((flag != Flags::Bouncy) &&
      ((flag != Flags::Jumping && !World::getWorld()->allowJumping()) ||
       (flag == Flags::NoJumping))) {
    return;
  }

  // add jump velocity (actually, set the vertical component since you

Let's do away with most of this section so that it reads like this:


FlagType* flag = getFlag();

// add jump velocity (actually, set the vertical component since you

The above allows us to jump whenever we want. Now, let's add some ability steer in air. Search for "can't control motion in air unless have wings", and you will come to a section that looks like this:


    // can't control motion in air unless have wings
    if (getFlag() == Flags::Wings) {
      float speed = desiredSpeed;

Specifically, let's look at the second line of the above:


if (getFlag() == Flags::Wings) {

Let's remove "== Flags::Wings" so that the line reads like this:


if (getFlag()) {

Save the file, compile your new client, and you're done. Many thanks to Felipe for sharing this one with us ;) You can view the original instructions in the comments of the Cheating BZFlag blog post, The Infamous BZFlag F5 Cheat. Please take a look at our previous posts if you haven't already done so. And, let's keep those tips rolling in >:) As always...

Have fun!

TIP: The Infamous BZFlag F5 Cheat

2007-07-27T01:47:00.000-07:00

By: Lord Jesus

Grab yourself a copy of the 2.0.4 version of BZFlag, and use F5 -- the screenshot function -- to insert artificial lag. One method is to press and hold F5 to insert the lag. This is a great technique for dodging bullets and capturing another team's flag.

You can also press and hold F5 to get to other places you normally couldn't get to... like the other side of a wall. Again, this is if you you use the older 2.0.4 version of BZFlag. The delay for taking a screenshot until you release F5 was "fixed" in version 2.0.8. You can read about how it works in this discussion:

my.bzflag.org/bb/

"The basic case is this: the tank moves along velocity vector, then collisions are checked. If the tank has moved too far along in one time step, it is now inside (or on the other side(the F5 cheat!)) of the object it 'collided' with." [emphasis added]

It's briefly mentioned here, too:

http://www.answers.com/topic/bzflag

"F5: To F5 is to take a screenshot of BZFlag, which also creates a small lagspike and makes your tank unhittable for a short interval of time."

As you can imagine, this has been around for quite a while. It's posted here at BZFlag Cheat just in case you didn't get an opportunity to take advantage of it previously >:) Some more information about the F5 technique is easy to find with your favourite search engine. Here's an example:

Google search

Keep in mind that it is not entirely undetectable especially among experienced players. Use it wisely ;) Here's an example of a player, soxs, who got banned for it:

http://gu.bzleague.com/index.php?link=shame

So, now you can enjoy enhanced gaming without having to modify or add a single line of code to your client! To control disk space, don't forget to empty your screenshots folder when you're finished playing. And as always...

Have fun!

Shoot While Sealed with Oscillation Overthruster

2007-07-27T01:34:00.000-07:00

By: Lord Jesus

Imagine that you have Oscillation Overthruster (OO) and you're chasing another player with OO. The other player dodges you by hiding in a building or some other structure (for example, while playing Hide-N-Seek Hills). You can go after the player to maintain your chase; however, what if the player stops while you're both sealed? You can't shoot if you're both sealed. Moreover, you can almost imagine the other player saying something like, "Haha! You can't shoot me here!"

Now, you can have the last laugh as the other tank goes Kaboom! Thrills and laughs abound now that buildings are no longer safe havens for other players with OO. But, why stop there? Snipe other players from the safety of buildings...

To do that, we're going to visit LocalPlayer.cxx (in /src/bzflag/ of the extracted source).

Use the search feature of your favorite text editor and look for "case Exploding". You will come to a section like this:


case Exploding:
  firingStatus = Deceased;
  break;
case InBuilding:
  firingStatus = (getFlag() == Flags::PhantomZone) ? Zoned : Sealed;
  break;
default:
  if (isPhantomZoned())

Let's do away with the "case InBuilding" section so that the modified file now looks like this:


case Exploding:
  firingStatus = Deceased;
  break;
default:
  if (isPhantomZoned())

Next, search for "make sure we're allowed to shoot". You will come to a section that looks like this:


// make sure we're allowed to shoot
if (!isAlive() || isPaused() ||
    ((location == InBuilding) && !isPhantomZoned())) {
  return false;
}

Let's do a quick edit so that it now looks like this:


// make sure we're allowed to shoot
if (!isAlive() || isPaused()) {
  return false;
}

Note that the above edit will only allow you to be able to shoot while sealed in a building; it will not affect your shooting while Phantom Zoned.

Save your new file, and you're done. In case you haven't already checked, take a look at the previous HOWTO posts for more tips. When you're finished, compile your client and...

Have fun!

See Cloaked Tanks

2007-07-27T01:22:00.000-07:00

By: Lord Jesus

Have you enjoyed being able to see those pesky Stealth tanks on your radar? Be sure to read the previous posts in case you've missed them :)

Anyway, here's a simple trick that will allow you to see cloaked tanks. As a note, this will not affect lasers; lasers will still pass through cloaked tanks. You will be able to see them, though. Think of it as training wheels until you get better at using your radar :)

I assume that you have already downloaded the source and have extracted the source from the tarball. Enter the extracted directory and go to the /src/bzflag/ directory and open Player.cxx with your favorite text editor. Use the search feature of your editor (e.g., ctrl+f for some text editors) and search for "cloak". The first thing you will find is:


 // set the alpha target
 if (effectFlag == Flags::Cloaking) {
   alphaTarget = 0.0f;
 } else {
   alphaTarget = 1.0f;
 }

Notice the line "alphaTarget = 0.0f;". Let's change 0.0f to 0.5f so that the line reads like this:


alphaTarget = 0.5f;

The effect will be that it is slightly translucent but not as much as zoned tanks (i.e., tanks with the Phantom Zone flag which are at 0.25f). Alternatively, you can use 1.0f instead of 0.5f.

Moving on. Search for "cloak" again. You now come to a section like this:


 }

 // is this tank fully cloaked?
 const bool cloaked = (flagType == Flags::Cloaking) && (color[3] == 0.0f);

 if (cloaked && !seerView) {
   return; // don't draw anything
 }

 // setup the visibility properties

Let's remove the check for seeing if a tank is cloaked and not drawing anything if it is. The newly edited section should like this:


 }

 // setup the visibility properties

Save the file, compile your client, and . . .

Have fun!

See STEALTH Tanks on Radar

2007-07-27T01:09:00.000-07:00

By: Lord Jesus

Have you enjoyed the Classic God Mode modification, yet? In case you haven't had a chance to try it out, read further down this blog to the previous HOWTO edition. If "god mode" isn't your thing, then you might find being able to see Stealth tanks on radar to be quite handy. Remember to keep it subtle; don't make yourself obvious. For example, if a Stealth tank is on the other side of a large wall, most players (particularly, the Stealth player) will know that you don't "coincidentally" shoot Super Bullets straight down the direction to the Stealth tank. Remember to pretend to be "surprised" when Stealth tank comes into view before you blow him up to kingdom come.

Being able to see stealth on your radar is very easy in and of itself. In fact, it doesn't require any additional lines of code. More elaborate adaptations of this modification, such as stealth blinking on radar, will in fact require some code; however, we're just going to stick to the simple trick for the purpose of this blog entry. We'll come back to it in more detail with various options including blinking on radar, toggle mode (to turn on/off being able to see stealth), selective stealth radar mode (in case you want to target only specifically annoying players), and so on. So, stay tuned for more later on.

After you unpack the source tarball, you will find the file "RadarRenderer.cxx" in the extracted "/bzflag-2.0.X/src/bzflag/" directory (where "X" is version number such as in version 2.0.8). Use your favorite text editor to open "RadarRenderer.cxx" and use your Find feature (e.g., ctrl+f in some graphic editors) to search for "stealth". You will come across some lines that look like this:


     }
     if (!player->isAlive() &&
         (!useTankModels || !observer || !player->isExploding())) {
       continue;
     }
     if ((player->getFlag() == Flags::Stealth) &&
         (myTank->getFlag() != Flags::Seer)) {
       continue;
     }

     const float* position = player->getPosition();

All we need to do is remove the portion that indicates that we should not be able to see Stealth if we don't have the Seer flag. When you are finished, the revised lines should look like this:


     }
     if (!player->isAlive() &&
         (!useTankModels || !observer || !player->isExploding())) {
       continue;
     }

     const float* position = player->getPosition();

Save the file, compile you client, and...

Have fun!

Classic God Mode

2007-07-26T21:15:00.000-07:00

By: Lord Jesus

Ever consider tinkering with "god mode" but just didn't quite know how? Well, you've come to the right place! With Classic God Mode, you will be invulnerable to shots, shock waves, guided missiles, lasers, steamroller, world weapons and so on. You will even be able to be like Jesus and drive on water. Tired of having your good flags stolen by Thief tanks? That will no longer be a problem either. A shortcoming, however, are that you will still be vulnerable to server /kill commands. That means admins can still /kill you, you will still blow up for killing teammates, and you will still blow up if you are a rogue and another rogue gets hit with genocide on a server with rogue genocide. Be sure to check out a later post about instant respawn ;)

Let's get started. After you've extracted the source tarball, navigate to the extracted directory. Once you're there, navigate on to the "/src/bzflag" directory. In that directory, you will find the file "playing.cxx". We'll work on some modifications to that file. Open your favorite text editor if you haven't already, open the file, and let's get going...

First, you may want to open a second editor and paste something like the following to it:


//skip this if alive
if (myTank->isAlive()) return;

We'll use it for quick pasting later on.

Also, I recommend backing up your original playing.cxx file for later use. Alternatively, you can extract a copy of the original file from your original tarball.

Now that you've got "playing.cxx" open it's time for a few changes. Use you editors "Find" feature (e.g., ctrl+f as with some graphic editors) to search for "see if" in the text of the file until you come to this section:


  // see if i've been shot
  const ShotPath* hit = NULL;

Hmmm... see if I've been shot? I'd rather not, if you don't mind >:) Let's do our paste action again so that the lines now read:


  // see if i've been shot
  // skip this if i'm alive
  if (myTank->isAlive()) return;
  const ShotPath* hit = NULL;

Next...


  // if not dead yet, see if i'm sitting on death
  else if (myTank->getDeathPhysicsDriver() >= 0) {

If not dead yet, then let's keep it that way. Let's paste again:


  // if not dead yet, see if i'm sitting on death
  // skip this if i'm alive
  if (myTank->isAlive()) return;
  else if (myTank->getDeathPhysicsDriver() >= 0) {

We'll continue making changes as we move along...


  // if not dead yet, see if i've dropped below the death level
  // skip this if i'm alive
  if (myTank->isAlive()) return;
  else if ((waterLevel > 0.0f) && (myTank->getPosition()[2] <= waterLevel)) {

And...


  // if not dead yet, see if i got run over by the steamroller
  // skip this if i'm alive
  if (myTank->isAlive()) return;
  else {

You're going to run across a few other lines pertaining to things such as guided missile. Keep searching past these entries, and you will find more "if not dead yet, see if ..." lines. Simply modify the lines as we've done above, you should be good to go on those.

Ah, you should be at the end of the document. You can run through it if you want to make sure that you hit all of the right spots :)

To be double sure, you can also search for "genocide". If you search from the beginning, keep using your Find Next feature, and you will find the line:


      // blow up if killer has genocide flag and i'm on same team as victim
      // (and we're not rogues, unless in rabbit mode)
      if (human && killerPlayer && victimPlayer && victimPlayer != myTank &&

Now that looks intriguing. Let's add our own little touch to that, shall we?


      // blow up if killer has genocide flag and i'm on same team as victim
      // (and we're not rogues, unless in rabbit mode)
      // skip this if i'm alive
      if (myTank->isAlive()) return;
      if (human && killerPlayer && victimPlayer && victimPlayer != myTank &&

Nothing like ignoring a teammate getting sacked with Genocide, huh? Keep in mind that some servers have rogues genocide. If you are playing on one of these servers as a rogue, then you will still get geno'd since the rogue genocide is handled by the server and sent to the client as a server kill message. Playing as a team color will eliminate that little problem.

Magnifico!

After that, save the file, compile your new client, and ...

Have fun!