[Chdata]

Trying to make a rage not work in midair.

PHP Code:

public FF2_PreAbility(index, const String:plugin_name[], const String:ability_name[], slot, status, &enabled)
{
    if(plugin_name[0])
    {
        if(strcmp(this_plugin_name, plugin_name))
        {
            return;
        }
    }
    
    if (!strcmp(ability_name, "rage_gugnir"))
    {
        new iBoss = GetClientOfUserId(FF2_GetBossUserId(index));

        if (!g_bHasGugnir[iBoss] || !IsClientInGame(iBoss) || !IsPlayerAlive(iBoss) || !(GetEntityFlags(iBoss) & FL_ONGROUND))
        {
            enabled = false;
            return;
        }
    }

    return;
} 


I set enabled = false, but you can still mid-air rage and lose all your rage.

[93SHADoW]

Originally Posted by Chdata Trying to make a rage not work in midair. PHP Code: public FF2_PreAbility(index, const String:plugin_name[], const String:ability_name[], slot, status, &enabled) {     if(plugin_name[0])     {         if(strcmp(this_plugin_name, plugin_name))         {             return;         }     }          if (!strcmp(ability_name, "rage_gugnir"))     {         new iBoss = GetClientOfUserId(FF2_GetBossUserId(index));         if (!g_bHasGugnir[iBoss] || !IsClientInGame(iBoss) || !IsPlayerAlive(iBoss) || !(GetEntityFlags(iBoss) & FL_ONGROUND))         {             enabled = false;             return;         }     }     return; }  I set enabled = false, but you can still mid-air rage and lose all your rage.

return Plugin_Changed?

[Chdata]

the function prototype doesn't support actions.

[Wliu]

Ok, I'll check this out.

[friagram]

That forward has never been useful. Also you can not determine the order that forward is going to happen in each subplugin.
You could do something there though, where if they have ability x, you reduce their rage so the ability can't fire (not sure if there is a check between pre and post)

[Chdata]

All I did is refund rage.

[Wliu]

From just looking through the code it looks like the enabled check should be working (it's a simple if(!enabled) return; statement). So I guess that means...are you sure you're reaching the enabled = false line?

[friagram]

One of the biggest problems is how the buttons are handled and the charge mechanism.. Constantly it calls the onability forward, so that will cause some issues with canceling it.

I don't see why preability doesn't get changed to return an action so it can result in canceling the ability. So few plugins use that forward, it probably won't interfere...

[Chdata]

Exactly what I was thinking.