[Bobakanoosh]

Hey,

Backstory:
I was trying to fix many of the broken traitor doors on TTT maps. After decompiling several maps with the broken doors, they all had filter_activator_name's hooked up to their buttons (image1, image2). I'm generally very confused as to why over 6 maps use this method of setting up a button -- Bara's TTT hasn't ever used these filters in the code to make functioning traitor doors. The only thing I can think of these being from is Garry's Mod. Even then, some clearly newer looking maps use them.

I've already applied a slight work around by just changing the name of the door to contain traitor, but that still means all the button-activated traps dont work, and any testers that have numerous logic_case's set up to them, dont work.

Question:
How can I access the fields from the images above like the func_button's filtername, and the filter_activator_name's Filter Name. I found a plugin using m_iFilterName, but that's not even a valid property.

I saw many mentions of filter_activator_name in surf plugin configs, but couldn't find how they were actually using them.

Any ideas?

Edit: I've tried sm_dump_netprops and couldnt find anything in there.

[Bobakanoosh]

Didn't quite answer the question, but still solved the problem:

https://github.com/Bara20/TroubleinT...a2d8b522ed95fa

Thanks to R3TROATTACK

Solved

[rodrigo286]

Change to "SOLVED" on tittle.

Good lucky on plugins.

Regards.

[Neuro Toxin]

Filters are used by trigger entities such as trigger_multiple to filter which entities can activate the outputs such as OnStartTouch.

Triggers which support filters have a filter property in Hammer's Smart Edit property editor.

filter_activator_name is a filter entity that is used to filter targets by their m_iName netprop.

Other filters allow filtering by team, classname, ect.

https://developer.valvesoftware.com/...r_Applications