Thanks for looking into this.I don't think it doesn't show the code because of the way the game is coded. AFAIK URM isn't able to "look ahead" very far, and that's why. Here's an example from the very beginning of day 2:
View attachment 3202922 View attachment 3202923
If the code I've marked in red would be before the "jump" command, URM would detect (and show) it:
View attachment 3202927 View attachment 3202929
The only "fix" would be to tell URM to look farther into the code -- but then again, how far into the next labels should URM analyze the code?
So yes, URM will stop looking ahead for code once it encounters a jump/call, and report this jump/call under "next label".
Since in this case there's only a jump after the choice it will not report any code.
I think that stop looking for code once we detect a jump/call makes most sense, but maybe I will add a feature to show the "next label" code by clicking it?!