Next: Map style.xml, Previous: Map rules.xml, Up: Reference

### 4.10 Map hints.xml

#### 4.10.1 background-color-auto

— Command-line option: `--background-color-auto=<value>`
— Environment variable: `LW6_BACKGROUND_COLOR_AUTO`
— XML key: `background-color-auto`

> Type: boolean

> Default value: true

> Defines wether hud colors will be set automatically from base and alternate colors. This is a time saver to keep map designers from requiring to redefined every single color in the game. You only need to set color-base-bg, color-base-fg, color-alternate-bg and color-alternate-fg. Then hud_color_frame_bg, hud_color_frame_fg, hud_color_text_bg and hud_color_text_fg will be automatically set.

#### 4.10.2 downsize-using-bench-value

— Command-line option: `--downsize-using-bench-value=<value>`
— Environment variable: `LW6_DOWNSIZE_USING_BENCH_VALUE`
— XML key: `downsize-using-bench-value`

> Type: boolean

> Default value: true

> If set, then the game will automatically downsize a map according to the 'bench-value' parameter. Downsizing means: a 1600x1200 maps becomes 200x150, for instance. Downsizing causes fighters to be bigger because map resolution is lower. This will avoid running the game on a too big map, with your computer not being able to handle it at the required speed.

#### 4.10.3 downsize-using-fighter-scale

— Command-line option: `--downsize-using-fighter-scale=<value>`
— Environment variable: `LW6_DOWNSIZE_USING_FIGHTER_SCALE`
— XML key: `downsize-using-fighter-scale`

> Type: boolean

> Default value: false

> If set, then the game will automatically downsize a map according to the 'fighter-scale' parameter. Downsizing means: a 1600x1200 maps becomes 200x150, for instance. Downsizing causes fighters to be bigger because map resolution is lower. This can be usefull if you don't want fighters to be too small.

#### 4.10.4 fighter-scale

— Command-line option: `--fighter-scale=<value>`
— Environment variable: `LW6_FIGHTER_SCALE`
— XML key: `fighter-scale`

> Type: float

> Default value: 1.0

> Defines how wide (in pixels) fighters must be. This parameter is very important and will largely condition the number of fighters on the map. It is used when loading the map. If it is, for instance, set to 1, there will be exactly a fighter per pixel on the screen. That is, if you play 640x480 on an empty map, the maximum fighters you could have is about 300000. The idea is that by changing the resolution, you also define the density of the map. In pratice, this is done in the hope that someone with a slow computer will pick up a low resolution and therefore play small levels. Conversely, someone with a brand new computer with powerfull CPU & GPU will use great resolutions and be happy with many fighters on the map. Still, changing the resolution after loading the map will not affet the number of fighters. Same for network games, the first player, who loads the map, defines its properties according to its own settings.

#### 4.10.5 guess-colors

— Command-line option: `--guess-colors=<value>`
— Environment variable: `LW6_GUESS_COLORS`
— XML key: `guess-colors`

> Type: boolean

> Default value: true

> Defines wether colors should be set automatically from texture colors. If set to true, then the program will try to pick up colors automatically from the texture, and will override the values of the color-base-bg, color-base-fg, color-alternate-bg and color-alternate-fg parameters. How these colors are picked up can't be garanteed, so if the map does not have strong contrast or if there can be any form of ambiguity, it's safe to set this to false and define one's own colors.

#### 4.10.6 guess-moves-per-sec

— Command-line option: `--guess-moves-per-sec=<value>`
— Environment variable: `LW6_GUESS_MOVES_PER_SEC`
— XML key: `guess-moves-per-sec`

> Type: boolean

> Default value: true

> If set, then loader will use 'time-to-cross-level' to guess the game speed parameters.

#### 4.10.7 hud-color-auto

— Command-line option: `--hud-color-auto=<value>`
— Environment variable: `LW6_HUD_COLOR_AUTO`
— XML key: `hud-color-auto`

> Type: boolean

> Default value: true

