[KiRRA]

Greetings. I was curious if one of you smart individuals could help me out on a little problem I am having.

I am currently looking to basically force the Phlogistinator to act identically to the basic Flamethrower. We currently use TF2Items to change some of the air-blast characteristics of all flame throwers for one of our mods. I would love to either be able to add the airblasting characteristics (if capable of doing that without creating any bugs) to the Phlog...OR to just turn Phlog into basic Flamethrower.

One of our mods does have some code in it that picks out certains weapons and literally swaps them out for counterparts, but I do not have the time to destroy the code looking for how to implement just that part into it's own plugin. As that particular plugin is not implemented in the game style I need to use this modification for. Was really hoping there was a way to do this by the use of TF2Items.

Would be GREATLY appreciated if any help can be given. Thank you and have a great day!

[Requiesta]

Just apply this attribute:

PHP Code:

"594"
        {
            "1"        "37"
        } 


[KiRRA]

Originally Posted by Requiesta Just apply this attribute: PHP Code: "594"         {             "1"        "37"         }

It should look like this when added to my current coding correct? Just making sure, thank you ahead of time! You've been a big help!

PHP Code:

"custom_weapons_v3"
{
 "*"
 {
  "*"
  {
   "preserve-attributes"    "1"
   "1"    "254 ; 4.0"
  }
  "594" 
  { 
   "1"        "37" 
  }
 }
} 


[asherkin]

The config is first-wins, so it needs to be before the wildcard.

[KiRRA]

Alright, it worked the other way around as well but just incase some problems arise that I don't notice right away I did what you said and put the Phlog entry before the wildcard. This is the code I currently have in my tf2weapons file.

PHP Code:

"custom_weapons_v3"
{
 "*"
 {
  "594" 
  { 
   "1"        "37" 
   "2"    "254 ; 4.0"
  }
  "*"
  {
   "preserve-attributes"    "1"
   "1"    "254 ; 4.0"
  }
 }
} 


Quick question even though it works and doesn't matter....What exactly is attribute 37? I looked in the items script and checked what attribute 37 was (hidden primary max ammo bonus) and seemed to be something completely unrelated to a flame thrower, or atleast the Phlog. Like I said, doesn't matter as the fix works (Phlog has 800 ammo displayed but infinite ammo ofcourse) but it works. =) Big help for those that just always forget to take that god forsaken weapon off.

[KiRRA]

I know this is a major necro to an old post but could finally use some help again after all this time.

The contents of my tf2 items config hasn't change but the Phlog no longer has airblast enabled anymore. Can someone point in the right direction to the revised/updated values to get them working again so the Phlog acts as a regular flamethrower?

It would be greatly appreciated! Thanks!

"custom_weapons_v3"
{
 "*"
 {
  "594" 
  { 
   "1"        "37" 
   "2"    "254 ; 4.0"
  }
  "*"
  {
   "preserve-attributes"    "1"
   "1"    "254 ; 4.0"
  }
 }
}

[Requiesta]

I don't think attribute 37 works for setting items back to stock value anymore, you'd need this:

		// The Phlogistinator
		"594"
		{
			"1"			"1 ; 1.0"
			"2"			"368 ; 0"
			"3"			"116 ; 0"
			"4"			"356 ; 0"
			"5"			"350 ; 0"
			"6"			"144 ; 0"
			"7"			"15 ; 1"
			"8"			"551 ; 1"
		}

[KiRRA]

I should have worded that better than I did. Thank you for the fast reply btw.

The ONLY characteristic I need to change on the Phlog is the ability to add the airblast func to it.

Also, did they change the values for the "airblast functionality flags" as well? I had it at 4.0 with the knowledge that player to player airblasting was non-functional but projectile based deflection was still working properly. Apparently 4.0 no longer ties the airblast to only projectiles and allows players to push each other back. Is there a different value now?

[Requiesta]

Oh in that case only set attribute 4 to 0. The ID for mod disable airblast is 356.

[nergal]

Originally Posted by asherkin The config is first-wins, so it needs to be before the wildcard.

small question about the wildcard

i know it applies to steamIDs but can it be applied to weapon/hat indexes?