Struct game::Args

pub(crate) struct Args {

    pub(crate) flags: Flags,
    pub(crate) start_with_edits: Option<String>,
    pub(crate) cam: Option<String>,
    pub(crate) start_time: Option<Duration>,
    pub(crate) diff_map: Option<String>,
    pub(crate) dump_raw_events: bool,
    pub(crate) scale_factor: Option<f64>,
    pub(crate) dev: bool,
    pub(crate) color_scheme: Option<ColorSchemeChoice>,
    pub(crate) minimal_controls: bool,
    pub(crate) prebake: bool,
    pub(crate) tutorial_intro: bool,
    pub(crate) challenges: bool,
    pub(crate) sandbox: bool,
    pub(crate) proposals: bool,
    pub(crate) ungap: bool,
    pub(crate) devtools: bool,
    pub(crate) load_kml: Option<String>,
    pub(crate) challenge: Option<String>,
    pub(crate) tutorial: Option<usize>,
    pub(crate) actdev: Option<String>,
    pub(crate) actdev_scenario: Option<String>,
}

Fields

flags: Flags

start_with_edits: Option<String>

Start with these map edits loaded. This should be the name of edits, not a full path.

cam: Option<String>

Initially position the camera here. The format is an OSM-style zoom/lat/lon string (https://wiki.openstreetmap.org/wiki/Browsing#Other_URL_tricks).

start_time: Option<Duration>

Start the simulation at this time

diff_map: Option<String>

Load the map at this path as a secondary debug map to compare to the main one

dump_raw_events: bool

Print raw widgetry events to the console for debugging

scale_factor: Option<f64>

Override the monitor’s auto-detected scale factor

dev: bool

Dev mode exposes experimental tools useful for debugging, but that’d likely confuse most players.

color_scheme: Option<ColorSchemeChoice>

The color scheme for map elements, agents, and the UI.

minimal_controls: bool

When making a screen recording, enable this option to hide some UI elements

prebake: bool

Run a configured set of simulations and record prebaked data.

tutorial_intro: bool

Start at the tutorial intro screen

challenges: bool

Start by listing gameplay challenges

sandbox: bool

Start in the simulation sandbox mode

proposals: bool

Start by showing community proposals

ungap: bool

Launch Ungap the Map, a bike network planning tool

devtools: bool

Start by listing internal developer tools

load_kml: Option<String>

Start by showing this KMl file in a debug viewer

challenge: Option<String>

Start playing a particular challenge

tutorial: Option<usize>

Start on a particular tutorial stage

actdev: Option<String>

Start in ActDev mode for a particular site name.

actdev_scenario: Option<String>

Start by showing an ActDev scenario. Either “base” or “go_active”.

Trait Implementations

impl StructOpt for Args

fn clap<'a, 'b>() -> App<'a, 'b>

Returns clap::App corresponding to the struct.

fn from_clap(matches: &ArgMatches<'_>) -> Self

Builds the struct from clap::ArgMatches. It’s guaranteed to succeed if matches originates from an App generated by [StructOpt::clap] called on the same type, otherwise it must panic.

fn from_args() -> Self

Builds the struct from the command line arguments (std::env::args_os). Calls clap::Error::exit on failure, printing the error message and aborting the program.

fn from_args_safe() -> Result<Self, Error>

Builds the struct from the command line arguments (std::env::args_os). Unlike [StructOpt::from_args], returns clap::Error on failure instead of aborting the program, so calling .exit is up to you.

fn from_iter<I>(iter: I) -> Self where
    I: IntoIterator,
    <I as IntoIterator>::Item: Into<OsString>,
    <I as IntoIterator>::Item: Clone, 

Gets the struct from any iterator such as a Vec of your making. Print the error message and quit the program in case of failure.

fn from_iter_safe<I>(iter: I) -> Result<Self, Error> where
    I: IntoIterator,
    <I as IntoIterator>::Item: Into<OsString>,
    <I as IntoIterator>::Item: Clone, 

Gets the struct from any iterator such as a Vec of your making.