Grand Theft Auto: San Andreas/Game Mechanics and Glitches/Phonecalls - Revision history

Tduva: /* List of Calls */

2016-01-09T15:34:43Z

List of Calls

← Older revision		Revision as of 15:34, 9 January 2016
Line 335:		Line 335:
	\| "Carl. It's me. The Truth. We got a date with destiny, man"		\| "Carl. It's me. The Truth. We got a date with destiny, man"
	\| $TORENO_TOTAL_PASSED_MISSIONS > 7 (Black Project)		\| $TORENO_TOTAL_PASSED_MISSIONS > 7 (Black Project)
	\| Mission Marker		\| Mission Marker/Unlock (Green Goo)
	\| style="background:lightgreen" \| MOB_VEG(1)		\| style="background:lightgreen" \| MOB_VEG(1)
	\|-		\|-
Line 399:		Line 399:
	\| style="background:lightgreen" \| MOB_VEG(9)		\| style="background:lightgreen" \| MOB_VEG(9)
	\|-		\|-
	\| 38		\| style="font-weight:bold" \| 38
	\| Woozie?		\| Woozie?
	\| "Are we doing this heist or are you going soft on me again."		\| "Are we doing this heist or are you going soft on me again."
	\| $CASINO_TOTAL_PASSED_MISSIONS > 8 (Saint Mark's Bistro)~~,<br />$1384 == 0~~		\| $CASINO_TOTAL_PASSED_MISSIONS > 8 (Saint Mark's Bistro)
	\| Mission Marker		\| Mission Marker if $37 == 1 (Keycard acquired)
	\| style="background:lightgreen" \| MOB_VEG(10)		\| style="background:lightgreen" \| MOB_VEG(10)
	\|-		\|-
Line 409:		Line 409:
	\| Woozie?		\| Woozie?
	\| "Get back to the Four Dragons and we can get on with this thing!"		\| "Get back to the Four Dragons and we can get on with this thing!"
	\| $CASINO_TOTAL_PASSED_MISSIONS > 8 (Saint Mark's Bistro),<br />$37 == 1 (Keycard acquired)		\| $CASINO_TOTAL_PASSED_MISSIONS > 8 (Saint Mark's Bistro),<br />$1384 == 0 (call 38 taken without Keycard acquired),<br />$37 == 1 (Keycard acquired)
	\| Mission Marker		\| Mission Marker
	\| style="background:lightgreen" \| MOB_VEG(11)		\| style="background:lightgreen" \| MOB_VEG(11)

Tduva: /* Holding Calls */

2015-12-29T05:23:43Z

Holding Calls

← Older revision		Revision as of 05:23, 29 December 2015
Line 36:		Line 36:

	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).		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====		====Related Resources====

Tduva: /* Holding Calls */

2015-12-26T00:23:20Z

Holding Calls

← Older revision		Revision as of 00:23, 26 December 2015
Line 24:		Line 24:
	During the state of holding the call you can carry it through a lot of things that would normally cancel it:		During the state of holding the call you can carry it through a lot of things that would normally cancel it:
	* Driving a vehicle		* Driving a vehicle
	* Failing missions, going through cutscenes		* Failing missions, going through some cutscenes
	* Using most weapons		* Using most weapons
	** You can't aim and shoot properly, since aiming will immediately shoot		** You can't aim and shoot properly, since aiming will immediately shoot

Tduva: /* List of Calls */ Added call id info, small fix

2015-12-21T20:01:51Z

List of Calls: Added call id info, small fix