> Defines wether hud colors will be set automatically from base and alternate colors. This is a time saver to keep map designers from requiring to redefined every single color in the game. You only need to set color-base-bg, color-base-fg, color-alternate-bg and color-alternate-fg. Then hud_color_frame_bg, hud_color_frame_fg, hud_color_text_bg and hud_color_text_fg will be automatically set.

#### 4.10.8 max-map-height

— Command-line option: `--max-map-height=<value>`
— Environment variable: `LW6_MAX_MAP_HEIGHT`
— XML key: `max-map-height`

> Type: integer

> Default value: 3000

> Allows you to give a maximum map height. When designing a map you might wonder: this is dumb I'm conceiving this map I know its height, why should I limit it? Now think of the play who plays on a old slowish computer with a tiny screen. He might redefine this himself, and does not necessarly wishes to fire Gimp to rescale the map.

#### 4.10.9 max-map-surface

— Command-line option: `--max-map-surface=<value>`
— Environment variable: `LW6_MAX_MAP_SURFACE`
— XML key: `max-map-surface`

> Type: integer

> Default value: 3000000

> Allows you to give a maximum map surface. Map surface is simply (width * height). This parameter is just here to save you the hassle of defining both 'max-map-width' and 'max-map-height' in a consistent manner.

#### 4.10.10 max-map-width

— Command-line option: `--max-map-width=<value>`
— Environment variable: `LW6_MAX_MAP_WIDTH`
— XML key: `max-map-width`

> Type: integer

> Default value: 4000

> Allows you to give a maximum map width. When designing a map you might wonder: this is dumb I'm conceiving this map I know its width, why should I limit it? Now think of the play who plays on a old slowish computer with a tiny screen. He might redefine this himself, and does not necessarly wishes to fire Gimp to rescale the map.

#### 4.10.11 menu-color-auto

— Command-line option: `--menu-color-auto=<value>`
— Environment variable: `LW6_MENU_COLOR_AUTO`
— XML key: `menu-color-auto`

> Type: boolean

> Default value: true

> Defines wether menu colors will be set automatically from base and alternate colors. This is a time saver to keep map designers from requiring to redefined every single color in the game. You only need to set color-base-bg, color-base-fg, color-alternate-bg and color-alternate-fg. Then menu_color_default_bg, menu_color_default_fg, menu_color_selected_bg, menu_color_selected_fg, menu_color_disabled_bg and menu_color_disabled_fg will be automatically set.

#### 4.10.12 min-map-height

— Command-line option: `--min-map-height=<value>`
— Environment variable: `LW6_MIN_MAP_HEIGHT`
— XML key: `min-map-height`

> Type: integer

> Default value: 15

> Allows you to give a minimum map height. When designing a map you might wonder: this is dumb I'm conceiving this map I know its height, why should I limit it? Now think of the player who decided to play with highly-defined maps because he has a super calculator and a hudge screen. He might redefine this himself, and does not necessarly wishes to fire Gimp to rescale the map.

#### 4.10.13 min-map-surface

— Command-line option: `--min-map-surface=<value>`
— Environment variable: `LW6_MIN_MAP_SURFACE`
— XML key: `min-map-surface`

> Type: integer

> Default value: 1200

> Allows you to give a minimum map surface. Map surface is simply (width * height). This parameter is just here to save you the hassle of defining both 'min-map-width' and 'min-map-height' in a consistent manner.

#### 4.10.14 min-map-width

— Command-line option: `--min-map-width=<value>`
— Environment variable: `LW6_MIN_MAP_WIDTH`
— XML key: `min-map-width`

> Type: integer

> Default value: 20

> Allows you to give a minimum map width. When designing a map you might wonder: this is dumb I'm conceiving this map I know its width, why should I limit it? Now think of the player who decided to play with highly-defined maps because he has a super calculator and a hudge screen. He might redefine this himself, and does not necessarly wishes to fire Gimp to rescale the map.

#### 4.10.15 resample

— Command-line option: `--resample=<value>`
— Environment variable: `LW6_RESAMPLE`
— XML key: `resample`

> Type: boolean

> Default value: true

> If set to true, maps will always be resampled to a size which depends on your screen resolution, zoom factor, and the rest. If false, maps will be set at the exact resolution of map.png.

#### 4.10.16 speed

— Command-line option: `--speed=<value>`
— Environment variable: `LW6_SPEED`
— XML key: `speed`

> Type: float

> Default value: 1.0

> This parameter is the main parameter on which game speed depends. The map loader will garantee, by downscaling the map, that to cross the level (by crossing the level we mean, for instance, going from top-left corner to bottom-right corner in a straight line) a fighter will take a constant amount of time. Under the hood, the loader might of course rescale the map but it will also change game speed so that, at the end, fighters take a constant time to cross the level. This is, indeed, the most important thing, players do not care much if internally there are X or Y moves per second, the global game experience depends on how fast fighter movement looks on the screen. The default settings corresponds roughly to one second to cross the level. If you set this to 2.0, it will go twice faster.

#### 4.10.17 system-color-auto

— Command-line option: `--system-color-auto=<value>`
— Environment variable: `LW6_SYSTEM_COLOR_AUTO`
— XML key: `system-color-auto`

> Type: boolean

> Default value: true

> Defines wether system colors will be set automatically from base and alternate colors. This is a time saver to keep map designers from requiring to redefined every single color in the game. You only need to set color-base-bg, color-base-fg, color-alternate-bg and color-alternate-fg. Then system_color_bg and system_color_fg will be automatically set.

#### 4.10.18 upsize-using-bench-value

— Command-line option: `--upsize-using-bench-value=<value>`
— Environment variable: `LW6_UPSIZE_USING_BENCH_VALUE`
— XML key: `upsize-using-bench-value`

> Type: boolean

> Default value: false

> If set, then the game will automatically upsize a map according to the 'fighter-scale' parameter. Upsizing means: a 160x120 maps becomes 400x300, for instance. Upsizing causes fighters to be smaller because map resolution is higher. This will avoid useless pixelish 'jumbo fighters' look when your computer is powerfull enough to do better.

#### 4.10.19 upsize-using-fighter-scale

— Command-line option: `--upsize-using-fighter-scale=<value>`
— Environment variable: `LW6_UPSIZE_USING_FIGHTER_SCALE`
— XML key: `upsize-using-fighter-scale`

> Type: boolean

> Default value: true

> If set, then the game will automatically upsize a map according to the 'fighter-scale' parameter. Upsizing means: a 160x120 maps becomes 400x300, for instance. Upsizing causes fighters to be smaller because map resolution is higher. This can be usefull if you don't want fighters to be too big.

#### 4.10.20 view-color-auto

— Command-line option: `--view-color-auto=<value>`
— Environment variable: `LW6_VIEW_COLOR_AUTO`
— XML key: `view-color-auto`

> Type: boolean

> Default value: true

> Defines wether view colors will be set automatically from base and alternate colors. This is a time saver to keep map designers from requiring to redefined every single color in the game. You only need to set color-base-bg, color-base-fg, color-alternate-bg and color-alternate-fg. Then view_color_cursor_bg, view_color_cursor_fg, view_color_map_bg and view_color_map_fg will be automatically set.

#### 4.10.21 wall-grease

— Command-line option: `--wall-grease=<value>`
— Environment variable: `LW6_WALL_GREASE`
— XML key: `wall-grease`

> Type: integer

> Default value: 0 Min value: -5 Max value: 5

> This parameter allows you to make walls (aka map foreground) thicker, or thiner, when map is loaded. Indeed, when map are resampled, and especially when they are downscaled, some walls may disappear, or some passages may be blocked. The loader can't automatically figure out wether it's more important to keep an existing wall or to keep an open passage for fighters. This parameter helps doing so, if you set it to a low value, level will be less greasy, and many passages might open themselves. On the contrary, if grease is at a high level, then a thin line of almost isolated pixels might become a thick wall. There's no real garantee your wall or passage will always be present, but it's a same bet to assume on a 'tunnel-like' level one needs to set grease to a low value, and on a 'wide open' level with few walls one needs to set grease to a high value.