Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
The "Only one action when event loops" will only let the event run one time per the condition being true. So the sample will play when the counter reaches a certain value, then it will not play again even if the counter stays at that value. This only resets if the counter changes to a different value, then goes back to being the required value, only then will it play again.
Either method is fine, but I find the "Only one action" condition to be finnicky cause it also can get reset when groups are opened and closed. Forcing the counter to change value gives you more direct control over its behavior and a much clearer idea of what is happening when you have to debug it.