Folks,
I've asked Julian to stop by this topic and take a look at any issues we've found or features we'd like added. To make it easier on him, let's try to summarize them in this thread. I'll go first:
* BUG? - the map list shows user-submitted maps, even if they're not approved yet - I'd consider this a feature rather than a bug, if there were an XML field saying what the status of the map was
TAS no longer shows unapproved maps. In addition, two new fields are provided:
- tournament_only - 1 if a map is reserved for only tournament matches (no maps (not even The Cage) are marked this way right now)
- random_pool - 1 if this map is part of the random pool
* DOC BUG: The value ranges listed in the TAS documentation for playerN_force_points and playerN_fpmax appear to be incorrect. You can set fpmax to 6 and force_points to 1. Both of these are desirable - it's just that the documentation says you can't do it.
Julian has fixed the documentation.
* DOC BUG: The documentation for starting a game says that the map should be specified by a field named "Map" (the m is capitalized). This (or apparently any other capital letter in a field name) results in a server error. Lower-case works fine, so it's just the documentation that needs to be touched up.
* REQUEST: In the map list, in addition to showing whether a map is approved or not, it'd be great if a field existed to specify which pool(s) (e.g. league games, big maps, etc.) the map was in.
We have 'tournament_only' and 'random_pool' flags. Julian says that small/medium/large is based on the product of x_size and y_size, but I don't know the cutoffs yet.
* REQUEST: It'd be nice if TAS could be used to start eague games. Obviously a player wouldn't have to accept a league game, but the option would be useful.
Julian doesn't want to do this right now. I'll try again in a while, but this was more of a forward-looking request, so unless somebody else needs it sooner, I'll back-burner it for now.
- FW
I've asked Julian to stop by this topic and take a look at any issues we've found or features we'd like added. To make it easier on him, let's try to summarize them in this thread. I'll go first:
* BUG? - the map list shows user-submitted maps, even if they're not approved yet - I'd consider this a feature rather than a bug, if there were an XML field saying what the status of the map was
TAS no longer shows unapproved maps. In addition, two new fields are provided:
- tournament_only - 1 if a map is reserved for only tournament matches (no maps (not even The Cage) are marked this way right now)
- random_pool - 1 if this map is part of the random pool
* DOC BUG: The value ranges listed in the TAS documentation for playerN_force_points and playerN_fpmax appear to be incorrect. You can set fpmax to 6 and force_points to 1. Both of these are desirable - it's just that the documentation says you can't do it.
Julian has fixed the documentation.
* DOC BUG: The documentation for starting a game says that the map should be specified by a field named "Map" (the m is capitalized). This (or apparently any other capital letter in a field name) results in a server error. Lower-case works fine, so it's just the documentation that needs to be touched up.
* REQUEST: In the map list, in addition to showing whether a map is approved or not, it'd be great if a field existed to specify which pool(s) (e.g. league games, big maps, etc.) the map was in.
We have 'tournament_only' and 'random_pool' flags. Julian says that small/medium/large is based on the product of x_size and y_size, but I don't know the cutoffs yet.
* REQUEST: It'd be nice if TAS could be used to start eague games. Obviously a player wouldn't have to accept a league game, but the option would be useful.
Julian doesn't want to do this right now. I'll try again in a while, but this was more of a forward-looking request, so unless somebody else needs it sooner, I'll back-burner it for now.
- FW
