|
Notes |
|
|
(0001998)
|
|
Tow
|
|
2011-09-06 05:50
|
|
I just tried and it worked fine. Apparently not so general issue.
Which players and heroes should I take to reproduce issue? |
|
|
|
|
I just played attached map and added all 8 players in hotseat mode. Now, firts fight started successfully (Sir Mullich against Orange). However, orange was still controlled by AI.
Then, blue and green got their turns, but remaining players did not. However, now both players in combat were human-controlled.
Finally, I attacked green hero with Sir Mullich in 2nd turn and then game freezed, reporting unanswered query.
In the second trial I decided to leave Tan and he got his turn, but teal, purple and pink did not. Maybe these are players with IDs after dead players and just don't get their turns.
In general, it feels quite complex and/or random issue. |
|
|
|
|
If by "Then, blue and green" you mean "Tan, blue and green", then I think the behavior is as expected (except for the game freeze of course, but that can have multiple reasons, maybe even not related to hot seat).
Regardless of how many players you create when you start the Hotseat mode, you cannot get more than the Human players set for that map. In the map attached, only Red, Blue, Tan and Green are Human. So it's normal that Orange was AI controlled in battle, and that the last 4 teams did not get a Hotseat turn. This is how H3 worked, and while I agree it should have given us a soft warning at map start that only the "first X players" will be able to play, it didn't.
It may be an idea though to code it as enhancement in VCMI. And we could take it even further that just a warning, but even give the choice to play other colors which are not Human. For example a choice warning like: "The default map allows only 4 human players, while you requested 8 human players for Hotseat. Do you want to play the map with 4 Human players only, as the map maker designed it, or would you like to unlock the AI-only flags for the rest of the Human players?"
Now, about the freeze, I am unable to reproduce it either. Can you reproduce it a map start directly? If yes, can you reproduce it in the 0.86 public release, or only in a dev version. If you can't reproduce it at map start, maybe you can try to find a pattern of actions performed before that lead to it, or else force a crashdump, to see if that can help identifying the cause. |
|
|
|
(0002190)
|
|
Tow
|
|
2012-02-19 19:36
|
|
I'm closing this issue, it's old and never was actually reproducible.
The unanswered query issue Warmonger described may have been fixed (there were some changes around this code).
If similar issue reappears, please open a new report. |
|
VCMI_Tests_2011b.h3m (18,798) 2011-09-08 11:33