Two more uses of MAPSEC_NONE and mapSec field name
This commit is contained in:
parent
cf253062b9
commit
37ebfa40f9
1 changed files with 4 additions and 4 deletions
|
@ -43,7 +43,7 @@ struct MatchCallStruct1 {
|
|||
|
||||
struct MatchCallSubstruct2 {
|
||||
u16 flag;
|
||||
u8 v2;
|
||||
u8 mapSec;
|
||||
};
|
||||
|
||||
struct MatchCallStruct2 {
|
||||
|
@ -929,17 +929,17 @@ static u8 sub_81D171C(match_call_t matchCall)
|
|||
if (!FlagGet(matchCall.type2->v10[i].flag))
|
||||
break;
|
||||
}
|
||||
return matchCall.type2->v10[i].v2;
|
||||
return matchCall.type2->v10[i].mapSec;
|
||||
}
|
||||
|
||||
static u8 sub_81D1750(match_call_t matchCall)
|
||||
{
|
||||
return 0xd5;
|
||||
return MAPSEC_NONE;
|
||||
}
|
||||
|
||||
static u8 sub_81D1754(match_call_t matchCall)
|
||||
{
|
||||
return 0xd5;
|
||||
return MAPSEC_NONE;
|
||||
}
|
||||
|
||||
bool32 MatchCall_IsRematchable(u32 idx)
|
||||
|
|
Loading…
Reference in a new issue