[TF2] Custom Weapons 2 (Beta 2, Mar 12 2014) - Page 63

Chdata · *Last edited by Chdata; 09-27-2015 at 14:27.*

There is an attribute to block default minigun sounds.

I can probably add support for replacing all sorts of sounds but that'll come over time.

http://imgur.com/ahw7dD7

Also I've added support for giving Self Made quality to specific steam IDs. By default you can specify up to 5 per weapon. To increase that you'd need to recompile.

Also yeah, any weapon with modified clip size attributes that lower the clip tend to start with more clip than their max as they'll start with the default clip size of the base weapon - the getmaxclip gamedata would just make things easier on everyone. "mag" would overwrite it.

(Why is it mag and not clip...?)

Theray070696 · *Last edited by Theray070696; 09-27-2015 at 16:11.*

Quote:

Originally Posted by Chdata

There is an attribute to block default minigun sounds.

I can probably add support for replacing all sorts of sounds but that'll come over time.

http://imgur.com/ahw7dD7

Also I've added support for giving Self Made quality to specific steam IDs. By default you can specify up to 5 per weapon. To increase that you'd need to recompile.

Also yeah, any weapon with modified clip size attributes that lower the clip tend to start with more clip than their max as they'll start with the default clip size of the base weapon - the getmaxclip gamedata would just make things easier on everyone. "mag" would overwrite it.

(Why is it mag and not clip...?)

I just looked at your github, the weapon description that's appearing is the weapon that killed you. The version you forked has a bug, I added a check for it only displaying when an enemy kills you, but I derped and made it show only when you kill yourself. It's fixed in the main branch.

404UserNotFound · *Last edited by 404UserNotFound; 09-27-2015 at 16:23.*

Quote:

Originally Posted by Chdata

Also I've added support for giving Self Made quality to specific steam IDs.

Also do-able via the "quality" option I added in back in Beta 3. Although with that option, it'd be Self-Made for everyone who equips the weapon....but you could always just add a "flag" for the weapon and restrict it that way.

Your thing is good for if we wanted to toss in our Steam IDs so that any weapons we give ourselves on any servers become Self-Made (might as well force-add the self-made sparkle particle attribute as well)

Theray070696 · 09-27-2015 , 18:40 Re: [TF2] Custom Weapons 2 (Beta 2, Mar 12 2014)

Quote:

Originally Posted by abrandnewday

Also do-able via the "quality" option I added in back in Beta 3. Although with that option, it'd be Self-Made for everyone who equips the weapon....but you could always just add a "flag" for the weapon and restrict it that way.

Your thing is good for if we wanted to toss in our Steam IDs so that any weapons we give ourselves on any servers become Self-Made (might as well force-add the self-made sparkle particle attribute as well)

I think he means the weapon maker can put a steamid for whoever made the weapon. For the Matador, it would be me, mecha, and whoever did the model. It could also be used to show who had the original idea or who suggested the weapon.

Chdata · *Last edited by Chdata; 09-27-2015 at 22:49.*

Quote:

Originally Posted by abrandnewday

Also do-able via the "quality" option I added in back in Beta 3. Although with that option, it'd be Self-Made for everyone who equips the weapon....but you could always just add a "flag" for the weapon and restrict it that way.

Your thing is good for if we wanted to toss in our Steam IDs so that any weapons we give ourselves on any servers become Self-Made (might as well force-add the self-made sparkle particle attribute as well)

I forgot to explain that my version overwrites the quality setting, thus I already knew about it. It's to give only the people involved in creating it, Self-Made quality, while other people get whatever the "quality" key is set to.

I didn't force the sparkle, because some people might do stuff like

http://advancedweaponiser.wikia.com/...he_Lifestealer

I'd attribute The Matador to Mecha (coder / probably came up with it) and Ritz (the modeler) but not the porter from aw2->cw2 just cause I don't intend to label my steamID over every bit of copy-paste work I do myself. (At least for any aw2 stuff I make myself).

By the way for people making custom attribute plugins, it's probably a lot better to

g_iThisWeaponHasACustomAttribute[MAXPLAYERS + 1][5]; // [iClient][iSlot]

than to

g_iWephascust[2049]; // [iWeapon]

Code:

stock GetSlotFromPlayerWeapon(iClient, iWeapon)
{
    for (new i = 0; i <= 5; i++)
    {
        if (iWeapon == GetPlayerWeaponSlot(iClient, i))
        {
            return i;
        }
    }
    return -1;
}


