ModdingRX/YimMenu
Archived
1
0
Fork 0
Code Actions Releases Activity

fix(Toxic): Don't use 0 as player id, make sure it's valid

Browse Source
This commit is contained in:
Yimura 2022-05-13 14:49:27 +02:00
parent 5fd3ef667d
commit 1bae411588
No known key found for this signature in database
GPG Key ID: 3D8FF4397E768682
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
BigBaseV2/src/util/toxic.hpp
View File

@ -13,7 +13,7 @@ namespace big::toxic
FIRE::ADD_OWNED_EXPLOSION(
PLAYER::GET_PLAYER_PED_SCRIPT_INDEX(to_blame),
pos.x, pos.y, pos.z,
(int)explosion_type,
explosion_type,
damage,
is_audible,
is_invisible,
@ -32,8 +32,8 @@ namespace big::toxic
{
const size_t arg_count = 22;
int64_t args[arg_count] = {
(int)eRemoteEvent::Bounty,
0, // doesn't matter of we set this to something else, the TRIGGER_SCRIPT_EVENT routine will set it to our player id anyways
static_cast<int64_t>(eRemoteEvent::Bounty),
self::id,
target,
0, // set by player or NPC?
amount,
@ -88,8 +88,8 @@ namespace big::toxic
{
constexpr size_t arg_count = 3;
int64_t args[arg_count] = {
(int)eRemoteEvent::ClearWantedLevel,
0,
static_cast<int64_t>(eRemoteEvent::ClearWantedLevel),
self::id,
*script_global(1893551).at(target, 599).at(510).as<int*>()
};