0001416: Retreat / Surrender sends hero to the left Tavern slot only - H3 used both slots to place them

View Revisions: Issue #1416		[ All Revisions ] [ Back to Issue ]
Summary	0001416: Retreat / Surrender sends hero to the left Tavern slot only - H3 used both slots to place them

Revision	2013-08-21 15:42 by Zamolxis
Description	H3 was making use of both slots, giving player the chance to keep 2 of the best heroes recently retreated or surrendered. I'm not very sure about the exact pattern and I didn't find info on this in Strategija. I played a bit with the VCMI_Tests map in WoG, retreating / surrendering each of the 8 heroes in different orders, and noticed the following: - first retreated/surrendered hero went into the left Tavern slot - from the 2nd onward, as long as I kept retreating only, they all went to the right slot (leaving the 1st retreated/surrendered hero there) - this went on until I surrendered with a hero, which went as well to the right slot; but after that, the next retreated/surrendered hero went to the left slot, overriding the hero that's been sitting there for a while. So H3 seems to prioritize surrendered heroes, to keep them there as long as possible; but if we have 2 surrendered heroes, the one who surrendered first (pending there unhired the longest) will be lost & replaced by the next hero retreating/surrendering. H3 does not look at hero/army strengths though: I had a retreating hero override the first surrendered hero, even though it was stronger (level, artifacts, army) than the second surrendered hero. This was a bit of a bummer, but the odds of having 2 surrendered heroes, and no chance to hire the best of them until you have to retreat/surrender another, are pretty small, so I guess we shouldn't bother to further tweak the H3 logic on that. My assumption of the OH3 pattern is the following: 1. Look, from left to right, for the "most vulnerable" hero to be replaced. In order, that would be the Default (randomly generated weekly) hero, considered weaker than a Retreated hero, which is weaker than a Surrendered hero. i.e.: so if a Default hero is found in the left slot, the algorithm stops here as that's the one replaced. 2. If both slots have retreated heroes, or both have surrendered heroes, then replace the "oldest". Or, in other words: 1. Check left slot > If Default hero, replace (> End) 2. Else check right slot > If Default, replace hero in right slot (> End) 3. Else check if both heroes have Retreated > If yes, replace the oldest (> End) 4. Else check if both heroes have Surrendered > If yes, replace the oldest (> End) 5. Else replace the one who Retreated > End __or split from step 3 into: 3. Else check if left slot = Retreated 3A. If Yes > Check if right slot = Retreated > Yes = replace oldest / No = replace left slot 3B. If No > Check if right slot = Retreated > Yes = replace right slot / No = replace oldest

Revision	2013-08-21 15:39 by Zamolxis
Description	H3 was making use of both slots, giving player the chance to keep 2 of the best heroes recently retreated or surrendered. I'm not very sure about the exact pattern and I didn't find info on this in Strategija. I played a bit with the VCMI_Tests map in WoG, retreating / surrendering each of the 8 heroes in different orders, and noticed the following: - first retreated/surrendered hero went into the left Tavern slot - from the 2nd onward, as long as I kept retreating only, they all went to the right slot (leaving the 1st retreated/surrendered hero there) - this went on until I surrendered with a hero, which went also the right slot; but the next retreated/surrendered hero then went to the left slot... So H3 seems to prioritize surrendered heroes, to keep them there as long as possible; but if we have 2 surrendered heroes, the one who surrendered first (pending there unhired the longest) will be lost & replaced by the next hero retreating/surrendering. H3 does not look at hero/army strengths though: I had a retreating hero override the first surrendered hero, even though it was stronger (level, artifacts, army) than the second surrendered hero. This was a bit of a bummer, but the odds of having 2 surrendered heroes, and no chance to hire the best of them until you have to retreat/surrender another, are pretty small, so I guess we shouldn't bother to further tweak the H3 logic on that. My assumption of the OH3 pattern is the following: 1. Look, from left to right, for the "most vulnerable" hero to be replaced. In order, that would be the Default (randomly generated weekly) hero, considered weaker than a Retreated hero, which is weaker than a Surrendered hero. i.e.: so if a Default hero is found in the left slot, the algorithm stops here as that's the one replaced. 2. If both slots have retreated heroes, or both have surrendered heroes, then replace the "oldest". Or, in other words: 1. Check left slot > If Default hero, replace (> End) 2. Else check right slot > If Default, replace hero in right slot (> End) 3. Else check if both heroes have Retreated > If yes, replace the oldest (> End) 4. Else check if both heroes have Surrendered > If yes, replace the oldest (> End) 5. Else replace the one who Retreated > End __or split from step 3 into: 3. Else check if left slot = Retreated 3A. If Yes > Check if right slot = Retreated > Yes = replace oldest / No = replace left slot 3B. If No > Check if right slot = Retreated > Yes = replace right slot / No = replace oldest

