Sharing

All bound controls and axes are saved to the machine file. This includes chained axes or axes referenced by custom axis initialization code.

This means machines with ACM binds can be shared on workshop.

When somebody opens your machine, all controller references will be resolved to the user's controller. Because of this, the user might end up with different axes. To avoid this, make sure your controller has proper mappings. You can correct it here.

When the user opens a machine, all used axes will be checked for their status. If there is an issue, the mod will automatically open the overview window and prompt you to fix the issues by clicking on the edit button. This happens e.g. if you have no device connected or missing libraries.

You can resolve all these issues by clicking the ✎ button.

Because of the complexity of the mod, pay attention to the following tips when designing your machine's controls:

• Use descriptive and simple names for your input axes, like shown above.
• If possible, try to minimize the number of used axes. Don't create duplicate axes for inverting controls, instead invert the block control interval.
• Keep in mind someone might have a different controller and will want to bind something to keys instead.
• If your creation relies heavily on complex chain or custom axes, use Lench Scripter Mod instead.