[2.0.76] "Station is not full" wait condition fails with station names containing [virtual-signal=signal-item-parameter]

[Ajedi32]

The "Station is not full" wait condition does not work with stations that have [virtual-signal=signal-item-parameter] in their name.

Test blueprint:

0eNqdmNtu4yAQhl/F4tqpfD5E2jfYu9273coiNk1QHfBinG5V5d13sJ04daZdqBQlcoCPmWHw/PBGdu3AOsWFJts30rC+VrzTXAqyJT8PzPtNfmhqnj3ee0Jq72lo29/Ee6Fce7UUDR8bG8mm5hepnr0Xrg9eP43rPX2g2jvQE/N+nbjSA203Pd8L2n6bfjZcs+Omo4oemWbq0eMCxjCuPAH/PBCfcJioJ9tfb2QaYUw1bWCjorwlZ+giGvaXbMPzo0+Y0GAVm0aMD6+VGI47pqCDfxlZD+rEmo0BbChM0smeT46/ESBFeeSTV/hNQ8A3XLF6ag2js3+Hja7YXgNxf9AjGMOmODZBqLG9sZmDsYm9sbm9sam1sUWAUzOEmqHUHULNLrbGFiHIrbF56IAtrLFFimOxGJT+bbZv6gPlYt5CWByyhws7fUhXRgcIPgyc+Hngyg/t1zCeyfl7LhbrMHJPDRtsbL+G5RWLgZL3Yf0woEV5CWgW3AU0xcj2Wy2bszeLLDzP3PIsupodr80uMHxub3XqYHXxxd1haXVpbXW5xBqrEIH1W/e6aCkKWraT4YCvWnaf7KXMeDkXY1PUWa+9EPrXspXKdJ6q4p5swcLd+E1NIfXJkQoo1tU4S1+1/Mj12HBvkn35uy4t7lts6Vt+4xuIA61kW+0YiAw++TSOrszojjXVohr0a2fgsw4hi9mTEvlppETP9MpnrQbmk9v/7JHfyfld/O000LhK0WqVgptVCr+wSvZ1v/w8A1P3VEZfkVHmnjc4KHd3DQctb5NW1vIoNT+xz/yCdwYw6K5lVSv3vNe87quXA4fnozxxAQv2RNse0kcqDpPNaRDY7D+TE5OI5c2N5BVD3TKqNk8DMw7+gdUHF4zFbM9EQ9UrWQbDWFFxcYKpJTSMsOUpHDOzfoZZTTDQlvDDluj8eIYPEsXSPUFKbDniwD1BcFDoniA4KHJ2LQ9RUOzs2gcg9239AchdVuTJ/ytonDnXfSts7lT3F5GV36tWDF841/211agYjktnMZyX/49GEjiLYSts6CyG11g0CklkqY0XuVbcaWPsqJTEluDlFGMJTpwDXKxPjNipOUmdT6J23Mz5KLrmotjc+f6kSG3MLZwvUNZcFFs636BYmZsGzlcoNuamofMdyj32EepzfWDN0M43YIuQMc9RcdNhlB+slqqZr9fujwnmoq+6XvRN3WbJ23es5k+8rhrozMU4tBJSV+aOcNSuR1C0rJq7U9GQLyvhSWd8eTDoKyWHbnYMJLkJgpb1s3FNTMG7hECO2qYwXQwOxix3pD5p6Q5kF3CM3vbMCWN9F7ob9tDvxFQ/mppmUZmUZVokQRQkxfn8D3OwCpY=

Note that the train is stuck waiting forever at "Test 1" and never proceeds to "[virtual-signal=signal-item-parameter]Test 2" despite the station not being full. Note also that removing "[virtual-signal=signal-item-parameter]" from the second station's name instantly causes the schedule to work as intended.

Spent an hour banging my head against the wall trying to figure out why this wasn't working. I guess naming my provider stations [virtual-signal=signal-item-parameter]->[item=cargo-wagon] wasn't a good idea.

[Techjar]

It's probably substituting the parameter and looking for a station matching whatever the first item it found in the cargo is (or just doing nothing if the cargo is empty). That is how parameters are intended to be used, after all.

[Ajedi32]

Probably something like that. But the item tooltip says it only does that when used in a schedule interrupt, there's no schedule interrupt involved here, just a normal stop and a wait condition.

[Rseding91]

Looking at the logic: the generic checking logic always runs when signal parameters are used. So this is simply a case that isn't supported.