Talk:Trigger soundscape: Difference between revisions
mNo edit summary |
|||
| Line 8: | Line 8: | ||
==The 'Soundscape' name== | ==The 'Soundscape' name== | ||
Should the 'Soundscape' name be changed to 'Soundscape Target Name' so there's no risk of confusion? or am i sounding stupid. --[[User:N0one|N0one]] ([[User talk:N0one|talk]]) 06:42, 27 January 2024 (PST) | Should the 'Soundscape' name be changed to 'Soundscape Target Name' so there's no risk of confusion? or am i sounding stupid. --[[User:N0one|N0one]] ([[User talk:N0one|talk]]) 06:42, 27 January 2024 (PST) | ||
: Why is this necessary if it is already indicated next to this {{codeblock|<target name>}} <br>-[[User:NOUG4AT|NOUG4AT]] ([[User talk:NOUG4AT|talk]]) 06:55, 27 January 2024 (PST) | |||
Revision as of 07:55, 27 January 2024
About the recently added warning
Recently a warning was added, stating that trigger_soundscape entities might break all triggers on the map in some unknown circumstance.
However, after looking at Qdude's vmf (the map that was supposedly broken) and compiling it numerous times, nothing seemed to be broken at all. My own triggers that i had added and other soundscape triggers worked as intended.
Even when I created new a test map with every single entity of l4d2 inside the trigger_soundscape volume, I still could not replicate broken triggers.
So i think its fair to say that whatever problem existed on that map, it was probably not the trigger_soundscape.
So i'm going to remove the warning.
--MrFunreal (talk) 12:38, 11 September 2021 (PDT)
The 'Soundscape' name
Should the 'Soundscape' name be changed to 'Soundscape Target Name' so there's no risk of confusion? or am i sounding stupid. --N0one (talk) 06:42, 27 January 2024 (PST)