light-switch on cs_estate

[KWo]

After getting to normal job button code with Podbot2.6mm we found one button (exactly light-switch) totally different than others. This is that general light-switch on cs_estate (see the first picture). All other buttons, light-switches return for the traceline "func_button" - so it's possible to use this part of code responsible to buttons. But only this one give us back after firing the traceline the "func_wall" (see the second picture). Can some of l33t mappers tell us what is this that switch? What other functions are possible to detect it - there is not only a wall - there is also light-switch? How is this switch working (when I push "use" - it's working - so there is some "pushable" area - I suppose)?

[Pierre-Marie Baty]

My opinion is that the light switch entity is BEHIND the 'func_wall', but just close enough for the player to use it. Or else it's invisible and noclipped. But there HAS to be a func_button or a func_pushable around. Use my PMTools to find out where it hides.

[KWo]

Originally Posted by Pierre-Marie Baty

But there HAS to be a func_button or a func_pushable around. Use my PMTools to find out where it hides.

At my second picture I tried it. I tried more up, more down, more left, more right. But maybe there is something in Your PMTools like ignore_walls - to let me shoot traceline (or something) to this hidden button throw this func_wall? Or maybe You meant rather about go to no-clip and than try once again? But - how to force bot to find it throw this func_wall? I'm confused...???

[sPlOrYgOn]

he means use find entities in sphere

[KWo]

OK . I made "asearch 40". There is found the "func_door". I'm surprised...And how to force bot to find it? Look at picture.

[stefanhendriks]

as i said in a PM:

try to find this entity and a target on it. I know func_doors are used as buttons as well. When a func_door is using a target, it must be a button (because normally a door does not have a target!). Triggered doors are different, the doors 'targetname' is then set and not 'target'. The button that triggers the door (which can be also a func_door) has a 'target' that is the same as 'targetname' of the triggered door.

So in short, 'target' is the magic key; you just need to know which entities are used as 'buttons'.

[Pierre-Marie Baty]

KWo, what you did was very useful. Now do a "printent 200" to print the variables of entity #200 (the func_door) and see what's its target.

If you want to log the output to a file, use the "logfile" command (ex: "logfile cs_log.txt").

[KWo]

OK. Here You have this dump. I don't know how to use the results of this.

BTW. I used condump, because when I tried this:
logfile : cs_log
printent 200

then CS crashed me. I tried at two computers. It's possible reproduce this. This ":" I found in the description (help) to this plugin. Probably need update this help for some working example to this "logfile" command usage (for n00bs like me)...

[stefanhendriks]

there you go, it refers to a target 'upstairs'.

[KWo]

Yeah. Thanks . sPlOrYgOn already made some dll for test for me and seems now is 75% OK. Sometimes bots try to reach this button even if they fall down from this cement block that raises up from the ground and then they got stuck. But normally now they can go there and use it. The problem currently I have is this. Without my calling "Taking fire - need assistance" they don't like go there, even I placed there one CT (blue) and one T (red) WP...