Page 1 of 1

Alhambra: scoring irregularity, bad advice, can't move a piece, and colour change request.

Posted: 03 November 2020, 04:18
by winterbadger
In the Alhambra match I'm playing with friends right now, we had the initial scoring round, and the game awarded me points for one tile I had in stock and did not award me points for another tile I had in stock. Surely *none* of the tiles in stock should count for scoring?

If I go to place a tile from my stock, the game tells me I can do that later, that I should buy a new tile or take money first. Of course, if I do either of those things. Of course, if I do either of those things, then I can't place a tile from my stock in the same turn.

I want to put another piece in stock from my board. I hover over the piece, but no X appears. An X appears if I hover over my starting tile, which of course makes no sense since one can't move the start tile to stock.

Finally, I really dislike having the blank spaces adjacent to one's tiles the same colour as the background of the tiles. It makes it look as if one can place tiles *adjacent* to them, which of course one can't. Please make them a different colour!!!

Re: Alhambra: scoring irregularity, bad advice, can't move a piece, and colour change request.

Posted: 03 November 2020, 04:55
by winterbadger
More problems.

Trying to move tiles to stock that are in a legal position to remove, but the app won't let the player do so. The (x) sign won't even show up. The (x) mark *does* show up over other tiles, tiles that shouldn't be moved, but not when the cursor is over those tiles--only when it's over adjacent tiles.

Also, a newly purchased piece can't be placed on a spot it ought legally to be playable; instead, the app drops the tile in a nearby space and won't let the player retract the placement.

Most of these problems seem to be most severe when the tile map shrinks because the player has created a pattern that's very wide. The tiles get very small, and the location of the cursor on the screen doesn't seem to be where the program is reading it.

Love the game, but this implementation has a LOT of problems! :(