• 如果可以的話，請轉貼螢幕顯示的錯誤訊息。

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

• 請說明你當時想做什麼，你做了什麼，然後發生了什麼事

• 你的瀏覽器是什麼？

• 請轉貼未翻譯的英文字句。 建議將此錯誤的螢幕截圖上傳到 Imgur.com 並轉貼連結。

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

• 這些文字存在於 翻譯系統 中嗎？若為真，其是否已被翻譯超過 24 小時？

• 你的瀏覽器是什麼？

• 請簡明精確地解釋你的建議，以便讓人一目了然。

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

• 你的瀏覽器是什麼？

• 當你不能動作時，螢幕上顯示什麼？（螢幕全黑？部份遊戲介面？錯誤訊息？）

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

• 你的瀏覽器是什麼？

• 遊戲規則的哪部分在 BGA 版本有所錯漏？

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

• 這項違反規則之處可否在遊戲重播中看到？若可以是在哪步？（重播時左上角資訊）

• 你的瀏覽器是什麼？

• 你當時想採取哪個遊戲行動？

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

• 你想觸發這個遊戲行動時做了什麼？

• 當你試著這麼做時發生了什麼（錯誤訊息、遊戲狀態條訊息...）？

• 你的瀏覽器是什麼？

• 問題發生在遊戲的哪一步？（目前遊戲指示是什麼）

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

• 當你試著進行遊戲動作時發生了什麼（錯誤訊息、遊戲狀態條訊息...）？

• 你的瀏覽器是什麼？

• 請描述顯示問題。 建議將此錯誤的螢幕截圖上傳到 Imgur.com 並轉貼連結。

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

• 你的瀏覽器是什麼？

• 請轉貼未翻譯的英文字句。 建議將此錯誤的螢幕截圖上傳到 Imgur.com 並轉貼連結。

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

• 這些文字存在於 翻譯系統 中嗎？若為真，其是否已被翻譯超過 24 小時？

• 你的瀏覽器是什麼？

• 請簡明精確地解釋你的建議，以便讓人一目了然。

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

• 你的瀏覽器是什麼？