Movementdef, Template

From Battletech Modding Wiki
Jump to: navigation, search

The movement Definitions are the movement Capability for each and every mech. The game uses this data rather than the information in the chassis data.

{
       "Description" : {
          "Id" : "movedef_atlas_AS7-D",
          "Name" : "MovementCapabilitiesDef for Atlas AS7-D",
          "Details" : "",
          "Icon" : "",
          "Cost" : 0,
          "Rarity" : 0,
          "Purchasable" : false
       },
       "MaxWalkDistance" : 105.0,
       "MaxSprintDistance" : 184.0,
       "WalkVelocity" : 20.0,
       "RunVelocity" : 28.0,
       "SprintVelocity" : 32.0,
       "LimpVelocity" : 8.0,
       "WalkAcceleration" : 12.0,
       "SprintAcceleration" : 18.0,
       "MaxRadialVelocity" : 60.0,
       "MaxRadialAcceleration" : 180.0,
       "MaxJumpVel" : 30.0,
       "MaxJumpAccel" : 15.0,
       "MaxJumpVerticalAccel" : 30.0
    } 
  • Description:{} object identifier for Description contains the standard set:
    • "Id" :- String used to identify this to the rest of the game eg "movedef_atlas_AS7-D",
    • "Name" :- String, friendly name for this file "MovementCapabilitiesDef for Atlas AS7-D",
    • "Details" : "", :- String, not used.
    • "Icon" : "", :- String, not used.
    • "Cost" : 0, :- Int, 0. Not used.
    • "Rarity" : 0, :- Int, 0 Not used.
    • "Purchasable" :- Bool, false not used.
  • "MaxWalkDistance" :-Float, maximum walk distance, based on "clear" terrain, Also appears according to hbs to be the max sprint (see below)
  • "MaxSprintDistance" :- Float should be maximum Sprint Distance however see below.
  • "WalkVelocity" :- Float, velocity for animation purposes ?
  • "RunVelocity" :- Float, velocity for animation purposes ?
  • "SprintVelocity" :- float :- velocity for animation purposes ?
  • "LimpVelocity" :- float :- velocity for animation purposes ?
  • "WalkAcceleration" :- float :- acceleration for animation purposes
  • "SprintAcceleration" :- float, :- acceleration for animation purposes
  • "MaxRadialVelocity" :- float :- acceleration for animation purposes
  • "MaxRadialAcceleration" :-float, :- acceleration for animation purposes ?
  • "MaxJumpVel" :-float, :- velocity for animation purposes
  • "MaxJumpAccel" :-float :- acceleration for animation purposes
  • "MaxJumpVerticalAccel" :-flaot  :- acceleration for animation purposes
All movement for mechs is defined in the movedef file associated with the chassis they run on, and the Panther's is movedef_panther_PNT-9R.
Inside there, you can find the max walk distance - which is technically max run distance, essentially "How far the mech can move when not sprinting or jumping.' At 165 meters, that's a run of 6 hexes (5.5, to be specific, because of how we've adjusted some of the movement to work). Sprint is 1.75 times that distance, so a faster base movement means a faster sprint.
So I'm pretty sure the panther is moving the appropriate distance. It may not always be 6 dots, because we path organically, not from dot to dot, but I think the Panther's movement is right.
Turns out the Panther IS in the wrong; looks like it got converted over with a strictly 30-meter dot spacing, which we don't use for other mechs. Its max walk should be 120, not 165, because each 'hex' increment is at 15, not 30 meters. So a 3/5 at 105 meters is correct, while a 4/6 should be 120, but defs not 165.
https://community.battletechgame.com/forums/threads/8134/comments/150768 https://community.battletechgame.com/forums/threads/8134/comments/150787

Wiki Quick Nav: File Formats | Other Tweaks and Adjustments | Tools and Scripts | Troubleshooting | Style Guide