 |
Setting this to resolved as the "foreach" spawnarg has meanwhile been introduced and works correctly. |
|
|
On second reading, this actually seems to be specifically about trigger brushes receiving the "foreach" functionality, which is currently only available for callscriptfunction entities and trigger_touch entities. You can already easily let a trigger brush target a callscriptfunction entity, so it seems to have little urgency to implement this for trigger brushes directly. The advantage would be that you would be able to pass to the script which actor entered the trigger brush (since foreach also enables passing on entity parameters to the script). |
 |
Added relationship to 0003303. We already have methods to allow actions to take place under such conditions as items beeing in a location etc... It doesn't make much sense to add tons of redundant functionalities if there is no real gain. It might be worthwhile discussing this in the forum - both possible advantages and actual usecases where this might be required. |
|
|
Would have to distinguish between 2 features: 1) "foreach" > calling the script in "call" on each targeted entity. This is kind of dubious to combine with a trigger brush, since the trigger brush already triggers all of its targets so you'd be adding a 2nd action. 2) passing variables to the script (itself, the entity that activated it and if foreach is enabled, one of the targeted entities). This could be quite useful for trigger brushes. You can't pass the original activating entity in a trigger + callscriptfunction combo, and you can't pass anything with an objective + location clip combo. Stim/Response could, however, replicate this functionality already since it can pass a lot of information if you know how to setup the script. For some reason callscriptfunction entities require "foreach" to be enabled before you can pass variables. That's why I even brought up feature 2 in this ticket. |
- Anonymous
