Is there any way to get the signed in user's display name without calling EOS_Platform_GetUserInfoInterface(e.g.when offline)?

Assuming a game is only launched from the Epic Launcher, is there some way to retrieve the display name of the user who launched the game without without using EOS_Platform_GetUserInfoInterface?

Specifically: is it possible to get the display name of the user who launched the game when the game is launched in offline mode?

Yes, the Epic Games Launcher will provide the Epic display name of the local user as one of the launch arguments passed to your game.

The argument is named “epicusername”, and will have the following format: **-**epicusername=“Alice”

ah nice! from the docs it didn’t sound like that was necessarily the same as the “Display Name” from their user info.

[Content removed] Thomas​ is there any chance you could point me at the docs for the launcher command line stuff?

I was looking at https://dev.epicgames.com/docs/epic-games-store/testing-guide#offline-mode-support

Which makes it sound like `-epicusername` & `-epicuserid` are only passed when in offline mode.

I’ve been unable to find a page which explains what command line parameters are passed and in what circumstances.

I can confirm that these are also passed when online. I’ve just written a knowledge base article about this, since I was also unable to find it in the docs.

I’ll work with the documentation team to discuss adding a full summary of all launch arguments passed by the launcher in one place.

[Content removed]

awesome - Thanks Ieuan, you’re a star :smiley:

is there any explicit way to detect “offline mode” from the launch parameters?

or do you just assume offline if there’s no exchange token (i.e. if -authPassword is missing / empty)?

I’ve spoken with the launcher team, and they’ve confirmed that there is currently no explicit flag to detect that the game was launched in offline mode.

Additionally, it’s not safe to assume that the absence of an exchange code conclusively indicates connectivity issues, as it may instead indicate an account service issue.

Our recommendation, therefore, would be to check for the exchange code and, if absent, make your own checks to determine connectivity status where necessary (e.g., OS APIs).

thanks ieuan - appreciated.