Delegation vs exposing properties

i was looking at facade-like delegation in classes, for example let's suppose that you got the Equipment class ( with Equip() and UnEquip() methods), and then you have a Player class which has a reference to the Equipment.

The way i would implement the Player class is to have some public methods like EquipItem and UnEquipItem, and those methods will delegate the tasks to the Equipment class. Now if the player also has another class that does stuff, like movement, then i would put again some public methods on the Player class that delegates to the Movement class, in a facade-like way. Now one of the disadvantages of the facade pattern is the growing interface the more classes or systems it handles. And let's suppose that i know that in the future, the Player class will have alot more functionality.

I don't know if this is the correct approach, nonetheless i was thinking if it would be possible to expose the Equipment and Movement references as properties, like so:

Class Player
{
     public Equipment equipment { get; set; }
     public Movement movement { get; set; }
}    

Now, i know that exposing the object's state is bad, but this way you have a better control of the growing interface of the class, and have more focused methods on the Player class. So instead of:

player.Equip();

you can do

player.equipment.Equip();

Sooo finally, my question would be what is the best approach in this scenario, or maybe i got something wrong ?. Thanks

PS: the example is from a game area, but the solution doesn't have to be necessarily applicable to games, i just thought it was simple to understand.