[realwx]

It's still not applying attributes on any of the two FF2 servers I'm on sadly.

edit: Working. I forgot to restart the server. Oops.

[friagram]

Originally Posted by Cookies.net Tried it out a bit, the signature for "CAttributeList:estroyAllAttributes" wasn't correct and caused a crash when called, tried playing a bit around with the TF2 Attributes Example plugin, and from what I tried, TF2Attrib_RemoveAll was the only one not working, causing a crash - so here's the gamedata with the corrected signature. If you have some crashes caused by this still (or something that just doesn't work), please try to figure out which native is the culprit, since it'll make it easier to pin down the signature in question.

CEconItemSchema::GetAttributeDefinitionByName is different between the two, is that one of the sigs you updated?

[PC Gamer]

The modified file presented by Cookies.net on post #220 seems to be working fine on my server.

Thanks!

[FlaminSarge]

Thanks Cookies. There's some wildcarding I might do so that future updates don't need gamedata updates, but thanks for the help!
I've been going through some sudden life stuff these past few days (nothing particularly horrendous, just time-consuming) so I haven't had a chance to do anything, but since it's now summer, I should have time to check and release the latest TF2Attributes update, which'll allow you to see the static attributes on an item, as well as the item-server attributes (strange kill counts, etc).

[Cookies.net]

Originally Posted by friagram CEconItemSchema::GetAttributeDefinitionByName is different between the two, is that one of the sigs you updated?

Voided took mine and shortened 2 of the signatures (removed 1 byte from CEconItemSchema::GetAttributeDefinition and 6 bytes from the one you mentioned), never bothered to to replaced my local copy when I saw it was just that. Would like to know why he felt it was necessary to shorten those 2, though.

Originally Posted by FlaminSarge Thanks Cookies. There's some wildcarding I might do so that future updates don't need gamedata updates, but thanks for the help!

No problem, it's the first time I've been finding signatures, no prior experience, so not exactly sure what to wildcard.

[VoiDeD]

Originally Posted by Cookies.net Would like to know why he felt it was necessary to shorten those 2, though.

It was the shortest unique signature. I don't manually do these, I have IDA scripts which automate the searching and wildcarding.

[Darthmule]

I cannot seem to prevent my changes from sticking to other classes/weapons, I tried TF2Attrib_ClearCache with just the entity I am editing, m_hOwnerEntity and even both but the changes just keep sticking.

case 132, 266, 482, 1082:  // Eyelander and skins
{
  TF2Attrib_SetByName(iClient, "max health additive penalty", -50.0);
  //TF2Attrib_ClearCache(iEntity); // first attempt
  TF2Attrib_ClearCache(GetEntPropEnt(iEntity, Prop_Send, "m_hOwnerEntity")) // second attempt
}

Does any of you have an idea or way on how to prevent this issue from happening?

[MasterOfTheXP]

You seem to be setting max health additive penalty on the client, there, instead of the weapon...on clients, attributes will permanently be attached, even past disconnects, until you remove them.

The Eyelander already has that attribute, though, so if you use that instead of max health additive penalty on the weapon itself, it will be overwritten rather than stack.

[Darthmule]

Originally Posted by MasterOfTheXP You seem to be setting max health additive penalty on the client, there, instead of the weapon...on clients, attributes will permanently be attached, even past disconnects, until you remove them. The Eyelander already has that attribute, though, so if you use that instead of max health additive penalty on the weapon itself, it will be overwritten rather than stack.

Oh yeah, I see, thanks for noting me on that.

About the second note, my intended use of SetByName was to further decrease the health penalty the Eyelander and its skins give.

[ygor.almeida]

My tf2attributes no longer works on servers with Windows after this last update, any tips or fix for this?