Configuration · Client configuration

Configuration

Client configuration

Every option a player can change in their own game, where it lives and what it does.

Mo’ Bends keeps its client settings in one file, .minecraft/config/mobends.cfg, in Forge’s INI-like format. You rarely need to open it: everything in it can be changed in game, in two places.

  • The Mo’ Bends menu: press G in game, or use Mods → Mo’ Bends → Config from the title screen. The per-entity settings, including each mob’s options.
  • Forge’s config screen: the More Settings button in the Mo’ Bends menu’s Settings. The mod options below.

Both write to the same file, and saving in one keeps what you changed in the other.

Mod options

These are under the general category of mobends.cfg, and in Forge’s config screen (the More Settings button in the Mo’ Bends menu’s Settings, bottom right). Changing one in game refreshes Mo’ Bends right away.

Option In game Default What it does
showArrowTrails Show Arrow Trails true Arrows in flight leave a trail
showSwordTrail Show Sword Trails true Swinging a sword leaves a trail
itemUseClassifications Item use classifications (empty) How using an item is animated, for items Mo’ Bends doesn’t recognise (see below)
itemAttackClassifications Item attack classifications (empty) How attacking with an item is animated (see below)
keepArmorAsVanilla Keep armor as vanilla (empty) Armour items drawn with their vanilla model, unbent (see below)
keepEntityAsVanilla Keep entity as vanilla (empty) Entity types that are never animated (see below)
general {
    B:showArrowTrails=true
    B:showSwordTrail=true

    S:itemUseClassifications <
        mymod:magic_staff=bow
     >

    S:itemAttackClassifications <
        mymod:*_hammer=tool
        mymod:katana=sword
     >

    S:keepArmorAsVanilla <
        othermod:*
     >

    S:keepEntityAsVanilla <
        minecraft:pig
     >
}

Item patterns

The four list options match items or entities by their registry id, namespace:path, and both halves can use a * wildcard at either end:

Pattern Matches
minecraft:diamond_sword exactly that item
mymod:* everything from mymod
mymod:*_sword ids in mymod ending with _sword
mymod:steel_* ids in mymod starting with steel_
mymod:*crystal* ids in mymod containing crystal
*:*_hammer any mod’s ids ending with _hammer

Item classifications

Mo’ Bends decides how an item is used and swung from what it is. A modded item it doesn’t recognise can be animated as one it does with an item=classification entry. The classification is case-insensitive.

Option Classifications Animated as
itemUseClassifications food, bow, shield eating or drinking, drawing a bow, raising a shield
itemAttackClassifications fists, sword, tool punching, the sword combo, a tool swing

When several entries match an item, the last one in the list wins, so put broad patterns first and exceptions after them:

S:itemAttackClassifications <
    mymod:*=tool
    mymod:katana=sword
 >

An entry without =, or with an unknown classification, is reported in chat as an invalid configuration and skipped.

performSpinAttack was one of these before 2.0. It is now the player’s Perform Spin Attack option. If you had turned it off, it stays off.

Keeping things vanilla

  • keepArmorAsVanilla lists armour items (patterns as above) that are drawn with their vanilla model. Use it for modded armour with a custom model that breaks when bent. Armour made with GeckoLib bends with the animation too; listing it keeps it as GeckoLib draws it.
  • keepEntityAsVanilla lists entity types (minecraft:zombie, othermod:*) that are never animated. Players have no entity id, so this can’t turn players off; use the Animated switch for that.

Per-entity settings

Press G to open the Mo’ Bends menu and pick Settings, beside its title. Its settings are stored in their own categories of the same mobends.cfg.

Animated

Every animated entity (the player, the zombie, the spider, …) has an on/off switch. Turned off, that entity is drawn with the vanilla model and animation.

Animated {
    B:"mobends:player"=true
    B:"mobends:zombie"=true
    B:"mobends:spider"=false
}

Keys are the entity’s bender key (mobends:player). Settings saved by Mo’ Bends before 2.0, under the old keys, are carried over the first time they’re read.

Order

Resource packs and mods can give one entity several types: a different animation for a player named Dinnerbone, say. When more than one applies, Mo’ Bends picks the most specific one, and the menu shows an Order button next to the entity so you can choose yourself. Move types up and down like resource packs; the top one wins. Reset goes back to the automatic order.

TypeRanks {
    I:"mobends:player"=0
    I:"yourpack:dinnerbone_zombie_arms"=1
}

A higher rank wins. A type that isn’t listed has rank 0.

Extensions

An extension adds animation on top of an entity’s own (a wave, a dance) instead of replacing it, and several can apply at once. When an entity has more than one, the menu shows an Extensions button: the extension at the top of the list is drawn on top of the others.

ExtensionRanks {
    I:"mobends_wave:wave"=1
    I:"mobends_dance:cow"=0
}

Options

Some mobs have options: settings their animation offers. The player has Perform Spin Attack, which ends the sword combo with a spin attack (a whirl slash), never while riding. Resource packs and mods can add options of their own.

In the menu’s settings, a mob with options shows an Options button. It lists each option, where it comes from (the model, a type or an extension) and its default. A change applies at once; Reset puts every option back to its default.

Options {
    D:"mobends:bends/models/player.json#spinAttack"=0.0
}

Only options you changed are stored, keyed by <owner>#<name>. An option you never changed follows its default, even if a new version changes it.

Resource packs

Animation content (types, extensions, animators, clips and model definitions) comes from mods and resource packs, not from the config. Enable a resource pack with Mo’ Bends animation as any other, and press Refresh in the Mo’ Bends menu after editing one.

On a multiplayer server, the server decides what resource packs may do to animation. With the default policy, a pack’s animation is kept close to the regular one and its custom models are ignored. See Server configuration.

Other files

Mo’ Bends also keeps a few files in .minecraft/config/mobends/:

File What it is
assets/ Cosmetic textures and models downloaded from mobends.com
asset_manifest.json The versions of the downloaded assets, so they’re only fetched again when they change
env.json Optional, for development: points the mod at another backend

env.json is only read if it exists, and replaces the defaults key by key:

{ "apiUrl": "http://localhost:3000" }

apiUrl (default https://mobends.com) is where cosmetics, player settings and assets come from. Leave the file out to use the official site. Offline play is unaffected when the site can’t be reached.