Config Directives

From BattletechMUX

Below is a list of config directives, things that determine many of the behaviors within the MUX. These are settable via @admin, or via netmux.conf. You may retrieve the values of many of these directives using config().

General MUX Directives

• allow_unloggedwho

Allow users to issue WHO from the login screen.

• room_parent

PENDING

• namechange_days

PENDING

• money_name_singular

PENDING

• money_name_plural

PENDING

• command_quota_increment

PENDING

• timeslice

PENDING

• fork_dump

PENDING

• paycheck

PENDING

• master_room

PENDING

• player_starting_room

PENDING

• player_starting_home

PENDING

• player_flags

PENDING

• exit_flags

PENDING

• room_flags

PENDING

• public_flags

PENDING

• find_money_chance

PENDING

• pemit_far_players

PENDING

• pemit_any_object

PENDING

• quotas

PENDING

• starting_quota

PENDING

• idle_interval

PENDING

• idle_timeout

PENDING

• dump_message

PENDING

• postdump_message

PENDING

• read_remote_desc

PENDING

• read_remote_name

PENDING

• queue_active_chunk

PENDING

• queue_idle_chunk

PENDING

• hostnames

PENDING

• player_match_own_commands

PENDING

• match_own_commands

PENDING

• see_owned_dark

PENDING

Battletech Directives

• btech_afterlife_dbref

Specifies the DBREF of the location to which players are moved upon death

• btech_critlevel

Defines the percentage of armor below which Through Armor Critical hitss are possible.

• btech_digbonus

PENDING

• btech_dig_only_fs

PENDING

• btech_dynspeed

PENDING

• btech_erange

PENDING

• btech_explode_ammo

Allows players to self-destruct via the explode ammo command. This is independent of btech_explode_reactor.

• btech_explode_reactor

Allow players to self-destruct via the explode reactor command. This is independent of btech_explode_ammo.

• btech_explode_stop

Allows players to abort a self-destruction sequence.

• btech_explode_time

Determines how long a self-destruct sequence takes. Ammo explosions take half the normal time.

• btech_fasacrit

PENDING

• btech_fasaturn

PENDING

• btech_failures

PENDING

• btech_hit_arcs

PENDING

• hudinfo_enabled

If set to 1, enables the hudinfo protocol.

Note: hundinfo_enabled requires compile directive to be enabled

• hudinfo_show_mapinfo

PENDING

• btech_ic

When not IC (0), players may not disembark into MechWarrior form or eject, or lose XP upon death.

• btech_limitedrepairs

PENDING

• btech_parts

When true, use and display part/weapon brand names.

• btech_phys_use_pskill

When true, use the associated piloting skill for determining physical attack BTH. If false, use a flat BTH of 4 and modify it based on conditions. XP for physicals is only enabled when this directive is true.

• btech_skidcliff

PENDING

• btech_slowdown

If set to 2, use the new speed reducer based on unit's current facing vs. desired heading. If set to 1, use a flat 2/3 speed reduction.

• btech_stackpole

When true, mechs that are destroyed by a triple engine crit explode, dealing splash damage to surrounding units.

• btech_tankfriendly

PENDING

• btech_tankshield

PENDING

• btech_usedmechstore

Specifies the DBREF of the object which RS Units are stored after they are destroyed.

• btech_vcrit

PENDING

XP Related Directives

• btech_oldxpsystem

PENDING

• btech_xp_bthmod

PENDING

• btech_xp_vrtmod

PENDING

• btech_xp_missilemod

PENDING

• btech_xp_ammomod

PENDING

• btech_defaultweapdam

PENDING

• btech_defaultweapbv

PENDING

• btech_xp_modifier

PENDING