#118325: "Movement: if expedition member moves back to tile from which it came, treat as undo not as new move"
Apie ką šis pranešimas?
Kas nutiko? Pasirinkite iš žemiau esančio sąrašo
Kas nutiko? Pasirinkite iš žemiau esančio sąrašo
Patikrinkite, ar jau yra pranešimas apie tą patį dalyką
Jei taip, balsuokite už šią ataskaitą. Ataskaitos su dauguma balsų pateikiamos PRIORITETU!
| # | Status | Votes | Game | Type | Title | Last update |
|---|
Detalus apibūdinimas
-
• Jei ekrane matote kokį nors klaidos pranešimą, įklijuokite jį čia.
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 -
• Prašome paaiškinti, ką norėjote padaryti, ką padarėte ir kas atsitiko
• Kokia tavo naršyklė?
Google Chrome v96
-
• Prašome nukopijuoti / įklijuoti tekstą, rodomą anglų kalba, o ne savo kalba. 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. Ar šis tekstas yra translation system? Jei taip, ar jis buvo išverstas daugiau nei 24 valandas?
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 • Kokia tavo naršyklė?
Google Chrome v96
-
• Prašome paaiškinti siūlomą pakeitimą tiksliai ir glaustai, kad būtų kuo lengviau suprasti, ką jūs siūlote.
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 • Kokia tavo naršyklė?
Google Chrome v96
-
• Kas buvo pavaizduota ekrane, tave užblokavus (juodas ekranas? Nepilna žaidimo sąsaja? Klaidos pranešimas?)
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 • Kokia tavo naršyklė?
Google Chrome v96
-
• Į kurias taisykles neatsižvelgiama BGA žaidimo versijoje
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 -
• Ar taisyklių pažeidimas matomas žaidimo atkartojime? Jeigu taip, kuris veiksmo numeris?
• Kokia tavo naršyklė?
Google Chrome v96
-
• Kurį žaidimo veiksmą norėjai atlikti?
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 -
• Ką reikia padaryti, kad iššauktum šį žaidimo veiksmą?
-
• Kas įvyko kai bandei tai padaryti (klaidos pranešimas, žaidimo būsenos pranešimas, ...)?
• Kokia tavo naršyklė?
Google Chrome v96
-
• Kuriuo žaidimo metu problema atsirado (koks buvo tuometinis žaidimo nurodymas)?
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 -
• Kas įvyko kai bandei atlikti žaidimo veiksmą (klaidos pranešimas, žaidimo būsenos pranešimas, ...)?
• Kokia tavo naršyklė?
Google Chrome v96
-
• Aprašykite rodomą problemą. 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 • Kokia tavo naršyklė?
Google Chrome v96
-
• Prašome nukopijuoti / įklijuoti tekstą, rodomą anglų kalba, o ne savo kalba. 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. Ar šis tekstas yra translation system? Jei taip, ar jis buvo išverstas daugiau nei 24 valandas?
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 • Kokia tavo naršyklė?
Google Chrome v96
-
• Prašome paaiškinti siūlomą pakeitimą tiksliai ir glaustai, kad būtų kuo lengviau suprasti, ką jūs siūlote.
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 • Kokia tavo naršyklė?
Google Chrome v96
Raportų istorija
Papildyti šį raportą
- Kitas stalo ID / ėjimo ID
- Ar F5 išsprendė šią problemą?
- Ar problemos atsirado keletą kartų? Kiekvieną kartą? Atsitiktiniu metu?
- 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.
