• Please copy/paste the error message you see on your screen, if any.

As on the Tumbleweed site, it would be nice to have an option when hovering over a hex to see if it's a viable placement and, if so, what number would be placed there based on its current line of sight. This is especially useful when first learning the game.

I'm not sure if implementing this would slow down the system too much, but perhaps there's a way to do it so that the hexes don't have to be recalculated with every hover and rather just keeping track of line of sight on every cell and updating affected cells incrementally when new pieces are placed (I'm not a coder!).

Thanks for your amazing work on this and your consideration!

• Please explains what you wanted to do, what you do and what happened

• What is your browser?

• Please copy/paste the text displayed in English instead of your language. If you have a screenshot of this bug (good practice), you can use Imgur.com to upload it and copy/paste the link here.

As on the Tumbleweed site, it would be nice to have an option when hovering over a hex to see if it's a viable placement and, if so, what number would be placed there based on its current line of sight. This is especially useful when first learning the game.

I'm not sure if implementing this would slow down the system too much, but perhaps there's a way to do it so that the hexes don't have to be recalculated with every hover and rather just keeping track of line of sight on every cell and updating affected cells incrementally when new pieces are placed (I'm not a coder!).

Thanks for your amazing work on this and your consideration!

• Is this text available in the translation system? If yes, has it been translated for more than 24 hours?

• What is your browser?

• Please explain your suggestion precisely and concisely so that it's as easy as possible to understand what you mean.

As on the Tumbleweed site, it would be nice to have an option when hovering over a hex to see if it's a viable placement and, if so, what number would be placed there based on its current line of sight. This is especially useful when first learning the game.

I'm not sure if implementing this would slow down the system too much, but perhaps there's a way to do it so that the hexes don't have to be recalculated with every hover and rather just keeping track of line of sight on every cell and updating affected cells incrementally when new pieces are placed (I'm not a coder!).

Thanks for your amazing work on this and your consideration!

• What is your browser?

• What was displayed on the screen when you were blocked (Blank screen? Part of the game interface? Error message?)

As on the Tumbleweed site, it would be nice to have an option when hovering over a hex to see if it's a viable placement and, if so, what number would be placed there based on its current line of sight. This is especially useful when first learning the game.

I'm not sure if implementing this would slow down the system too much, but perhaps there's a way to do it so that the hexes don't have to be recalculated with every hover and rather just keeping track of line of sight on every cell and updating affected cells incrementally when new pieces are placed (I'm not a coder!).

Thanks for your amazing work on this and your consideration!

• What is your browser?

• Which part of the rules was not respected by the BGA adaptation

As on the Tumbleweed site, it would be nice to have an option when hovering over a hex to see if it's a viable placement and, if so, what number would be placed there based on its current line of sight. This is especially useful when first learning the game.

I'm not sure if implementing this would slow down the system too much, but perhaps there's a way to do it so that the hexes don't have to be recalculated with every hover and rather just keeping track of line of sight on every cell and updating affected cells incrementally when new pieces are placed (I'm not a coder!).

Thanks for your amazing work on this and your consideration!

• Is the rules violation visible on game replay? If yes, at which move number?

• What is your browser?

• Which was the game action you wanted to do?

As on the Tumbleweed site, it would be nice to have an option when hovering over a hex to see if it's a viable placement and, if so, what number would be placed there based on its current line of sight. This is especially useful when first learning the game.

I'm not sure if implementing this would slow down the system too much, but perhaps there's a way to do it so that the hexes don't have to be recalculated with every hover and rather just keeping track of line of sight on every cell and updating affected cells incrementally when new pieces are placed (I'm not a coder!).

Thanks for your amazing work on this and your consideration!

• What do you try to do to trigger this game action?

• What happened when you try to do this (error message, game status bar message, ...)?

• What is your browser?

• At which step of the game did the problem occurs (what was the current game instruction)?

As on the Tumbleweed site, it would be nice to have an option when hovering over a hex to see if it's a viable placement and, if so, what number would be placed there based on its current line of sight. This is especially useful when first learning the game.

I'm not sure if implementing this would slow down the system too much, but perhaps there's a way to do it so that the hexes don't have to be recalculated with every hover and rather just keeping track of line of sight on every cell and updating affected cells incrementally when new pieces are placed (I'm not a coder!).

Thanks for your amazing work on this and your consideration!

• What happened when you try to do a game action (error message, game status bar message, ...)?

• What is your browser?

• Please describe the display issue. If you have a screenshot of this bug (good practice), you can use Imgur.com to upload it and copy/paste the link here.

As on the Tumbleweed site, it would be nice to have an option when hovering over a hex to see if it's a viable placement and, if so, what number would be placed there based on its current line of sight. This is especially useful when first learning the game.

I'm not sure if implementing this would slow down the system too much, but perhaps there's a way to do it so that the hexes don't have to be recalculated with every hover and rather just keeping track of line of sight on every cell and updating affected cells incrementally when new pieces are placed (I'm not a coder!).

Thanks for your amazing work on this and your consideration!

• What is your browser?

• Please copy/paste the text displayed in English instead of your language. If you have a screenshot of this bug (good practice), you can use Imgur.com to upload it and copy/paste the link here.

As on the Tumbleweed site, it would be nice to have an option when hovering over a hex to see if it's a viable placement and, if so, what number would be placed there based on its current line of sight. This is especially useful when first learning the game.

I'm not sure if implementing this would slow down the system too much, but perhaps there's a way to do it so that the hexes don't have to be recalculated with every hover and rather just keeping track of line of sight on every cell and updating affected cells incrementally when new pieces are placed (I'm not a coder!).

Thanks for your amazing work on this and your consideration!

• Is this text available in the translation system? If yes, has it been translated for more than 24 hours?

• What is your browser?

• Please explain your suggestion precisely and concisely so that it's as easy as possible to understand what you mean.

As on the Tumbleweed site, it would be nice to have an option when hovering over a hex to see if it's a viable placement and, if so, what number would be placed there based on its current line of sight. This is especially useful when first learning the game.

I'm not sure if implementing this would slow down the system too much, but perhaps there's a way to do it so that the hexes don't have to be recalculated with every hover and rather just keeping track of line of sight on every cell and updating affected cells incrementally when new pieces are placed (I'm not a coder!).

Thanks for your amazing work on this and your consideration!

• What is your browser?