the blish logs show the local time stamp. That is usefull because noone really thinks in UTC+0 timezone, but rather in their local time zone. BUT when a user shares their log in discord help channel it is hard to find out for helping people, whether this was a recent log or an hours old log.
example:
13:43:40.8202 | INFO | Blish_HUD.Modules.Pkgs.StaticPkgRepoProvider | Getting module list...
suggested behavior:
Option 1:
keep the local time stamp, but add the UTC timezone behind it.
example:
13:43:40.8202 (UTC+6) | INFO | Blish_HUD.Modules.Pkgs.StaticPkgRepoProvider | Getting module list...
Option 2:
OR add the UTC timezone offset once at top of each log. maybe as a single log message or in a different way
example:
"local time (UTC+3): 13:00:00, UTC time: 10:00:00"
current behavior:
the blish logs show the local time stamp. That is usefull because noone really thinks in UTC+0 timezone, but rather in their local time zone. BUT when a user shares their log in discord help channel it is hard to find out for helping people, whether this was a recent log or an hours old log. example: 13:43:40.8202 | INFO | Blish_HUD.Modules.Pkgs.StaticPkgRepoProvider | Getting module list...
suggested behavior:
Option 1: keep the local time stamp, but add the UTC timezone behind it. example: 13:43:40.8202 (UTC+6) | INFO | Blish_HUD.Modules.Pkgs.StaticPkgRepoProvider | Getting module list...
Option 2: OR add the UTC timezone offset once at top of each log. maybe as a single log message or in a different way example: "local time (UTC+3): 13:00:00, UTC time: 10:00:00"