Smaller waiting room id

[ClaudeZsb]

PlayerGlobal: {
  keySchema: {
    addr: "address",
  },
  schema: {
    roomId: "bytes32",
    gameId: "uint32",
    status: "PlayerStatus",
  },
},

First of all, roomId is reusable. Then a field of 2**256 seems to be too large and produces waste of storage. PlayerGlobal can be limited into just one slot if we use uint128 instead. Then any read or write of this table could be more gas efficient.

[aLIEzsss4]

When displaying the waiting room, if the room owner has not exited, the room will continue to exist. Therefore, we need to add a last updated time for sorting, to ensure active rooms are seen by players.