Wandler said: Why would that make the select function improperly? I do expect the value to be the same on both options. All options with the same value are expected to be treated as one option, it is nothing more than an interface for the player. If you select Zeitzunder, @{trigger_entzug} will be 2. The next time the system loads up the select dropdown, it will try to select an option with a value that matches @{trigger_entzug}. I'm not sure if the system will go to the first match or the last match, but either way, the displayed value won't be Zeitzunder despite the fact that's what the player actually selected. Instead, you could do something like this: <select name="attr_trigger_entzug_name">
<option value="Befehl">Befehl</option>
<option value="Kontakt">Kontakt</option>
<option value="Zeitzünder">Zeitzünder</option>
<option value="Ver. Befehl">Ver. Befehl</option>
<option value="Ver. Kontakt">Ver. Kontakt</option>
<option value="Ver. Kontakt Geschlecht/Metatyp">Ver. Kontakt Geschlecht/Metatyp</option>
</select>
<input type="hidden" name="attr_trigger_entzug"> <script type="text/worker"> on('change:repeating_my_repeating_section_name:trigger_entzug_name', function() { getAttrs(['trigger_entzug_name'], function(values) { switch(values.trigger_entzug_name) { case 'Befehl:
case 'Zeitzünder':
case 'Ver. Befehl': setAttrs({ trigger_entzug: 2 }); break;
case 'Kontakt':
case 'Ver. Kontakt': setAttrs({ trigger_entzug: 1 }); break;
case 'Ver. Kontakt Geschlecht/Metatyp': setAttrs({ trigger_entzug: 3 }); break; } }); }); </script> The select would work properly, @{trigger_entzug} would be the correct numeric value, and @{trigger_entzug_name} would be the name of the label.