Difference between revisions of "Grand Theft Auto: San Andreas/Game Mechanics and Glitches/Phonecalls"

Latest revision as of 10:34, 9 January 2016

Phonecalls are triggered after certain events (often finishing a certain mission).

There are two different kinds of phonecalls:

• High-priorty calls have a recall delay of 20s before Badlands and 15s after finishing the mission Badlands. These calls are usually ones that unlock missions (Most Threads).
• Low-priority calls have a recall delay of 60s. These calls include e.g. the Catalina troll calls after CJ parts ways with her (MOB_RAN Thread).

The delay counts from the last time the game considered you busy, this includes being on a mission, receiving a phonecall, cancelling a ringing phone. So for example a high-priority call might come 15s after you finished the last mission or 15s after you last cancelled a call. Even though you can't receive phonecalls when you have a wanted level, it doesn't count towards the delay, so you can receive a phonecall directly after you loose your wanted stars.

Answering/Cancelling phonecalls

You can only receive calls (phone ringing) when you are not on a mission ($ONMISSION=0) and not in an interior.

The ringing phone counts as a small mission, setting $ONMISISON=1, which means you can't start any missions. Once the call is finished (either because you cancelled it or you accepted and finished it), it will set $ONMISSION=0 again.

You can cancel calls by shooting or getting into a vehicle, which will set $ONMISSION=0 after about 1.6 seconds (timed from between the "Press TAB to answer phone" dialog disappearing to mission markers re-appearing on the map, counted frames on video). So the effective delay after you cancelled a phonecall will be 16.6/21.6/61.6 seconds after you performed the action to cancel (e.g. shooting).

Holding Calls

Holding a call means sort of keeping it in the state of when you're about to answer it. You press and hold the Action key (default TAB) to hold a call, the same key you would press and then let go when normally answering a call, just that you don't let go but keep holding it, until you want to take or cancel the call.

To hold phonecalls in vehicles keep AltFire pressed as long as you are in a vehicle. You have to keep Action pressed as long as you are on foot, including the get in/out animations, but not if you are completely in a vehicle. So you should press Action and AltFire during the get in/out animations and can then let go of one of them accordingly. It might be safer to bind Action/AltFire to one key though, which is possible because one is for on foot and the other for vehicles. This way you only need to keep one button pressed during the entire time you want to hold a phonecall, including driving vehicles.

It is noteworthy that holding AltFire while on a bike will continuosly shoot if you have a MicroSMG or Tec9, which might be a problem and also prevents you from leaning down to go faster.

During the state of holding the call you can carry it through a lot of things that would normally cancel it:

• Driving a vehicle
• Failing missions, going through some cutscenes
• Using most weapons
  • You can't aim and shoot properly, since aiming will immediately shoot
  • You will keep shooting unless you move or switch weapons
  • Using a viewfinder (e.g. aiming with the Sniper Rifle or Rocket Launcher) seems to have the same effect as letting go of holding the call (answer or cancel it)

Letting go of holding the call will answer the call (CJ picks up the phone and the conversation starts, the call won't be available after that) only when:

• You're not in an interior
• You're not in a vehicle
• You're currently on $ONMISSION=1 (so if you try to answer a held call with $ONMISSION=0, it will just cancel it)

Otherwise it will just cancel the call immediately (but still set $ONMISSION=0, since even cancelling a ringing phone will do that, the call will still be available after that).

Problems with holding calls

You have to make sure that the button you use for holding calls actually works in all situations:

• Your keyboard may not support some buttons to be held at the same time. Example: Holding Shift and pressing a NumPad-number button lets go off Shift, even though you're still physicially holding it. However with disabling NumLock it works. This is just an example, it may be different for your setup.
• The game sometimes seems to remove keypresses when cancelling cutscenes. This appears to apply to all keys, however holding some keys will immediately recognize the keypress again after a fraction of a second, whereas all other keys just don't recognize the keypress anymore (until you let go and press it again). This can be important if you need to hold a call that starts ringing right after a cutscene. Shift (Left and Right) and mousebuttons seem to work best for this.

Perform thorough tests to make sure holding calls works with your setup:

• Receive and hold a call and perform all the actions you normally would, including everything you would do in a car like drive-by shooting. Then check if the call is still there. When you are using a regular (not $ONMISSION=0) call, you can easily tell if the call is still held by the mission markers not being there. This is to make sure that all keys you are using work with the key you use to hold the call.
• Practice all the dupes and setups.

Related Resources

• Holding calls is used for Duping
• Video on how to hold calls in vehicles

List of Calls

The following threads, which are started/stopped as the game progresses, are used to check for different groups of phonecalls (check delay in ms):

• MOB_LA1 (90)
• MOB_CAT (120)
• MOB_SF (150)
• MOB_VEG (180)
• MOB_LA2 (250)
• MOB_RAN (1000)
• MOB_GF (150)

Each thread checks independantly every x ms (as noted in the list above) if the recall time has passed and the prerequisites for calls are met. This means that if calls from different threads are available, calls can come in a somewhat random order, although calls from threads that are checked with a smaller delay probably have a higher chance of getting in first.

In the table the number behind the thread name (e.g. MOB_RAN(3)) is the order the calls are checked in that thread, which means you receive calls with a smaller number first if several are available. It doesn't necessarily mean that the calls will actually come in that order, since that depends on which ones are unlocked.

The mission name behind a given prerequisite shows the mission that the game expects to have been be passed.

This list is not necessarily complete (the MOB_GF thread hasn't been added yet). The prerequisites and results info of a call may not be entirely complete (which would basicially require posting the code in here), but the relevant stuff should mostly be in there.

If the Unlocks column says "Mission Marker/Unlock (Mission Name)" then the variable that is said if the call was answered is also checked for starting that mission, which means it doesn't just create the marker, but also actually unlocks the mission. If it doesn't say "Unlock", the call might not be responsible for unlocking the mission, however it might also mean that this call merely hasn't been checked for that yet.

The call IDs are taken from the mission script. Call IDs that are shown in bold are calls that usually come up in any% runs.