Cool idea, but I don't think it makes sense for there to be both a Player class and a warrior object. They seem like they are/should be one in the same. At the very least, I think behind the scenes, the Player class should look more like this such that the warrior object is always available, and I don't need to pass it around from method to method that I define. e.g.:

    class Player
      attr_reader :warrior

      def initialize(warrior)
        @warrior = warrior
      end

      def play_turn
        # I can now access `warrior` here or in any other methods I write
      end
    end