How to set "Busy", "Looking for Trade", "Looking to Play" statuses with the new UI

[Hrcak]

Hi there,

Here's one of the ways to get back the mentioned statuses.

All we have to do is to create a shortcut that starts the Steam with specific parameter.

To do this :

Find the shortcut used to start the Steam.
Duplicate it using Copy/Paste.
Right Click on the created copy of the shortcut -> Properties
In the "Target:" field you will find a path :
"C:\Program Files (x86)\Steam\Steam.exe"

At the end of this path, add one of the following lines to get the desired status :

Busy:
steam://friends/status/busy

Looking to Trade:
steam://friends/status/trade

Looking to Play :
steam://friends/status/play

Notes:
You can only use one status per shortcut.
Copy the lines for the desired status and paste them without the quotes, but after the last quotation mark. For example :

Correct:
"C:\Program Files (x86)\Steam\Steam.exe" steam://friends/status/busy

You can simply double click on the shortcut while the Steam is running, to change your status.

Limited Alternative #2 :
Steam -> Settings -> Interface -> Set Taskbar Preferences
Tick : Busy and confirm.

This should now allow you to set your status to "Busy" using the context menu on Steam taskbar Icon.

[Collision]

There's another way around the Busy status but it's useless for me since I switched to the web browser chat. The client chat is so bugged.

[Boris]

everything is bugged if you try any new method, only luck, anyways new steam should get updates ....

[Philuu]

Originally posted by Hrcak:

Busy:
steam://friends/status/busy

Looking to Trade:
steam://friends/status/trade

Looking to Play :
steam://friends/status/play

Don't know if this counts as necro or not but if anyone is looking to use these Statuses, those lines can also be used on the fly when executing them per "Run" aka. Win + R.

[Eddooo - False Trade Ban]

does this still work ?

[Watermelon {JESUS IS LORD}]

Originally posted by Eddooo⇄Trading:

does this still work ?

yes

[76561199407495642]

This thread was quite old before the recent post, so we're locking it to prevent confusion.