public Action:TF2_CalcIsAttackCritical(iClient, iWeapon, String:szWeaponNAme[], &bool:bResult)
{
    new iSlot = GetSlotFromPlayerWeapon(iClient, iWeapon);
    if (g_iSniperCombo1016[iClient][iSlot] > 0)
    {
        g_iSniperComboHit1016[iClient][iSlot] = false;

        new Handle:hData;
        WritePackCell(hData, iClient);
        WritePackCell(hData, iSlot);
        RequestFrame(Frame_Attribute_1016_Expire, hData);
    }
}

public Frame_Attribute_1016_Expire(any:Pack)
{
    ResetPack(Handle:Pack);
    new iClient = ReadPackCell(Handle:Pack);
    new iSlot = ReadPackCell(Handle:Pack);
    CloseHandle(Handle:Pack);

    if (!g_iSniperComboHit1016[iClient][iSlot])
    {
        g_iSniperCombo1016[iClient][iSlot] = 0;
    }
}

For attributes that affect specifically "Sniper Rifle Charge" or "Any cloak property" or "Any shield property"

Don't even make it a 2D array, you just need g_iSrifleChargeAttr[MAXPLAYERS + 1];

Since sniper rifle charge is something that is exclusive to primary weapons.

I've only looked at basic/custom-attributes which indexes by 2049, at least.

crafting · 09-28-2015 , 00:15 Re: [TF2] Custom Weapons 2 (Beta 2, Mar 12 2014)

Quote:

Originally Posted by The655

Also,mediguns has sounds?

When you heal someone... people have made custom healing sounds

Theray070696 · *Last edited by Theray070696; 09-28-2015 at 00:21.*

Quote:

Originally Posted by Chdata

I forgot to explain that my version overwrites the quality setting, thus I already knew about it. It's to give only the people involved in creating it, Self-Made quality, while other people get whatever the "quality" key is set to.

I didn't force the sparkle, because some people might do stuff like

http://advancedweaponiser.wikia.com/...he_Lifestealer

I'd attribute The Matador to Mecha (coder / probably came up with it) and Ritz (the modeler) but not the porter from aw2->cw2 just cause I don't intend to label my steamID over every bit of copy-paste work I do myself. (At least for any aw2 stuff I make myself).

By the way for people making custom attribute plugins, it's probably a lot better to

g_iThisWeaponHasACustomAttribute[MAXPLAYERS + 1][5]; // [iClient][iSlot]

than to

g_iWephascust[2049]; // [iWeapon]

Code:

stock GetSlotFromPlayerWeapon(iClient, iWeapon)
{
    for (new i = 0; i <= 5; i++)
    {
        if (iWeapon == GetPlayerWeaponSlot(iClient, i))
        {
            return i;
        }
    }
    return -1;
}


public Action:TF2_CalcIsAttackCritical(iClient, iWeapon, String:szWeaponNAme[], &bool:bResult)
{
    new iSlot = GetSlotFromPlayerWeapon(iClient, iWeapon);
    if (g_iSniperCombo1016[iClient][iSlot] > 0)
    {
        g_iSniperComboHit1016[iClient][iSlot] = false;

        new Handle:hData;
        WritePackCell(hData, iClient);
        WritePackCell(hData, iSlot);
        RequestFrame(Frame_Attribute_1016_Expire, hData);
    }
}

public Frame_Attribute_1016_Expire(any:Pack)
{
    ResetPack(Handle:Pack);
    new iClient = ReadPackCell(Handle:Pack);
    new iSlot = ReadPackCell(Handle:Pack);
    CloseHandle(Handle:Pack);

    if (!g_iSniperComboHit1016[iClient][iSlot])
    {
        g_iSniperCombo1016[iClient][iSlot] = 0;
    }
}

For attributes that affect specifically "Sniper Rifle Charge" or "Any cloak property" or "Any shield property"

Don't even make it a 2D array, you just need g_iSrifleChargeAttr[MAXPLAYERS + 1];

Since sniper rifle charge is something that is exclusive to primary weapons.

I've only looked at basic/custom-attributes which indexes by 2049, at least.

I guess I can throw an attribute in rays attributes which will add the sparkle for the maker, should only need to check quality and apply the particle attribute. Of course, the weapon maker will have to add the attribute to the weapon.