When multiple unit types are selected they are displayed
in the following priority order: nukes, land units, ships, planes.
To highlight sectors you own, specify the 'h' flag.
+With the 't' flag, the command shows your true bmap rather than your
+working bmap.
+.s1
+.L "Working and true bmap"
.s1
You actually have two bmaps. One which is created by the server; this
one is called your 'true' bmap. You can view your true bmap at any
-time using the
-.SY "bmap <SECTS|SHIP> true"
-command. However, usually when you view your bmap, you are looking at
+time using the 't' bmap flag.
+However, usually when you view your bmap, you are looking at
your 'working' bmap. The only difference between your working bmap
and your true bmap is that your working bmap also contains
designations put on there by you using the 'bdes' command, and by your
When multiple unit types are selected they are displayed
in the following priority order: nukes, land units, ships, planes.
To highlight sectors you own, specify the 'h' flag.
+With the 't' flag, the command shows your true bmap rather than your
+working bmap.
+.s1
+.L "Working and true bmap"
.s1
You actually have two bmaps. One which is created by the server; this
one is called your 'true' bmap. You can view your true bmap at any
-time using the
-.SY "lbmap <SECTS|LAND UNIT> true"
-command. However, usually when you view your bmap, you are looking at
+time using the 't' bmap flag.
+However, usually when you view your bmap, you are looking at
your 'working' bmap. The only difference between your working bmap
and your true bmap is that your working bmap also contains
designations put on there by you using the 'bdes' command, and by your
When multiple unit types are selected they are displayed
in the following priority order: nukes, land units, ships, planes.
To highlight sectors you own, specify the 'h' flag.
+With the 't' flag, the command shows your true bmap rather than your
+working bmap.
+.s1
+.L "Working and true bmap"
.s1
You actually have two bmaps. One which is created by the server; this
one is called your 'true' bmap. You can view your true bmap at any
-time using the
-.SY "nbmap <SECTS|NUKE> true"
-command. However, usually when you view your bmap, you are looking at
+time using the 't' bmap flag.
+However, usually when you view your bmap, you are looking at
your 'working' bmap. The only difference between your working bmap
and your true bmap is that your working bmap also contains
designations put on there by you using the 'bdes' command, and by your
When multiple unit types are selected they are displayed
in the following priority order: nukes, land units, ships, planes.
To highlight sectors you own, specify the 'h' flag.
+With the 't' flag, the command shows your true bmap rather than your
+working bmap.
+.s1
+.L "Working and true bmap"
.s1
You actually have two bmaps. One which is created by the server; this
one is called your 'true' bmap. You can view your true bmap at any
-time using the
-.SY "pbmap <SECTS|PLANE> true"
-command. However, usually when you view your bmap, you are looking at
+time using the 't' bmap flag.
+However, usually when you view your bmap, you are looking at
your 'working' bmap. The only difference between your working bmap
and your true bmap is that your working bmap also contains
designations put on there by you using the 'bdes' command, and by your
When multiple unit types are selected they are displayed
in the following priority order: nukes, land units, ships, planes.
To highlight sectors you own, specify the 'h' flag.
+With the 't' flag, the command shows your true bmap rather than your
+working bmap.
+.s1
+.L "Working and true bmap"
.s1
You actually have two bmaps. One which is created by the server; this
one is called your 'true' bmap. You can view your true bmap at any
-time using the
-.SY "sbmap <SECTS|SHIP> true"
-command. However, usually when you view your bmap, you are looking at
+time using the 't' bmap flag.
+However, usually when you view your bmap, you are looking at
your 'working' bmap. The only difference between your working bmap
and your true bmap is that your working bmap also contains
designations put on there by you using the 'bdes' command, and by your
.s1
Note that the sharebmap command only changes your 'working' bmap and
so you can delete sharebmap information from your bmap by typing:
-.EX "bmap revert"
+.EX "bmap <SECTS> revert"
See 'info bmap' for more details.
.s1
.SA "bdes, bmap, Communication, Maps"
#include "file.h"
#include "land.h"
#include "map.h"
+#include "match.h"
#include "misc.h"
#include "nat.h"
#include "nsc.h"
return draw_map(origin, map_flags, &ns);
}
+static void
+warn_deprecated_arg(char *what, char *arg, char *use)
+{
+ pr("%s '%s' is deprecated and will go away in a future release.\n"
+ "Use %s instead.\n",
+ what, arg, use);
+}
+
static int
parse_map_flags(int bmap, char *str)
{
int map_flags;
char *p;
+ int tflags = 0;
+ char *tp = NULL;
switch (bmap) {
default: CANT_REACH();
if (!str)
return map_flags;
+ /* special case "revert" */
+ if (bmap == 'b' && mineq(str, "revert") != ME_MISMATCH)
+ return MAP_BMAP_REVERT;
+
for (p = str; *p; p++) {
switch (*p) {
case 's':
case 't':
if (bmap != 'b')
goto bad_flag;
- return map_flags | MAP_ALT;
+ map_flags |= MAP_ALT;
+ /*
+ * Flags following 't' used to be ignored. That breaks
+ * perfectly sensible "ts". Try to continue, but save
+ * state for when a bad flag is found.
+ */
+ if (!tflags) {
+ tflags = map_flags;
+ tp = p;
+ }
+ break;
case 'r':
- if (bmap != 'b')
+ if (bmap != 'b' || tflags)
goto bad_flag;
+ warn_deprecated_arg("Map flag", "r", "argument 'revert'");
return MAP_BMAP_REVERT;
default:
bad_flag:
+ if (tflags) {
+ /* ignore bad flags following 't' */
+ warn_deprecated_arg("Argument", tp, "map flag 't'");
+ return tflags;
+ }
pr("Bad flag %c!\n", *p);
return -1;
}