[Theray070696]

Originally Posted by The enigma I really love this plugin, and making em is fun, however, is there a way to add admin flags to the weapons? So like, I make a really OP weapon, And I want to make it flag Z able to use it. First up, is it possible?

Easily! Just add "flag" or "flags" (with quotes) into the weapon file and put "z" after it (again, with quotes).
Example:

"flags" "z"

Make sure you're using the github build!

[nosoop]

Originally Posted by superwry Thanks! The plugin is successfully compiled. However, as my being unable to read the code, I don't know how to configure the txt correctly.(Is there 6 values?!)

Correct, there's six optional values plus the required exploding sapper attribute. I've added in my documentation for all the attributes here. The #define ATTR_EXPLODING_SAPPER_* preprocessor directives refer to string constants; you don't deal with them when using the attributes.

There are also downloads available now (though I probably ended up compiling them against 1.8 where DataPacks are not backwards compatible, oops).

[The enigma]

Originally Posted by Theray070696 Easily! Just add "flag" or "flags" (with quotes) into the weapon file and put "z" after it (again, with quotes). Example: "flags" "z" Make sure you're using the github build!

Thanks!

Also where do I get the github build? (just in case it has some extra support and stuff)

Also When using custom attributes on a weapon, and you drop the weapon, and you go to it and pick it up in battle, it doesn't retain its custom attributes.
Is it because its not recognized?

I dunno, also, is there a command that makes the custom weapons disappear on death?

[The enigma]

Originally Posted by Mr.Orion Orion's attributes has been updated ! yay ! ¥ Changelog : UPDATE : 8.00: 8.01: - Added a duration to Fury Swipe which can be refreshed (stopping the duration and re-launching it from the beginning). - - If the duration ends, bonus damage from Fury Swipe will be lost. 8.00: - orion.smx has been cut in 3 new attributes which are : - - orion.smx which regroups attributes coming from my own mind or request. - - moreaw2.smx which regroups all the advanced weaponiser 2 attributes that I made. - - dota2.smx which regroups attributes from Dota 2. <-- I don't take any request for this plugin. - Some attributes name have changed because of bugs or because it needed it. - - "hot sauce" to "hotsauce" - - "hot sauce on crit" to "hotsauce on crit" - - "stun on crit" to "stun on hitcrit" - - "last will" to "berserker near death" - - "respawn" to "respawn where you died" - - "jinada" to "jinada attr" - - And maybe one more, but I don't remember which one. - Added the followings attributes : 15 - - Spawn Skeleton on Kill. ¥ - - Berserker Near Death. ¥ - - Low Berserker Near Death. ¥ - - Slow on Hit. ¥ - - Buzz Axe Rampage. ¥ - - Heat Increases Fire Rate. ¥ - - Remove Bleed. ¥ - - Fly While Shooting. ¥ - - Minimann. ¥ - - Disable Primary. ¥ - - Evasion. ¥ - - Fervor. ¥ - - Overpower. ¥ - - Last Will. ¥ - - True Strike. ¥ - Made the attributes' help easier to understand, I guess, it's easier for me anyway. - There is now 3 pages on the attributes' help, 1 page for 1 attributes pack. - - First page is for orion.smx - - Second page is for moreaw2.smx - - And the third page is for dota2.smx - Fixed bugs and stuff, you know, that kind of things. - Some have attributes' values have different place order now. eg : from "1 2 3" to "2 3 1", something like that. - Improved attributes, I think, I hope, maybe, maybe not, you to judge. - Stuff. - ( ͡° ͜ʖ ͡°) - Also, remember childrens, it's Wingardium Leviosah!

How do I install Orion's attribute packs? (and the AW and Dota)

and also, how do I use them IE

"spawn skeleton on kill"
{
"plugin" "????" <---- what goes here? (for orion AW and dota
"value" "1"

}

Please?
I would love to know, also, is there some description on what these do?
there's a lot.

[404UserNotFound]

Originally Posted by The enigma Also where do I get the github build? (just in case it has some extra support and stuff)

https://github.com/404UserNotFound/CustomWeapons2

Originally Posted by The enigma Also When using custom attributes on a weapon, and you drop the weapon, and you go to it and pick it up in battle, it doesn't retain its custom attributes. Is it because its not recognized?

Plugin-added custom attributes are not tied to the weapon when it gets converted to a dropped weapon entity. There's probably a way we can code in a weapon-dropping check and make sure to tie the attributes to the weapon entity and have them reload when you pick the weapon up.

It'd be nice if we could hook into the name display of the dropped weapon entity and change the name to the custom name.

[starblaster64]

Originally Posted by abrandnewday It'd be nice if we could hook into the name display of the dropped weapon entity and change the name to the custom name.

Do TF2 attributes 500 (custom name attr) or 2024 (item name text override) work when applied through SourceMod?

[The enigma]

Question for this awesome plugin.
When using custom weapon it is invisible,
That sorta defeats the purpose. I am not using custom weapon models,
But I want them to show,
IE I make a mini gun look like the minigun (15)
But nothing shows.
Help?
Also, with the github build, it is very glitchy, I cant make weapons use ADMIN flags.

[Naydef]

Originally Posted by The enigma Question for this awesome plugin. When using custom weapon it is invisible, That sorta defeats the purpose. I am not using custom weapon models, But I want them to show, IE I make a mini gun look like the minigun (15) But nothing shows. Help? Also, with the github build, it is very glitchy, I cant make weapons use ADMIN flags.

Valve restriction, but there are some ways to make them visible!

[Ksed]

Originally Posted by Naydef Valve restriction, but there are some ways to make them visible!

How? It seems random when the weapons are visible and invisible. Mostly invisible when other players have them.

But bots have the visible weapons 99% of the time.

When a player has a custom weapon, they randomly will be visible or not. Or upon death, they become visible/invisible.

I have no idea about custom models though.

[Naydef]

Originally Posted by Ksed How? It seems random when the weapons are visible and invisible. Mostly invisible when other players have them. But bots have the visible weapons 99% of the time. When a player has a custom weapon, they randomly will be visible or not. Or upon death, they become visible/invisible. I have no idea about custom models though.

There are (several) methods, but to say that Valve gave us one official way to give visible weapons and other things, but I predict If we abuse it, Valve will make the same restrictions as in CS:GO. Every server need to be with toke GSLT and in case of abuse, the server will be banned. Like in CS:GO. This is the idea!

@The655 Just to remind you. It's perfectly OK to have visible weapons. It's NOT OK to have visible official hats!