#118325: "Movement: if expedition member moves back to tile from which it came, treat as undo not as new move"
What is this report about?
What happened? Please select from below
What happened? Please select from below
Please check if there is already a report on the same subject
If yes, please VOTE for this report. Reports with the most votes are given PRIORITY!
| # | Status | Votes | Game | Type | Title | Last update |
|---|
Detailed description
-
• Please copy/paste the error message you see on your screen, if applicable.
So the subject above is a bit awkwardly phrased due to BGA's character limitations, but here's the idea in full:
When moving an expedition member, I can move it multiple tiles before confirming the entire move—great!
But I notice that if I move it to a tile that I'd previously come from, the interface treats it like a new move... hmm. This is technically legal, but I suggest that a more practical usage would be to have the move treated as /undoing/ the movement to the current tile.
Here's an example: if my member starts on tile A, and I click B > C > D > C, instead of spending all the points to move from A > B > C > D > C as currently happens, the player would be better served by having the interface just spend the points for A > B > C.
I posit that players it would be /exceedingly/ rare for any player to overspend points, but allowing this "contained" undo would be a much more likely, and therefore helpful, case. And in the rare case that a player wants to do A > B > C > D > C, that player could do that in two separate moves: A > B > C > D, then D > C, confirming after both (and the double confirmation will act as a guard against unintentionally overspending on inefficient moves).
Again, any "undoing" is to happen before the move is confirmed, so hopefully this "localized" undo functionality won't have the major cost that you mentioned in boardgamearena.com/bug?id=117454 -
• Please explain what you wanted to do, what you did and what happened
• Which browser are you using?
Google Chrome v96
-
• 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 a picture hosting service of your choice (snipboard.io for example) to upload it and copy/paste the link here. Is this text available in the translation system? If yes, has it been translated for more than 24 hours?
So the subject above is a bit awkwardly phrased due to BGA's character limitations, but here's the idea in full:
When moving an expedition member, I can move it multiple tiles before confirming the entire move—great!
But I notice that if I move it to a tile that I'd previously come from, the interface treats it like a new move... hmm. This is technically legal, but I suggest that a more practical usage would be to have the move treated as /undoing/ the movement to the current tile.
Here's an example: if my member starts on tile A, and I click B > C > D > C, instead of spending all the points to move from A > B > C > D > C as currently happens, the player would be better served by having the interface just spend the points for A > B > C.
I posit that players it would be /exceedingly/ rare for any player to overspend points, but allowing this "contained" undo would be a much more likely, and therefore helpful, case. And in the rare case that a player wants to do A > B > C > D > C, that player could do that in two separate moves: A > B > C > D, then D > C, confirming after both (and the double confirmation will act as a guard against unintentionally overspending on inefficient moves).
Again, any "undoing" is to happen before the move is confirmed, so hopefully this "localized" undo functionality won't have the major cost that you mentioned in boardgamearena.com/bug?id=117454 • Which browser are you using?
Google Chrome v96
-
• Please explain your suggestion precisely and concisely so that it's as easy as possible to understand what you mean.
So the subject above is a bit awkwardly phrased due to BGA's character limitations, but here's the idea in full:
When moving an expedition member, I can move it multiple tiles before confirming the entire move—great!
But I notice that if I move it to a tile that I'd previously come from, the interface treats it like a new move... hmm. This is technically legal, but I suggest that a more practical usage would be to have the move treated as /undoing/ the movement to the current tile.
Here's an example: if my member starts on tile A, and I click B > C > D > C, instead of spending all the points to move from A > B > C > D > C as currently happens, the player would be better served by having the interface just spend the points for A > B > C.
I posit that players it would be /exceedingly/ rare for any player to overspend points, but allowing this "contained" undo would be a much more likely, and therefore helpful, case. And in the rare case that a player wants to do A > B > C > D > C, that player could do that in two separate moves: A > B > C > D, then D > C, confirming after both (and the double confirmation will act as a guard against unintentionally overspending on inefficient moves).
Again, any "undoing" is to happen before the move is confirmed, so hopefully this "localized" undo functionality won't have the major cost that you mentioned in boardgamearena.com/bug?id=117454 • Which browser are you using?
Google Chrome v96
-
• What was displayed on the screen when you were blocked (Blank screen? Part of the game interface? Error message?)
So the subject above is a bit awkwardly phrased due to BGA's character limitations, but here's the idea in full:
When moving an expedition member, I can move it multiple tiles before confirming the entire move—great!
But I notice that if I move it to a tile that I'd previously come from, the interface treats it like a new move... hmm. This is technically legal, but I suggest that a more practical usage would be to have the move treated as /undoing/ the movement to the current tile.
Here's an example: if my member starts on tile A, and I click B > C > D > C, instead of spending all the points to move from A > B > C > D > C as currently happens, the player would be better served by having the interface just spend the points for A > B > C.
I posit that players it would be /exceedingly/ rare for any player to overspend points, but allowing this "contained" undo would be a much more likely, and therefore helpful, case. And in the rare case that a player wants to do A > B > C > D > C, that player could do that in two separate moves: A > B > C > D, then D > C, confirming after both (and the double confirmation will act as a guard against unintentionally overspending on inefficient moves).
Again, any "undoing" is to happen before the move is confirmed, so hopefully this "localized" undo functionality won't have the major cost that you mentioned in boardgamearena.com/bug?id=117454 • Which browser are you using?
Google Chrome v96
-
• Which part of the rules was not followed by the BGA adaptation?
So the subject above is a bit awkwardly phrased due to BGA's character limitations, but here's the idea in full:
When moving an expedition member, I can move it multiple tiles before confirming the entire move—great!
But I notice that if I move it to a tile that I'd previously come from, the interface treats it like a new move... hmm. This is technically legal, but I suggest that a more practical usage would be to have the move treated as /undoing/ the movement to the current tile.
Here's an example: if my member starts on tile A, and I click B > C > D > C, instead of spending all the points to move from A > B > C > D > C as currently happens, the player would be better served by having the interface just spend the points for A > B > C.
I posit that players it would be /exceedingly/ rare for any player to overspend points, but allowing this "contained" undo would be a much more likely, and therefore helpful, case. And in the rare case that a player wants to do A > B > C > D > C, that player could do that in two separate moves: A > B > C > D, then D > C, confirming after both (and the double confirmation will act as a guard against unintentionally overspending on inefficient moves).
Again, any "undoing" is to happen before the move is confirmed, so hopefully this "localized" undo functionality won't have the major cost that you mentioned in boardgamearena.com/bug?id=117454 -
• Is the rules violation visible on game replay? If yes, at which move number?
• Which browser are you using?
Google Chrome v96
-
• What was the game action you wanted to do?
So the subject above is a bit awkwardly phrased due to BGA's character limitations, but here's the idea in full:
When moving an expedition member, I can move it multiple tiles before confirming the entire move—great!
But I notice that if I move it to a tile that I'd previously come from, the interface treats it like a new move... hmm. This is technically legal, but I suggest that a more practical usage would be to have the move treated as /undoing/ the movement to the current tile.
Here's an example: if my member starts on tile A, and I click B > C > D > C, instead of spending all the points to move from A > B > C > D > C as currently happens, the player would be better served by having the interface just spend the points for A > B > C.
I posit that players it would be /exceedingly/ rare for any player to overspend points, but allowing this "contained" undo would be a much more likely, and therefore helpful, case. And in the rare case that a player wants to do A > B > C > D > C, that player could do that in two separate moves: A > B > C > D, then D > C, confirming after both (and the double confirmation will act as a guard against unintentionally overspending on inefficient moves).
Again, any "undoing" is to happen before the move is confirmed, so hopefully this "localized" undo functionality won't have the major cost that you mentioned in boardgamearena.com/bug?id=117454 -
• What did you try to do to trigger this game action?
-
• What happened when you tried to do this (error message, game status bar message, ...)?
• Which browser are you using?
Google Chrome v96
-
• At which step of the game did the problem occur? What was the current game instruction?
So the subject above is a bit awkwardly phrased due to BGA's character limitations, but here's the idea in full:
When moving an expedition member, I can move it multiple tiles before confirming the entire move—great!
But I notice that if I move it to a tile that I'd previously come from, the interface treats it like a new move... hmm. This is technically legal, but I suggest that a more practical usage would be to have the move treated as /undoing/ the movement to the current tile.
Here's an example: if my member starts on tile A, and I click B > C > D > C, instead of spending all the points to move from A > B > C > D > C as currently happens, the player would be better served by having the interface just spend the points for A > B > C.
I posit that players it would be /exceedingly/ rare for any player to overspend points, but allowing this "contained" undo would be a much more likely, and therefore helpful, case. And in the rare case that a player wants to do A > B > C > D > C, that player could do that in two separate moves: A > B > C > D, then D > C, confirming after both (and the double confirmation will act as a guard against unintentionally overspending on inefficient moves).
Again, any "undoing" is to happen before the move is confirmed, so hopefully this "localized" undo functionality won't have the major cost that you mentioned in boardgamearena.com/bug?id=117454 -
• What happened when you tried to do this game action (error message, game status bar message, ...)?
• Which browser are you using?
Google Chrome v96
-
• Please describe the display issue. If you have a screenshot of this bug (good practice), you can use a picture hosting service of your choice (snipboard.io for example) to upload it and copy/paste the link here.
So the subject above is a bit awkwardly phrased due to BGA's character limitations, but here's the idea in full:
When moving an expedition member, I can move it multiple tiles before confirming the entire move—great!
But I notice that if I move it to a tile that I'd previously come from, the interface treats it like a new move... hmm. This is technically legal, but I suggest that a more practical usage would be to have the move treated as /undoing/ the movement to the current tile.
Here's an example: if my member starts on tile A, and I click B > C > D > C, instead of spending all the points to move from A > B > C > D > C as currently happens, the player would be better served by having the interface just spend the points for A > B > C.
I posit that players it would be /exceedingly/ rare for any player to overspend points, but allowing this "contained" undo would be a much more likely, and therefore helpful, case. And in the rare case that a player wants to do A > B > C > D > C, that player could do that in two separate moves: A > B > C > D, then D > C, confirming after both (and the double confirmation will act as a guard against unintentionally overspending on inefficient moves).
Again, any "undoing" is to happen before the move is confirmed, so hopefully this "localized" undo functionality won't have the major cost that you mentioned in boardgamearena.com/bug?id=117454 • Which browser are you using?
Google Chrome v96
-
• 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 a picture hosting service of your choice (snipboard.io for example) to upload it and copy/paste the link here. Is this text available in the translation system? If yes, has it been translated for more than 24 hours?
So the subject above is a bit awkwardly phrased due to BGA's character limitations, but here's the idea in full:
When moving an expedition member, I can move it multiple tiles before confirming the entire move—great!
But I notice that if I move it to a tile that I'd previously come from, the interface treats it like a new move... hmm. This is technically legal, but I suggest that a more practical usage would be to have the move treated as /undoing/ the movement to the current tile.
Here's an example: if my member starts on tile A, and I click B > C > D > C, instead of spending all the points to move from A > B > C > D > C as currently happens, the player would be better served by having the interface just spend the points for A > B > C.
I posit that players it would be /exceedingly/ rare for any player to overspend points, but allowing this "contained" undo would be a much more likely, and therefore helpful, case. And in the rare case that a player wants to do A > B > C > D > C, that player could do that in two separate moves: A > B > C > D, then D > C, confirming after both (and the double confirmation will act as a guard against unintentionally overspending on inefficient moves).
Again, any "undoing" is to happen before the move is confirmed, so hopefully this "localized" undo functionality won't have the major cost that you mentioned in boardgamearena.com/bug?id=117454 • Which browser are you using?
Google Chrome v96
-
• Please explain your suggestion precisely and concisely so that it's as easy as possible to understand what you mean.
So the subject above is a bit awkwardly phrased due to BGA's character limitations, but here's the idea in full:
When moving an expedition member, I can move it multiple tiles before confirming the entire move—great!
But I notice that if I move it to a tile that I'd previously come from, the interface treats it like a new move... hmm. This is technically legal, but I suggest that a more practical usage would be to have the move treated as /undoing/ the movement to the current tile.
Here's an example: if my member starts on tile A, and I click B > C > D > C, instead of spending all the points to move from A > B > C > D > C as currently happens, the player would be better served by having the interface just spend the points for A > B > C.
I posit that players it would be /exceedingly/ rare for any player to overspend points, but allowing this "contained" undo would be a much more likely, and therefore helpful, case. And in the rare case that a player wants to do A > B > C > D > C, that player could do that in two separate moves: A > B > C > D, then D > C, confirming after both (and the double confirmation will act as a guard against unintentionally overspending on inefficient moves).
Again, any "undoing" is to happen before the move is confirmed, so hopefully this "localized" undo functionality won't have the major cost that you mentioned in boardgamearena.com/bug?id=117454 • Which browser are you using?
Google Chrome v96
Report history
Add to this report
- Another table ID / move ID
- Did F5 solve the problem?
- Did the problem appear several times? Every time? Randomly?
- If you have a screenshot of this bug (good practice), you can use a picture hosting service of your choice (snipboard.io for example) to upload it and copy/paste the link here.
