-
Notifications
You must be signed in to change notification settings - Fork 0
Blocks & Tags
Blocks are, of course blocks. MCS finds these so called blocks based on a "tagging" system, usually denoted as such:
<type>[side][group]<+/->
- A type is a variety of joint (or block), such as a: hip, knee, etc.
- A side is left or right, abbreviated as L or R.
- A group is a number defining a leg group, 1 by default if left empty.
- A +/- provides a way to invert joints, useful for hinges or rotors placed untraditionally.
-
NOTE: This is required! It's also used as a "distinguisher" between other block names/tags
-
Legs are handled by a "grouping" system, where a group has both left and right legs.
For example, group 1 could be referenced as such:
-
HR1+andHL1+would be the right and left hip of group 1 respectively
Each alternating group has an offset, so 1 and 3 have the same animation offset, and 2 and 4 have the same animation offset.
Each leg group has it's own configuration that includes leg type, offsets, and etc; you can access these configurations through any block within the leg group in the Custom Data.
NOTE: For configuration changes to take effect, you must run the reload command or have setup mode active.
π - Rotor or Hinge π - Rotor + Gyroscope or standalone Gyroscope πͺ - Gyroscope π - Thruster β° - Timerblock π§² - Magnetic plate / Landing gear π· - Camera πͺ - Piston
- π
hip - π
knee - π
foot - π
quad- For 4 pieced mechs such as spiders or digitigrade
- π
strafe - π
turn
- π
ap(arm pitch, mouse up/down) - π
ay(arm yaw, mouse left/right)
- π
thruster - π
vy(vtol yaw) - π
vp(vtol pitch) - π
vr(vtol roll)
- π
gy(yaw / azimuth) - π
gp(pitch / elevation) - π
gr(roll) - πͺ
gg(3 axis)
- β°
tb:<event>:[specific]
For timer blocks, there is events you can listen for, and are all detailed here.
- π
tt(torso twist) - π·
camera - πͺ
hydraulic (pistons) - π§²
magnet