Revision	2013-08-21 15:33 by Zamolxis
Description	H3 was making use of both slots, giving player the chance to keep 2 of the best heroes recently retreated or surrendered. I'm not sure what the exact pattern and I didn't find info on this in Strategija. I played a bit with the VCMI_Tests map in WoG, retreating / surrendering each of the 8 heroes in different orders, and noticed the following: - first retreated/surrendered hero went into the left Tavern slot - from the 2nd onward, as long as I kept retreating only, they all went to the right slot (leaving the 1st retreated/surrendered hero there) - this went on until I surrendered with a hero, which went also the right slot; but the next retreated/surrendered hero then went to the left slot... So H3 seems to prioritize surrendered heroes, to keep them there as long as possible; but if we have 2 surrendered heroes, the one who surrendered first (pending there unhired the longest) will be lost & replaced by the next hero retreating/surrendering. H3 does not look at hero/army strengths though: I had a retreating hero override the first surrendered hero, even though it was stronger (level, artifacts, army) than the second surrendered hero. This was a bit of a bummer, but the odds of having 2 surrendered heroes, and no chance to hire the best of them until you have to retreat/surrender another, are pretty small, so I guess we shouldn't bother to further tweak the H3 logic on that. My assumption of the OH3 pattern is the following: 1. Look, from left to right, for the "most vulnerable" hero to be replaced. In order, that would be the Default (randomly generated weekly) hero, considered weaker than a Retreated hero, which is weaker than a Surrendered hero. i.e.: so if a Default hero is found in the left slot, the algorithm stops here as that's the one replaced. 2. If both slots have retreated heroes, or both have surrendered heroes, then replace the "oldest". Or, in other words: 1. Check left slot > If Default hero, replace (> End) 2. Else check right slot > If Default, replace hero in right slot (> End) 3. Else check if both heroes have Retreated > If yes, replace the oldest (> End) 4. Else check if both heroes have Surrendered > If yes, replace the oldest (> End) 5. Else replace the one who Retreated > End or split at step 3: 3. Check if left slot = Retreated 3A. If Yes > Check if right slot = Retreated > Yes = replace oldest / No = replace left slot 3B. If No > Check if right slot = Retreated > Yes = replace right slot / No = replace oldest

Revision	2013-08-21 15:19 by Zamolxis
Description	H3 was making use of both slots, giving player the chance to keep 2 of the best heroes recently retreated or surrendered. I'm not sure what the exact pattern and I didn't find info on this in Strategija. I played a bit with the VCMI_Tests map in WoG, retreating / surrendering each of the 8 heroes in different orders, and noticed the following: - first retreated/surrendered hero went into the left Tavern slot - from the 2nd onward, as long as I kept retreating only, they all went to the right slot (leaving the 1st retreated/surrendered hero there) - this went on until I surrendered with a hero, which went also the right slot; but the next retreated/surrendered hero then went to the left slot... So H3 seems to prioritize surrendered heroes, to keep them there as long as possible; but if we have 2 surrendered heroes, the one who surrendered first (pending there unhired the longest) will be lost & replaced by the next hero retreating/surrendering. H3 does not look at hero/army strengths though: I had a retreating hero override the first surrendered hero, even though it was stronger (level, artifacts, army) than the second surrendered hero. This was a bit of a bummer, but the odds of having 2 surrendered heroes, and no chance to hire the best of them until you have to retreat/surrender another, are pretty small, so I guess we shouldn't bother to further tweak the H3 logic on that. My assumption of the OH3 pattern is the following: 1. Look, from left to right, for the "most vulnerable" hero to be replaced. In order, that would be the Default (randomly generated weekly) hero, considered weaker than a Retreated hero, which is weaker than a Surrendered hero. i.e.: so if a Default hero is found in the left slot, the algorithm stops here as that's the one replaced. 2. If both slots have retreated heroes, or both have surrendered heroes, then replace the "oldest". Or, in other words: 1. Check left slot > If Default hero, replace (> End) 2. Else check right slot > If Default, replace hero in right slot (> End) 3. Else check if both heroes have the same Retreated/Surrendered property > If yes, replace the oldest (> End) 4. Else replace the Retreated > End

Site | Forums | Wiki | Slack | GitHub