It would require some changes to the zwift-login.script but is doable for anyone with just a tiny bit of coding skills (see guidance below).

You have to be aware that the passwords are not securely saved, so I would not recommend using zwift-login in a public setting where one user potentially could find the passwords of other users.

The changes needed are:

Line 133: Change
Loop, 5 {
to
Loop, 30 {

After line 229:
Add additional lines for the values 6-30 like this:
Gui, Add, Radio, xp+30 yp gRadioSlot5, 6
et cetera.

Line 760: Change
Loop, 5
to
Loop, 30

Line 895: Add extra blocks for each of the value 6-30 like this:
RadioSlot5:
Slot := 6
SaveSlotToIni()
LoadFromIni()
SetGuiInitialState()
Return

Line 760: Change
Loop, 5
to
Loop, 30

Thanks

Jesper

You’re welcome 🙂

Excellent. I think that solved it for me. (The bottom of the screen still shows “Loading login screen” and “Filling fields”. Just an FYI). Thank you very much.

The sequence always include Change User because it made the internal logic much easier and saves a lot of troubleshooting in scenarios with multiple users of the same Zwift setup.

You can skip it adding the /nouser switch to the start menu shortcut to zwift-login. In your case you could also add /launch – then it will be a fully automated launch of Zwift when you start zwift-login.

I just added the description of /nouser to this page (it was in the latest release notes).

I’m not sure if this is the expected behavior, but why does the sequence “always” involve pressing the “Change User” button? And is there any way where I can skip that?

I’m the only user of Zwift.

My expectation is a single shortcut click, that would automatically “/launch” zwift and takes me straight away to the pairing screen.

Thank you very much.

Unfortunately I do not know of anything similar for macOS.