#118325: "Movement: if expedition member moves back to tile from which it came, treat as undo not as new move"
Mille kohta see veateade on?
Mis juhtus? Palun vali alt
Mis juhtus? Palun vali alt
Palun kontrolli, kas samal teemal on juba aruanne olemas
Kui jah, siis HÄÄLETAGE selle raporti poolt. Kõige rohkem hääli sisaldavatele aruannetele antakse PRIORITEET!
| # | Status | Votes | Game | Type | Title | Last update |
|---|
Detailne kirjeldus
-
• Kui näed ekraanil veateadet, kopeeri see siia.
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 -
• Kirjelda, mida sa soovisid teha, mida sa tegid ja mis juhtus
• mis on sinu veebilehitseja?
Google Chrome v96
-
• Palun kopeeri/kleebi kuvatud tekst inglise keeles, mitte sinu oma keeles. 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. Kas see tekst on kättesaadav tõlkesüsteemis ? Kui jah, kas see on tõlgitud rohkem kui 24 tundi tagasi?
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 • mis on sinu veebilehitseja?
Google Chrome v96
-
• Palun selgita oma ettepanekut täpselt ja lühidalt, et oleks võimalikult lihtne mõista, mida silmas pead.
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 • mis on sinu veebilehitseja?
Google Chrome v96
-
• Mis oli ekraanil, kui sind blokeeriti? (Tühi ekraan? Osa mänguliidesest? Veateade?)
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 • mis on sinu veebilehitseja?
Google Chrome v96
-
• Millist osa BGA kohandamisest ei järgitud
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 reeglite rikkumist on mängu taasesitusel näha? Kui jah, siis mitmendal käigul?
• mis on sinu veebilehitseja?
Google Chrome v96
-
• Milline oli mängu tegevus, mida tahtsid sooritada?
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 -
• Mida püüdsid teha, et seda mängu tegevust käivitada?
-
• Mis juhtus, kui seda proovisite (veateade, mängu olekuriba teade, ...)?
• mis on sinu veebilehitseja?
Google Chrome v96
-
• Millises mängu etapis esines probleem (Mis oli selle mänguetapi instruktsioon)?
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 -
• Mis juhtus, kui proovisite sooritada seda mängu käiku (veateade, mängu olekuriba sõnum, ...)?
• mis on sinu veebilehitseja?
Google Chrome v96
-
• Kirjelda kuvamise probleemi. 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 • mis on sinu veebilehitseja?
Google Chrome v96
-
• Palun kopeeri/kleebi kuvatud tekst inglise keeles, mitte sinu oma keeles. 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. Kas see tekst on kättesaadav tõlkesüsteemis ? Kui jah, kas see on tõlgitud rohkem kui 24 tundi tagasi?
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 • mis on sinu veebilehitseja?
Google Chrome v96
-
• Palun selgita oma ettepanekut täpselt ja lühidalt, et oleks võimalikult lihtne mõista, mida silmas pead.
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 • mis on sinu veebilehitseja?
Google Chrome v96
Aruande ajalugu
Lisa midagi sellele raportile
- Teine laua ID / käigu ID
- Kas F5 lahendas probleemi?
- Kas probleem esines mitmel korral? Igal korral?
- 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.
