[Klonan] [2.0.32] Train interrupt wildcard conditions evaluated incorrectly

[Milichip]

Hello!

Please refer to the image/video for context.
When using the wildcard signal in a train interrupt against another signal's value, the game behaves incorrectly.

For example, while the train stop is being supplied "Iron 100" and "A 100", the interrupt "Wildcard(signal) == A" will not trigger. This is also true for "Wildcard(signal) <= A", and yet "Wildcard(signal) >= A" does trigger the interrupt, as well as "Wildcard(signal) != A" also does.
Of course Iron 100 == A 100 should trigger because it's true, but it doesn't. Same for <=, all the while != shouldn't trigger. Didn't test the others.

Testing against constants, however, works perfectly fine.

I suggest you test every operator when wildcard is used against signals, since they seem to be particularly wonky.

Thanks :3

[robot256]

When testing the Signal Wildcard against a constant, does the interrupt trigger for a signal with the correct value but for which no station exists? I forget if they accounted for that case. The problem with "Signal Wildcard == A" is that A == A whenever A is nonzero.

[Loewchen]

The wildcard just does not take the "iron" value (even though it does take the icon in the station name), greater than even triggers with an iron signal of 1 and A of 1M. It is also not limited to signals, it is the same for the cargo wildcard. It is not signal ID that takes precedence because swapping them does not change anything.

[Muche]

It seems to me that the issue is the (signal) wildcard is being evaluated in a mode similar to combinators' EACH, but not exactly.

Combinators first evaluate all incoming signals, then run the parallel EACH mode.
That is, a decider with "EACH=A -> EACH" will output all signals whose value is the value of A.

Interrupt's wildcard mode seems to skip the signals evaluation, so "SignalWildcard=A" is effectively "EACH=0".

[Klonan]

Hello!

Please refer to the image/video for context.
When using the wildcard signal in a train interrupt against another signal's value, the game behaves incorrectly.

Hello, thank you for the report, and welcome to the forum

Would you kindly be able to upload your save game and attach it here?

[Muche]

0eNrVmV9vozgQwL/Kys+kwvwJIdI+bG+/wa50D1WEHHBSqwRnjUmvV+W73xiTQKmrjHdPp72oasCYn8eeGc948kq2dcePSjSarF+JKGXTkvXDK2nFvmG1aWvYgZM1UUzU5BwQ0VT8L7Km58DRqZalPEgtTnzSNXJ21QBsFq2Wx0nX+G1X/XI0XU9C6Q5agsu7tsdi+DoyBc2aqwkoOW8CwhsttOB2Qv3NS9F0hy30XNMrrOzUiVcLM78FgzGOsoW3ZGMEANIiXgXkBWaRAr0Sipf2Ie2nNaNGo4hmfvtH3XNd1NRJTRzQGA+N0dAED6VoaIqGRjkausRDMzQ0w0PxilrhoXhF5XgoXlE0RFMpXlOU4ql4VVG8U1G8rijeqyheWRTvVtRDW6NfTTZYBzIckbxh25oXtdyLVouyLZ4fBdwf5Ek0e7LesbrlAZFKwFjMQsI7Y+ulrKUyRGVa8iQ3n9UqzPIwo2GS5BFdZdAPIDDctv/P+nhAhOYHu9mKarLTt7IW1WLXcRs/bCfo0xSiOcHwUr3Yl8Y7WJtWs/Kpp5eyM9GJpufNGf4c64PfIjyMGb9FeNjyCh12Eid06YLmTujWBR1MOcPEsnGPMFmBZo1egPFtRcNASa61vRvcL7szUsNLWsm62PJHdhLWplo7Yvv2ute9zSoCshM1hPJ5641M4Au0/IAHID80NlId+k4grkkOjLhr8pmMpmSme8lObsLv/eCLKT2/Sf/j50U3/n6D/tVb9o3xMpc5jJv7JHX70BlmFpa47UFxVhU7JQ9FzyRrrTrYlvqbwgxw5FWBzge/ExDcbBx2TPKdt/orP0pNXPOJsF5DnTNyeWI0BpWKl6Li6obHWHJ+l6JWa2AW8KwSVz+a3oHP7IRqNX7NOCsfzbYM3ggc/HtfyPmdGZmcW3b62On5GQIlxEeGl+C3N2t8MX27nM7dLf0ZVcXh/1BV9/+dqiaBGDYa6F3DOilRLo6ydmUsyyFk9OvqAmZY3acXzbsoY9S9CsQbrvYvCzj3crVjpUu4AQnWQ7bdbgfabMXf3Gy7149rsBwf4gejWt421zjEUrML00WhvrIl4VvZVi5q5CfbnEldyxjHvl6fpAhREz97mjPdoqa++VeSz7DOY/8SF3CHSsI7ZjQNhcXD4NBD0eTzZRvfuGJjnCGHpr8w9L176JVfWJ6P7VzJ3LfYk1KEgpLQt9ozxzqp1Lfcg6JGvvUeFDX2LfigqIlvxQdFTX1LPijq0rfmg6JmvkUfFHXlW/RBUXPfog+Gmoa+RR8UlfoWfVDUyLfog6LGnkUNFDTxLGqgoKlnUeM9FLLRtnzkVVcP1fqxzmXuaTrpYM+NpVTVkLo6znsBeWZCF7N82+bAvBhSXNZU5HqA1uJgckAtyifovAzNOdj8mgDpoeqOQ5Z8iYkwzp+irkqmqm82cQ6Ix1ilUGUn9PQlMynP44Dr149/5RRnVDwTvz8S/XbS3/9W0l+KZEPNciYVGJNmas/13Gg/So/mQ2yINcgWzpXF1S6HSm5fGTVJlyyfjNU309pa32rrp+AX4Ham+SEKgyiA6BFtguE6ttexuU4v13C3DKi5ToPEXEebjS3iguzjb4cBqdmWw9IR6xCfngf/+GScBR6fuGr7CafLyBSV0zRdJWEYn8//ABMydFA=

Copy blueprint

[Klonan]

Thanks for the report,

This is fixed for 2.0.34