Difference between revisions of "SET CHAR AS MISSION CHAR"
Jump to navigation
Jump to search
(New page: {{Native |np=2 |p1t=integer |p1d=ped handle |p2t=boolean |p2d=true if mission char, false if not}} Before you can use any other SET_CHAR_ functions on a char you didn't create, you have t...) |
|||
| Line 3: | Line 3: | ||
Before you can use any other SET_CHAR_ functions on a char you didn't create, you have to set them as mission chars. | Before you can use any other SET_CHAR_ functions on a char you didn't create, you have to set them as mission chars. | ||
| − | So, for instance, if you get a random ped using | + | So, for instance, if you get a random ped using [[GET_RANDOM_CHAR_IN_AREA_OFFSET_NO_SAVE]], you first need to set that ped as a mission char before you can change any of their other flags. |
| − | + | Setting a char as a mission char is essentially the opposite of [[MARK_CHAR_AS_NO_LONGER_NEEDED]]. | |
Latest revision as of 01:13, 10 April 2009
| Number of parameters: 2 | ||
|---|---|---|
| Parameter # | Type | Description |
| 1. | integer | ped handle |
| 2. | boolean | true if mission char, false if not |
| Return value: | ||
| Type | Description | |
| None | ||
Before you can use any other SET_CHAR_ functions on a char you didn't create, you have to set them as mission chars.
So, for instance, if you get a random ped using GET_RANDOM_CHAR_IN_AREA_OFFSET_NO_SAVE, you first need to set that ped as a mission char before you can change any of their other flags.
Setting a char as a mission char is essentially the opposite of MARK_CHAR_AS_NO_LONGER_NEEDED.
