Help:VE276: Difference between revisions
From TrainzOnline
Jump to navigationJump to search
Created page with "'''Mismatched 'conflicts-with-queues' data. Queue '<queue>' specifies '<other queue>' as a conflict but the reverse is not true.''' A product queue lists another queue in its..." |
No edit summary |
||
| Line 1: | Line 1: | ||
'''Mismatched 'conflicts-with-queues' data. Queue '<queue>' specifies '<other queue>' as a conflict but the reverse is not true.''' | '''Mismatched 'conflicts-with-queues' data. Queue '<queue>' specifies '<other queue>' as a conflict but the reverse is not true.''' | ||
A product queue lists another queue in its 'conflicts-with-queues' data, but that other queue does not list this one back. Queue conflicts must be declared on both queues so the relationship is unambiguous. | A product queue lists another queue in its '[["Queues"_container#conflicts-with-queues|conflicts-with-queues]]' data, but that other queue does not list this one back. Queue conflicts must be declared on both queues so the relationship is unambiguous. | ||
Add the matching conflict entry to the other queue, so each queue lists the other. On older assets the mismatched conflict is ignored and reported as a warning; from trainz-build 5.7 it is an error. | Add the matching conflict entry to the other queue, so each queue lists the other. On older assets the mismatched conflict is ignored and reported as a warning; from trainz-build 5.7 it is an error. | ||
[[Category:Validation Errors]] | [[Category:Validation Errors]] | ||
Latest revision as of 02:25, 10 August 2026
Mismatched 'conflicts-with-queues' data. Queue '<queue>' specifies '<other queue>' as a conflict but the reverse is not true.
A product queue lists another queue in its 'conflicts-with-queues' data, but that other queue does not list this one back. Queue conflicts must be declared on both queues so the relationship is unambiguous.
Add the matching conflict entry to the other queue, so each queue lists the other. On older assets the mismatched conflict is ignored and reported as a warning; from trainz-build 5.7 it is an error.
