feed back [ test on July 29 ]

[ClaudeZsb]

• bad UX. When you buy an hero in altar, the last unsold hero would move to the slot where the bought hero previously was. This is becase we technically implement a pop operation of an array through replacing the popped one by the last one.
  1. One way to resolve it is that on the client side, we internally write down and update the index of each hero in the altar after buying and keep each unsold hero as unmoved to player.
  2. The other way is that we update the hero altar to an array of constant length. @noyyyy
• bad UX. The same issue of hero inventory as the previous one.
• bad UX. Sometimes, it takes a long time for loading hero images. @noyyyy
• front-end bug. When you have more than 1 hero on your board, all replacing operations of an hero on board only apply to the last one you put on board. @aLIEzsss4
• contract bug. Once there were 3 Juggs of the same tier, but they were not merged. When the 4th Jugg was bought, 2 of 3 Juggs did merged with the bought one. @ClaudeZsb
• mud indexer bug. A while after starting a game, values of tables were not synced and updated. @noyyyy
• contract bug. In the case of 3 players, sometimes two players had the same other player as their opponent. @ClaudeZsb

[ClaudeZsb]

Fot the 1st and 2nd, using a constant array would be easier. And compared to the other resolution, it handles also the scenario where a player refreshed the window during the game.

[ClaudeZsb]

Both of two contract bugs are not fully tested out.

But I did found another one and fixed it.

More detail could be found in #62