How should I position the "Remove player" button?

Note: There will always be at least two players, so the first two players won't have the "Remove player" button.


For the view with three players, it seems to make sense to put the "Remove player" button above the top-right corner of the grid:

enter image description here

For the view with three players where the screen is more narrow, it also seems to make sense to put the "Remove player" button above the top-right corner of the grid:

enter image description here

However, on the view with four players and a wide screen, the players are arranged in a grid, and I'm not sure where it'd make sense to place the "Remove player" button.

Having the tier and category selectors to the right of the grid is important because it allows the user to view everything about two players at once, because it's all above the fold for 13+ inch screens.

enter image description here

Option 1: At the top-right corner of the "player box". Looks really awkward, but I'm having trouble articulating why. Also, there's the downside of it not being consistent with where it's positioned in the other views.

enter image description here

Option 2: Above the top-right corner of the grid (like the other views). Seems decent, but the button doesn't feel like it's associated with the tier and category selectors. Users of the app will probably understand that those components are part of "the player", and thus that they'll also be removed, but it isn't as intuitive as I'd like.

enter image description here

Option 3: Above the top-right corner of the tier selector. In this position, it seems more clear to me that the tier and category components will be removed as well. The downside though is that it's inconsistent with the placement in the other views (in the other views, it is above the top-right corner of the grid).

enter image description here

Option 4: To the right of the equity text. It doesn't pop out this way. You have to read the text to realize what it is. When it's positioned alone, I think UI conventions prime the user to expect some sort of remove/close button.

enter image description here