#118325: "Movement: if expedition member moves back to tile from which it came, treat as undo not as new move"
Kāds ir šis ziņojums?
Kas notika? Lūdzu izvēlies no zemākredzamajiem
Kas notika? Lūdzu izvēlies no zemākredzamajiem
Lūdzu, pārbaudiet, vai par šo pašu tēmu jau ir ziņojums
Ja jā, lūdzu, balsojiet par šo ziņojumu. Ziņojumiem ar vislielākajām balsīm tiek dota PRIORITĀTE!
| # | Status | Votes | Game | Type | Title | Last update |
|---|
Detalizēts apraksts
-
• Lūdzu nokopē/ielīmē kļūdas ziņu, ko redzi ekrānā, ja tāda ir.
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 -
• Lūdzu paskaidro, ko Tu vēlējies darīt, ko Tu izdarīji un kas notika
• Kāda ir Tava pārlūkprogramma?
Google Chrome v96
-
• Lūdzu iekopē tekstu, kas redzams angļu, nevis tavā valodā. 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. Vai šis teksts ir pieejams tulkošanas sistēmā? Ja jā, vai tas ir ticis tulkots pēdējo 24 stundu laikā?
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āda ir Tava pārlūkprogramma?
Google Chrome v96
-
• Lūdzu, paskaidrojiet savu ieteikumu precīzi un kodolīgi, lai tas būtu pēc iespējas vieglāk saprotams.
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āda ir Tava pārlūkprogramma?
Google Chrome v96
-
• Kas tika attēlots ekrānā, kad Tu tiki bloķēts (tukšs ekrāns? Daļa no spēles interfeisa? Ziņa par kļūdu?)?
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āda ir Tava pārlūkprogramma?
Google Chrome v96
-
• Kura noteikumu daļa netika ņemta vērā BGA versijā?
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 -
• Vai noteikumu pārkāpums ir redzams spēles atkārtojumā? Ja jā, tad kurā gājienā?
• Kāda ir Tava pārlūkprogramma?
Google Chrome v96
-
• Kādu spēles darbību Tu vēlējies veikt?
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 -
• Ko tu dari, lai panāktu šo spēles darbību?
-
• Kas notika, kad veicāt šo darbību (kļūdas paziņojums, spēles informācijas paziņojums,...)?
• Kāda ir Tava pārlūkprogramma?
Google Chrome v96
-
• Kurā spēles solī problēma parādījās (kas bija tā brīža spēles instrukcija)?
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 notika, kad mēģinājāt veikt spēles darbību (kļūdas paziņojums, spēles informācijas paziņojums,...)?
• Kāda ir Tava pārlūkprogramma?
Google Chrome v96
-
• Lūdzu aprakstiet radušos problēmu. 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 • Kāda ir Tava pārlūkprogramma?
Google Chrome v96
-
• Lūdzu iekopē tekstu, kas redzams angļu, nevis tavā valodā. 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. Vai šis teksts ir pieejams tulkošanas sistēmā? Ja jā, vai tas ir ticis tulkots pēdējo 24 stundu laikā?
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āda ir Tava pārlūkprogramma?
Google Chrome v96
-
• Lūdzu, paskaidrojiet savu ieteikumu precīzi un kodolīgi, lai tas būtu pēc iespējas vieglāk saprotams.
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āda ir Tava pārlūkprogramma?
Google Chrome v96
Ziņojuma vēsture
Pievieno kaut ko šim ziņojumam
- Cita galda ID / gājiena ID
- Vai F5 atrisināja šo problēmu?
- Vai šī problēma parādās vairākas reizes? Katru reizi? Nekonkrētās reizēs?
- 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.
