Cross-referencing another template increment that uses a different trigger does not work

[MikeSchumacherCapgemini]

As the title says, trying to reference a set of templates that uses a different trigger currently leads to problems.
The reason for this is that the different triggers assign different variables from which the templates get their values.

This feature was originally implemented to save users a bit of time so they do not have to generate one increment after another but can instead generate one increment which in turn generates the other increment automatically.

There are some problems with this however.
The issue already mentioned is the mismatched triggers. This is a problem because it requires one of two things. Either Cobigen needs to be able to recognize multiple triggers, which requires a lot of refactoring work, or it requires Cobigen to be able to properly compile new files in the middle of generating which, while it could possibly add the option for a lot more features in the future, may be incredibly difficult or impossible to implement.

However, the question is if this feature is needed or can be removed.
There are very few templates that utilize this feature and the effort it might take to make this feature work properly may be disproportionate to the benefit it would bring, especially since the user has an easy workaround by generating two different times manually.