[shotgiy12]

The dragon's fury isn't working and only allows for one use of the weapon, I don't know if it's due to my understanding of needed attributes for the weapon or that it just doesn't work.
I've tried noanims and ffbat_defaults but still come with up with a negative, if anyone has any knowledge on this it would be greatly appreciated.

[JuegosPablo]

need put the specific attributes (example: the phlogistonator use 839 ; 2.8 ; 841 ; 0 ; 843 ; 12 ; 844 ; 2300 ; 862 ; 0.6 ; 863 ; 0.1 ; 865 ; 5 ; 368 ; 1 ; 144 ; 1 ; 116 ; 5 ; 356 ; 1 ; 15 ; 0 ; 350 ; 1 on the attributes)


This i use on my Edited Fujiwara no Kokou

{
		"name"	"rage_random_weapon"
		"arg0"	"-1"
		"arg1"	"0" // trigger. 0 = E rage, 1 = triggered by ability management system
		"arg2"	"1" // number of weapons (MAX: 10)
		"arg3"	"0.0" // weapon duration. set to 0.0 to keep it forever. (or until replaced)
		"arg4"	"" // mapwide sound to play when rage is used
		
		// all weapons below have the "no random critical hits" attribute
		// from arg11 and every 10 args after, specs for various weapons repeat
		"arg11"	"tf_weapon_flamethrower" // weapon name
		"arg12"	"594" // weapon index (cleaver)
		"arg13"	"839 ; 2.8 ; 841 ; 0 ; 843 ; 12 ; 844 ; 2300 ; 862 ; 0.6 ; 863 ; 0.1 ; 865 ; 5 ; 368 ; 1 ; 144 ; 1 ; 116 ; 5 ; 356 ; 1 ; 15 ; 0 ; 350 ; 1 ; 2025 ; 2 ; 2014 ; 1" // weapon args (set to headshot for 360, body shot for 60)
		"arg14"	"0" // weapon visibility
		"arg15"	"255" // weapon alpha (0 = fully hidden, 255 = fully visible)
		"arg16"	"0" // weapon slot
		"arg17"	"0" //"454" // optional, wearable to use for bodygroup swaps
		"arg18"	"50" // starting clip
		"arg19"	"50" // starting reserve ammo
		
		"plugin_name"	"ff2_sarysapub3"
	}

[Batfoxkid]

Dragon's Fury default attributes are:
37 ; 0.2 ; 783 ; 20 ; 801 ; 0.8 ; 856 ; 1 ; 2062 ; 0.25 ; 2063 ; 1 ; 2064 ; 1 ; 2065 ; 1

[JuegosPablo]

	{
		"name"	"rage_random_weapon"
		"arg1"	"0" // trigger. 0 = E rage, 1 = triggered by ability management system
		"arg2"	"1" // number of weapons (MAX: 10)
		"arg3"	"0.0" // weapon duration. set to 0.0 to keep it forever. (or until replaced)
		"arg4"	"" // mapwide sound to play when rage is used
		
		// all weapons below have the "no random critical hits" attribute
		// from arg11 and every 10 args after, specs for various weapons repeat
		"arg11"	"tf_weapon_rocketlauncher_fireball" // weapon name
		"arg12"	"1178" // weapon index (cleaver)
		"arg13"	"37 ; 0.2 ; 783 ; 20 ; 801 ; 0.8 ; 856 ; 1 ; 2062 ; 0.25 ; 2063 ; 1 ; 2064 ; 1 ; 2065 ; 1 ; 2025 ; 2 ; 2014 ; 1" // weapon args (set to headshot for 360, body shot for 60)
		"arg14"	"0" // weapon visibility
		"arg15"	"255" // weapon alpha (0 = fully hidden, 255 = fully visible)
		"arg16"	"0" // weapon slot
		"arg17"	"0" //"454" // optional, wearable to use for bodygroup swaps
		"arg18"	"50" // starting clip
		"arg19"	"50" // starting reserve ammo
		
		"plugin_name"	"ff2_sarysapub3"
	}

Like this gonna be used on hales cfgs (this is a example)

[shotgiy12]

Originally Posted by Batfoxkid Dragon's Fury default attributes are: 37 ; 0.2 ; 783 ; 20 ; 801 ; 0.8 ; 856 ; 1 ; 2062 ; 0.25 ; 2063 ; 1 ; 2064 ; 1 ; 2065 ; 1

It works now, thanks, also is there a way to access the default attributes attached to the weapons, I don't really know where to find it and would appreciate knowing where to find said information.

[kking117]

Originally Posted by shotgiy12 I don't really know where to find it and would appreciate knowing where to find said information.

"tf\scripts\items\items_game.txt" In your Team Fortress 2 folder should be where you can find it.

Here's some brief instructions for finding stuff:

Spoiler

Search (CTRL+F helps) for the item you're looking for (This website may help.)
Once you've found the item you're looking for the "static_attrs" part .

Dragon's Fury should look something like this:

