You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Hitting play just defaults to whatever SubAccount of the Battle.net Account you where signed in for the game (WoW being the example here).
Expected behavior
Kind of recreate this
The text was updated successfully, but these errors were encountered:
Then - research if it this is possible to run different game version from using command line args.
Currently plugin calls <path_to_battlenet_exe> --exec="launch WOW" that calls default one.
For example you can run from cmd console:
Actually I think we should make transition from battlenet cmd line arguments to direct game exe arguments like it is done in desktop shortcuts created via battlenet for example:
"C:\Games\World of Warcraft\World of Warcraft Launcher.exe" --productcode=wow_classic
this makes bnet open with proper game selected. Do not tested with ptr-s. @yoshimo, can you check, please?
Describe the bug
Hitting play just defaults to whatever SubAccount of the Battle.net Account you where signed in for the game (WoW being the example here).
Expected behavior
Kind of recreate this
The text was updated successfully, but these errors were encountered: