Last Man Standing

The `claimThrone()` function incorrectly uses the following check:

​

```javascript

require(msg.sender == currentKing, "Game: You are already the king. No need to re-claim.");

```

​

- This logic enforces that only the current king can call `claimThrone()`,

​

which defeats the purpose of the game where new players are supposed to challenge the king** by sending more ETH.

​

The message suggests that it’s meant to prevent the same address from reclaiming the throne,

​

but the logic does the opposite: it **only allows the current king to re-claim.

​

- This breaks the game by not letting new challengers participate.

​

​

​

1. Game Dynamics: Breaks player competition by locking the throne

​

2. Funds Stuck: No one can increase the pot, game is frozen

​

3. User Frustration: Players cannot participate even with higher bid

```javascript

address currentKing = alice;

​

claimThrone{value: 2 ether}(); // from Bob's address

​

require(msg.sender == currentKing, "Game: You are already the king.");

```

​

-> Expected behavior: Bob should be allowed to claim the throne if he sends more ETH than the current king.

​

-> Actual behavior: Only Alice can call the function, defeating the purpose of competitive king-of-the-hill dynamics.

​

```diff

function claimThrone() external payable gameNotEnded nonReentrant {

require(msg.value >= claimFee, "Game: Insufficient ETH sent to claim the throne.");

// remaining code

​

```