# Trigger that chooses between 1 of 7 commands based on property

**URL:** <https://forum.vassalengine.org/t/trigger-that-chooses-between-1-of-7-commands-based-on-property/77394>\
**Category:** Module Design\
**Created:** [June 29, 2023, 12:38pm UTC](https://forum.vassalengine.org/t/trigger-that-chooses-between-1-of-7-commands-based-on-property/77394 "2023-06-29T12:38:43Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![marktb1961](https://forum.vassalengine.org/user_avatar/forum.vassalengine.org/marktb1961/32/231_2.png) [@marktb1961](https://forum.vassalengine.org/u/marktb1961)\
**Post date:** [June 29, 2023, 4:40pm UTC](https://forum.vassalengine.org/t/trigger-that-chooses-between-1-of-7-commands-based-on-property/77394/2 "2023-06-29T16:40:06Z")

</div>

Not really. You are asking for a Switch / Case statement, which is generally agreed would be a very useful feature but it has not made it into reality so far. @Brent_Easton mentioned implementation challenges in this [thread](https://forum.vassalengine.org/t/switch-trigger-action/11217/14). Perhaps it will happen one day, meanwhile I generally do what you are thinking of.

One of the big advantages of a Case statement would be avoiding the problem of a later trigger mis-firing because the earlier one changed the conditions. So, I have [sometimes](https://forum.vassalengine.org/t/making-a-case-statement/74190) found it best to evaluate the condition (case) into a property at the start and then activate the chain of triggers, only one of which will activate based on the case property.

---

_[View the full topic](https://forum.vassalengine.org/t/trigger-that-chooses-between-1-of-7-commands-based-on-property/77394)._