"static_attrs"
{
	"min_viewmodel_offset"					"10 -3 -10"
	"item_meter_charge_type"							"1"
	"item_meter_charge_rate"				"0.8"
	"meter_label"							"#TF_Pressure"
	"hidden primary max ammo bonus"			"0.2"
	"airblast cost scale hidden"			"0.25"
	"dragons fury neutral properties"		"1"
	"dragons fury positive properties"		"1"
	"dragons fury negative properties"		"1"
	"extinguish restores health"			"20"
}

These are the attributes the weapon uses, the item_game.txt also contains a list of attributes and their index, so search for "hidden primary max ammo bonus" until you find its' index:

"37"
{
	"name"	"hidden primary max ammo bonus"
	"attribute_class"	"mult_maxammo_primary"
	"description_string"	"unused"
	"description_format"	"value_is_percentage"
	"hidden"	"1"
	"effect_type"	"positive"
	"stored_as_integer"	"0"
}

However it doesn't stop here as "static_attrs" doesn't contain all attributes each weapon has in most cases (Dragon's Fury is one of those exceptions). Some items use a thing called "prefab" which is usually where their "static_attrs" is held instead.

For brief instructions of items using "prefab" I'll be using the Degreaser as an example:

Spoiler

"215"
{
	"name"	"The Degreaser"
	"prefab" "weapon_degreaser paintkit_base"
	"first_sale_date"	"2010/09/29"
	"particle_suffix"	"degreaser"
	"tags"
	{
		"can_be_festivized"		"1"
	}
	"visuals"
	{
		"attached_models_festive"
		{
			"0"
			{
				"model"	"models/workshop/weapons/c_models/c_degreaser/c_degreaser_festivizer.mdl"
			}
		}
	}
}

See how it lacks "static_attrs" when it obviously has attributes? Well that's because at some point (Jungle Inferno I believe) items_game.txt started using something called "prefab". The Degreaser uses "prefab" "weapon_degreaser paintkit_base" we can ignore the paintkit_base part as that's used for weapon skins.

"weapon_degreaser" is what we want, and a quick search shows:

"weapon_degreaser"
{
	"enabled"	"1"
	"prefab"	"weapon_baseflamethrower"
	"capabilities"
	{
		"nameable"		"1"
	}
	"tags"
	{
		"can_deal_damage"			"1"
		"can_reflect_projectiles"	"1"
		"can_extinguish"			"1"
		"can_deal_posthumous_damage"	"1"
		"can_deal_critical_damage"	"1"
		"is_flamethrower" "1"
	}
	"item_logname"	"degreaser"
	"item_iconname"	"degreaser"
	"show_in_armory"	"1"
	"item_name"	"#TF_TheDegreaser"
	"image_inventory"	"backpack/workshop/weapons/c_models/c_degreaser/c_degreaser"
	"image_inventory_size_w"		"128"
	"image_inventory_size_h"		"82"
	"model_player"	"models/workshop/weapons/c_models/c_degreaser/c_degreaser.mdl"
	"attach_to_hands"	"1"
	"inspect_panel_dist" "91"
	"item_quality"	"unique"
	"propername"	"1"
	"min_ilevel"	"10"
	"max_ilevel"	"10"
	"used_by_classes"
	{
		"pyro"	"1"
	}
	"static_attrs"
	{
		"min_viewmodel_offset"					"10 0 -10"
		"single wep deploy time decreased"		"0.4"
		"switch from wep deploy time decreased"	"0.7"
		"weapon burn dmg reduced"				"0.34"
		"airblast cost increased"				"1.25"
	}
	"visuals"
	{
		"attached_models"
		{
			"0"
			{
				"model"	"models/workshop/weapons/c_models/c_degreaser/c_degreaser_pilotlight.mdl"
			}
		}
		"sound_single_shot"	"Weapon_Degreaser.FireStart"
		"sound_special1"	"Weapon_Degreaser.FireLoop"
		"sound_burst"	"Weapon_Degreaser.FireLoopCrit"
		"sound_special3"	"Weapon_Degreaser.FireEnd"
	}
	"mouse_pressed_sound"	"ui/item_heavy_gun_pickup.wav"
	"drop_sound"		"ui/item_heavy_gun_drop.wav"
}

As we can see this contains "static_attrs" which holds the attributes the Degreaser uses, but wait this prefab also uses a prefab? Yes it does and it links to "weapon_baseflamethrower" which then links to "prefab" "weapon_newflame" which is where the "static_attrs" for controlling the flamethrower flames is held:

"weapon_newflame"
{
	"static_attrs"
	{
		"flame_gravity"							"0"
		"flame_drag"							"8.5"
		"flame_up_speed"						"50"
		"flame_speed"							"2450"
		"flame_spread_degree"					"2.8"
		"flame_lifetime"						"0.6"
		"flame_random_life_time_offset"			"0.1"
	}
}

This probably seems confusing but I'm pretty sure that only flamethrowers are this complex when it comes to using prefabs. Most simply link to a prefab containing all their attributes but just double check to be sure.