Dhoomstriker
Girlie Builder
- Joined
- Aug 12, 2006
- Messages
- 13,474
SGOTM Settler and Warrior moves with a goal-oriented approach
The way I see it, the moves of the Warrior and the Settler are intricately interlinked.
Where we move the Warrior and possibly move the Settler will depend upon our initial mindset.
For example, if we are seriously going to consider settling on the Coast to grab the Fish + Corn + whatever else we can get, then we'll want to use our Warrior to determine where on the Coast to settle.
One Coastal location is where the Warrior is standing, but going there relative to 1N of where the Warrior is standing does not seem like it would be a good place to go, as where the Warrior is standing gets us 2 Ocean squares, 1 Coast square, 1 Plains square, and 1 Plains Riv For (plus possibly a Resource) square versus settling 1N of the Warrior giving us 1 GRiv For square, 2 Plains squares (which may or may not contain Resources), 1 Coast square, and 1 unknown square.
So, call 1N of the Warrior "Coast A." (The location of where the Warrior is standing doesn't even get its own name, haha).
"Coast B" would be 1SE of the Settler (1W of the Warrior) on the GFor. That square gives us more Riverside squares and less Coast squares, but it may miss out on a Seafood Resource, should a Seafood Resouce be there.
"Coast C" might be 2N of the Warrior--it's hard to tell--if the square 3N of the Fish (NE + E of the G Corn) is a Coast square, then 2N of the Warrior would be a Coastal location.
So, let's say that we decided we almost certainly wanted to settle on the Coast with our capital. Let's also say that we were willing to give up the Riverside squares in hopes of getting some randomly-good squares in the fog to the north of our Warrior.
In that case, we know that we would be moving our Settler toward the Coast and thus we could use our Warrior with that assumption in mind. Sending the Warrior 1SW GH would be one way to check that by NOT settling 1SE on the GFor, we wouldn't be missing out on any Resources... and if no Resources were revealed, the Settler could move 1NE G Corn and then 1 E onto the "Coast C" square.
We'd move there instead of to "Coast A" since we would be out of movement points for the Settler regardless of which location we went to, while we could then settle in either Coast A or Coast C location on Turn 1 (the first turn of the game is Turn 0), assuming that we didn't have a really bad stroke of luck with a Forest growing at the Coast A location.
We'd then know what the area around Coast C looked like--it might not even be Coast--and could pick between Coast A and Coast C (unless Coast C is not on the Coast).
Alternatively, if we knew that we wanted to settle on the Coast but we thought that getting some Riverside squares was important, we'd send our Warrior 1NE PFor. In that way, we'd confirm that we didn't reveal any additional Seafood squares that a Coast A or Coast C location might pick up and thus we would confidently move our Settler 1SE on the GFor location, aka Coast B. If we spotted a Seafood Resource with the Warrior, we'd then decide if that Seafood Resource outweighed having some additional Riverside squares within our capital's big fat cross.
Now, all of that thought process is done with the initial goal in mind of wanting to settle on the Coast. If we go in with a mindset of not wanting to settle on the Coast, it's a totally different ball game.
For example, let's say that we do agree that we want to move the Settler 1W, with the plan of keeping most of the River squares and the Corn, but with the hopes of picking up something else nice randomly.
In that case, it depends upon what we'd be willing to do based on what the Warrior saw.
For example, if the Warrior revealed 1 more Coastal Fish, would we be willing to move to the Coast? If yes, then moving the Warrior 1NE might make more sense, so that we can feel good about ignoring the Coast and moving inland.
Moving the Warrior 1SW onto the GH wouldn't actually reveal any squares that were in our original fat cross that we would be losing, so it would actually be a pretty useless move in this case.
Assuming, however, that we were dead set on not going to the Coast, our strongest Warrior move in this scenario would be to move the Warrior 1NW GFor (1S of the G Corn) and then 1NW GFor (1W of the G Corn). Doing so reveals the two squares that are 1E and 1N of the G Corn that we would get by settling in place... we'd be confirming that we weren't missing out on Plains Marble or something, and would reveal a few more squares to the north, which might help us decide if we think that it would be worth moving the Settler yet again.
What I'm getting at is that I would like to get away from the idea of "let's vote where to move the Warrior first and then decide what to do" and replace it with "let's vote on the top few Warrior-combined-with-Settler movements, but be willing to alter those choices based on what we see."
For example, some might be:
a) We might settle on the Coast if it is nice but otherwise want to head west instead of settling in place
T0
i. Warrior moves 1NE PFor (1N of the Fish)
ii. Settler moves 1W GRiv For
T1
iii. Warrior probably moves 1NW or 1N, but it won't really give us much info anyway
b) We don't want a Coastal capital but want to head west with the Settler
T0
i. Warrior moves 1NW GFor (1S of the G Corn)
ii. Settler moves 1W GRiv For
T1
iii. Warrior moves 1NW GFor (1W of the G Corn)
c) We want a Coastal capital and we want to keep as many Riverside squares as possible
T0
i. Warrior moves 1NE PFor (1N of the Fish)
ii. Based on what the Warrior reveals, we move the Settler either 1NE G Corn OR we move the Settler 1SE GFor
d) We want a Coastal capital and we'd like to hope that we can settle 2N of the Warrior and still be coastal, while not minding about missing out on Riverside squares, and also hoping for something nice in the fog to the north of the Warrior
T0
i. Warrior moves 1SW GH (3S of the G Corn)
ii. Settler moves 1NE GCorn (we can pause here)
iii. Settler moves 1E Plains (which we hope, in this scenario, is Coastal)
T1
iv. Warrior can't help us much in deciding
v. Settler settles where he is located if it's Coastal (Coast C) or else moves 1S and settles there (Coast A)
e) We want to move the Settler 1NW with the hopes of picking up more production squares while keeping the Corn and many, but not all, of the River squares (and likely getting 1 less Flood Plains square than moving the settler 1W)
T0
i. The Warrior could optionally move toward the NW, to help with exploring up there, or could move 1SW just to confirm that we aren't losing a GRiv For Deer/Spice/Fur square 2S of where the Settler starts
Other possibilities exist, too. This list is just to get you started thinking about how your initial mindset and settling goals can play a huge role in deciding which information that we can reveal will be useful for making a decision and which information won't affect our decision at all and thus is not worthwhile information to chase after.
The way I see it, the moves of the Warrior and the Settler are intricately interlinked.
Where we move the Warrior and possibly move the Settler will depend upon our initial mindset.
For example, if we are seriously going to consider settling on the Coast to grab the Fish + Corn + whatever else we can get, then we'll want to use our Warrior to determine where on the Coast to settle.
One Coastal location is where the Warrior is standing, but going there relative to 1N of where the Warrior is standing does not seem like it would be a good place to go, as where the Warrior is standing gets us 2 Ocean squares, 1 Coast square, 1 Plains square, and 1 Plains Riv For (plus possibly a Resource) square versus settling 1N of the Warrior giving us 1 GRiv For square, 2 Plains squares (which may or may not contain Resources), 1 Coast square, and 1 unknown square.
So, call 1N of the Warrior "Coast A." (The location of where the Warrior is standing doesn't even get its own name, haha).
"Coast B" would be 1SE of the Settler (1W of the Warrior) on the GFor. That square gives us more Riverside squares and less Coast squares, but it may miss out on a Seafood Resource, should a Seafood Resouce be there.
"Coast C" might be 2N of the Warrior--it's hard to tell--if the square 3N of the Fish (NE + E of the G Corn) is a Coast square, then 2N of the Warrior would be a Coastal location.
So, let's say that we decided we almost certainly wanted to settle on the Coast with our capital. Let's also say that we were willing to give up the Riverside squares in hopes of getting some randomly-good squares in the fog to the north of our Warrior.
In that case, we know that we would be moving our Settler toward the Coast and thus we could use our Warrior with that assumption in mind. Sending the Warrior 1SW GH would be one way to check that by NOT settling 1SE on the GFor, we wouldn't be missing out on any Resources... and if no Resources were revealed, the Settler could move 1NE G Corn and then 1 E onto the "Coast C" square.
We'd move there instead of to "Coast A" since we would be out of movement points for the Settler regardless of which location we went to, while we could then settle in either Coast A or Coast C location on Turn 1 (the first turn of the game is Turn 0), assuming that we didn't have a really bad stroke of luck with a Forest growing at the Coast A location.
We'd then know what the area around Coast C looked like--it might not even be Coast--and could pick between Coast A and Coast C (unless Coast C is not on the Coast).
Alternatively, if we knew that we wanted to settle on the Coast but we thought that getting some Riverside squares was important, we'd send our Warrior 1NE PFor. In that way, we'd confirm that we didn't reveal any additional Seafood squares that a Coast A or Coast C location might pick up and thus we would confidently move our Settler 1SE on the GFor location, aka Coast B. If we spotted a Seafood Resource with the Warrior, we'd then decide if that Seafood Resource outweighed having some additional Riverside squares within our capital's big fat cross.
Now, all of that thought process is done with the initial goal in mind of wanting to settle on the Coast. If we go in with a mindset of not wanting to settle on the Coast, it's a totally different ball game.
For example, let's say that we do agree that we want to move the Settler 1W, with the plan of keeping most of the River squares and the Corn, but with the hopes of picking up something else nice randomly.
In that case, it depends upon what we'd be willing to do based on what the Warrior saw.
For example, if the Warrior revealed 1 more Coastal Fish, would we be willing to move to the Coast? If yes, then moving the Warrior 1NE might make more sense, so that we can feel good about ignoring the Coast and moving inland.
Moving the Warrior 1SW onto the GH wouldn't actually reveal any squares that were in our original fat cross that we would be losing, so it would actually be a pretty useless move in this case.
Assuming, however, that we were dead set on not going to the Coast, our strongest Warrior move in this scenario would be to move the Warrior 1NW GFor (1S of the G Corn) and then 1NW GFor (1W of the G Corn). Doing so reveals the two squares that are 1E and 1N of the G Corn that we would get by settling in place... we'd be confirming that we weren't missing out on Plains Marble or something, and would reveal a few more squares to the north, which might help us decide if we think that it would be worth moving the Settler yet again.
What I'm getting at is that I would like to get away from the idea of "let's vote where to move the Warrior first and then decide what to do" and replace it with "let's vote on the top few Warrior-combined-with-Settler movements, but be willing to alter those choices based on what we see."
For example, some might be:
a) We might settle on the Coast if it is nice but otherwise want to head west instead of settling in place
T0
i. Warrior moves 1NE PFor (1N of the Fish)
ii. Settler moves 1W GRiv For
T1
iii. Warrior probably moves 1NW or 1N, but it won't really give us much info anyway
b) We don't want a Coastal capital but want to head west with the Settler
T0
i. Warrior moves 1NW GFor (1S of the G Corn)
ii. Settler moves 1W GRiv For
T1
iii. Warrior moves 1NW GFor (1W of the G Corn)
c) We want a Coastal capital and we want to keep as many Riverside squares as possible
T0
i. Warrior moves 1NE PFor (1N of the Fish)
ii. Based on what the Warrior reveals, we move the Settler either 1NE G Corn OR we move the Settler 1SE GFor
d) We want a Coastal capital and we'd like to hope that we can settle 2N of the Warrior and still be coastal, while not minding about missing out on Riverside squares, and also hoping for something nice in the fog to the north of the Warrior
T0
i. Warrior moves 1SW GH (3S of the G Corn)
ii. Settler moves 1NE GCorn (we can pause here)
iii. Settler moves 1E Plains (which we hope, in this scenario, is Coastal)
T1
iv. Warrior can't help us much in deciding
v. Settler settles where he is located if it's Coastal (Coast C) or else moves 1S and settles there (Coast A)
e) We want to move the Settler 1NW with the hopes of picking up more production squares while keeping the Corn and many, but not all, of the River squares (and likely getting 1 less Flood Plains square than moving the settler 1W)
T0
i. The Warrior could optionally move toward the NW, to help with exploring up there, or could move 1SW just to confirm that we aren't losing a GRiv For Deer/Spice/Fur square 2S of where the Settler starts
Other possibilities exist, too. This list is just to get you started thinking about how your initial mindset and settling goals can play a huge role in deciding which information that we can reveal will be useful for making a decision and which information won't affect our decision at all and thus is not worthwhile information to chase after.