What is it?
Options to make console more readable.
How?
Remove file path and hierarchy & color code line#
Why?
The console hasn’t evolved in years and 70% is visual noise
Exhibit A
Exhibit B
This is just how call stacks work. Those practically haven’t evolved ever since debuggers were invented. This is not going to change.
Your exhibit B actually trims away important details. What if there were two different Generate() methods in two different files named WorldGenerator.cs spread across two different plugins/assets/packages? You wouldn’t know which one. Neither would the IDE because now you couldn’t double-click the line to jump to that given file (unless metadata is preserved and passed on to the IDE).
Every single piece of information up there could be useful in some context.
Source: I have debugged… a LOT.
This happens CONSTANTLY… overloaded methods are everywhere, namespace-differentiated classes / methods are even more common… and often bugs are located in a subtle interaction between the overloaded function variants.
If you want to howl about console callstack deficiencies, howl about the fact that IL2CPP crashes STILL (at least at my writing using Unity2021) do not show the actual line number of the original C# code that crashed.
That single deficiency is responsible for more Debug.Log() statement insertion and debugger attachment than any other thing in the Unity ecosystem.
Off course all remains clickable.
In your case the visual noise is reduced by only showing delta path …/Path1/Path2/WorldGenerator.cs:50.