← Older revision		Revision as of 20:01, 21 December 2015
Line 61:		Line 61:

	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.		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.

	{\| class="wikitable sortable"		{\| class="wikitable sortable"
Line 381:		Line 383:
	\| style="background:lightgreen" \| MOB_VEG(8)		\| style="background:lightgreen" \| MOB_VEG(8)
	\|-		\|-
	\| 51		\| style="font-weight:bold" \| 51
	\| Leone		\| Leone
	\| "You won't be hearing from Mr. Rosenberg again."		\| "You won't be hearing from Mr. Rosenberg again."

Tduva: /* List of Calls */ Clarified mission unlocks

2015-12-15T17:40:59Z

List of Calls: Clarified mission unlocks

← Older revision		Revision as of 17:40, 15 December 2015
Line 59:		Line 59:

	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.		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.

	{\| class="wikitable sortable"		{\| class="wikitable sortable"
Line 300:		Line 302:
	\| "Son, get back to the ranch and I'll explain everything."		\| "Son, get back to the ranch and I'll explain everything."
	\| $TORENO_TOTAL_PASSED_MISSIONS > 0 (Monster)		\| $TORENO_TOTAL_PASSED_MISSIONS > 0 (Monster)
	\| ~~Highjack~~ Mission Marker		\| Mission Marker/Unlock (Highjack)
	\| style="background:gold" \| MOB_SF(8)		\| style="background:gold" \| MOB_SF(8)
	\|-		\|-
Line 307:		Line 309:
	\| "Here. Now. Don't screw around."		\| "Here. Now. Don't screw around."
	\| $TORENO_TOTAL_PASSED_MISSIONS > 1 (Highjack)		\| $TORENO_TOTAL_PASSED_MISSIONS > 1 (Highjack)
	\| Interdiction		\| Mission Marker/Unlock (Interdiction)
	\| style="background:gold" \| MOB_SF(9)		\| style="background:gold" \| MOB_SF(9)
	\|-		\|-

Tduva: /* List of Calls */

2015-12-11T01:44:27Z

List of Calls

Show changes

Tduva: /* Holding Calls */

2015-11-22T09:33:38Z

Holding Calls

← Older revision		Revision as of 09:33, 22 November 2015
Line 30:		Line 30:
	** 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)		** 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) when:		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 an interior
	* You're not in a vehicle		* You're not in a vehicle
	* You ~~must~~ currently be $ONMISSION=1 (so if you try to answer a held call with $ONMISSION=0, it will just cancel it)		* 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).		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).

Tduva: /* Related Resources */

2015-11-22T09:30:35Z

Related Resources

← Older revision		Revision as of 09:30, 22 November 2015
Line 37:		Line 37:
	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).		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).

	===Related Resources===		====Related Resources====
	* Holding calls is used for [[Grand Theft Auto: San Andreas/Game Mechanics and Glitches/Duping\|Duping]]		* Holding calls is used for [[Grand Theft Auto: San Andreas/Game Mechanics and Glitches/Duping\|Duping]]
	* [https://www.youtube.com/watch?v=nBfIiummlFs Video on how to hold calls in vehicles]		* [https://www.youtube.com/watch?v=nBfIiummlFs Video on how to hold calls in vehicles]

Tduva: /* Holding Calls */

2015-11-22T09:30:11Z

Holding Calls

← Older revision		Revision as of 09:30, 22 November 2015
Line 36:		Line 36:

	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).		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).

			===Related Resources===
			* Holding calls is used for [[Grand Theft Auto: San Andreas/Game Mechanics and Glitches/Duping\|Duping]]
			* [https://www.youtube.com/watch?v=nBfIiummlFs Video on how to hold calls in vehicles]

	==List of Calls==		==List of Calls==

Tduva: /* Answering/Cancelling phonecalls */

2015-11-22T09:27:53Z

Answering/Cancelling phonecalls

← Older revision		Revision as of 09:27, 22 November 2015
Line 9:		Line 9:

	==Answering/Cancelling phonecalls==		==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.		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.

Line 14:		Line 16:

	===Holding Calls===		===Holding Calls===
	Holding Action (default TAB) ~~will~~ hold a ~~ringing phonecall~~ until you let go of Action. This way you ~~can~~ keep ~~it ringing even when going into an interior (even though it might not actually be audibly ringing anymore)~~. ~~You can also use weapons~~ while ~~doing this~~, which ~~would normally cancel~~ the call~~. You can't actually answer it in an interior, but~~ you can carry it through ~~one and then answer~~ it ~~in an environment where you~~ can, e.g. ~~outdoors~~ or in a ~~cutscene.~~		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 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) when:
			* You're not in an interior
			* You're not in a vehicle
			* You must currently be $ONMISSION=1 (so if you try to answer a held call with $ONMISSION=0, it will just cancel it)

	~~You can also hold phonecalls in vehicles by keeping 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.		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).

	==List of Calls==		==List of Calls==