[Bug] Millennium Tries Logging Info To A Drive That Doesn't Exist

[PaxGunner]

Before Reporting

• I found no existing issues matching my bug
• My issue is not caused by a theme
• My issue is not caused by a plugin

Describe the Bug

After installing Millennium, it installs successfully however it will fail to open Steam because of info being written to a drive that doesn't exist.
Opening Steam with -dev shows errors, & opening %steam%/ext/millennium.ini show's Millennium trying to a non-existant drive.

[PackageManager]
devtools = no
dev_packages = no
auto_update_dev_packages = yes
use_pip = yes
python = B:\Steam\ext\data\cache\python.exe
pip_logs = B:\Steam\ext\data\logs\pacman.log
pip_boot = B:\Steam\ext\data\logs\pip_boot.log

[Settings]
check_for_updates = yes
enabled_plugins = core
useinterface = yes

^ for reference, I have no B drive, only C & D.
Opening %steam%/ext/millennium.ini and changing the drive letter to the correct one will fix it.

Expected Behavior

When opening Steam it will give the message "Debugger paused in another tab, click to switch to that tab", which will appear either while Steam logs into your account, or when Steam's full application tries opening. If you click to open the other tab, it will either be unresponsive and Steam will crash, or it will launch Steam in the other tab with all Millennium features disabled.

Steps To Reproduce

1. Install Millenium
2. Millennium will try writing to a non-existant drive
3. Steam won't start because of the error above

Operating System

Windows

Anything else?

No response