Gurken Khan Posted April 29 Share Posted April 29 The game just failed to create a map. I don't know why it says "stronghold", a previous game (I didn't play) was named that. Shouldn't Coast Range be able to handle three teams? logs290426.zip Link to comment Share on other sites More sharing options...
Stan` Posted April 30 Share Posted April 30 Usually it's because there is a stronghold placement type that's being set in the map options. But it might be persist match settings acting out again. CC @phosit Link to comment Share on other sites More sharing options...
Gurken Khan Posted April 30 Author Share Posted April 30 11 minutes ago, Stan` said: Usually it's because there is a stronghold placement type that's being set in the map options. I did not do such a thing. (Didn't know match settings were acting up.) Link to comment Share on other sites More sharing options...
Stan` Posted April 30 Share Posted April 30 Basically player placement option is the reason it would fail Link to comment Share on other sites More sharing options...
phosit Posted May 1 Share Posted May 1 I don't know of a remaining issue of persistent map settings. Also the name of a game should be causally unrelated to the placement. I know #8148 which is related especially this link. Link to comment Share on other sites More sharing options...
Gurken Khan Posted May 1 Author Share Posted May 1 18 minutes ago, phosit said: this link. Oh, "someone" had a similar experience... #8148 seems to me like a different case, as one deliberately sets up a specific match versus playing a random random random game. So, the above message is the intended behavior when player settings and rng result aren't compatible? Could the game be forced to comply with the settings so that an error won't be shown to the player? Link to comment Share on other sites More sharing options...
phosit Posted May 1 Share Posted May 1 Oh, so you choose random as placement - I understand now. I think it would be a hard to delay the random selection to the mapgen script. One would also have to change replay-summary: there it shouldn't be displayed as "random". The more complete solution is the one stated in the ticket. Link to comment Share on other sites More sharing options...
Gurken Khan Posted May 1 Author Share Posted May 1 10 minutes ago, phosit said: The more complete solution is the one stated in the ticket. I don't see it. Are you referring to this part? Quote When the condition is not met the Start Game! button should be disabled and a tooltip should explain why. I still don't think this is applicable with random random random games. The application doesn't ~know what map it will roll and thus doesn't know whether it will work with the selected options; so it couldn't disable the Start button at that point. Spoiler Link to comment Share on other sites More sharing options...
phosit Posted May 1 Share Posted May 1 To fix the issue, the map has to somehow expose the restrictions. Those restrictions could then also be read by the random selection algorithm. At least that's how I think of it. 1 Link to comment Share on other sites More sharing options...
Gurken Khan Posted May 1 Author Share Posted May 1 @phosit Can't say much about that, but if you think it's feasible... Coming back to the map: I believe I have played it, maybe when it was first included with vanilla, with my usual settings. Anyway, what's keeping it from just putting the players in a circle? Link to comment Share on other sites More sharing options...
phosit Posted May 2 Share Posted May 2 That's because it first chooses the placement, without knowing whether the map supports it. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now