IntegratedScripting guide for All the Mods 10 2.12

IntegratedScripting is included in this pack at version 1.0.10, built for Minecraft 1.21.1 on NeoForge. If you see it in your mod list and wonder what it's doing there, this page tells you what we can confirm about it.^[1]

It isn't a new addition. The pack has shipped it since version 0.49 or earlier, so it has been part of the pack for a long time.^[1]

Unverified We don't have a guidebook, platform description or quest data for this mod, so what it does in detail, who it's best suited to, and where it fits in the pack's progression are unconfirmed. We also have nothing confirming a place on the ATM Star path, so don't assume you need it for that route. Check back once more details are documented.

Same as in the All the Mods 10 8.1 guide

Integrated Scripting lets you write scripts for handling complex operations in Integrated Dynamics. Getting going takes three pieces: the Scripting Terminal, the Scripting Disk and the Scripting Drive. The disk stores your scripts, the drive serves them to your network, and the terminal is where you edit them. Here's the order I'd make them in.^[2]

First: Mendesite

Everything starts with Mendesite. The mod describes it as a basic resource, and the disk and terminal recipes below both build on it, so get some before anything else.^[2][3]

Second: the Scripting Disk

Next, make a Scripting Disk. This is what stores your scripting data, so it's the heart of the setup.^[2]

8× Scripting DiskMod recipe

Crafting Shaped

Crafting Shaped

Empty slot	Variable Card	Empty slot
Variable Card	Mendesite	Variable Card
Empty slot	Variable Card	Empty slot

Recipe id: integratedscripting:crafting/scripting_disk

Third: the Scripting Drive

The Scripting Drive exposes your Scripting Disks to the network. That's how you load scripts into your network, and it needs a disk to hold them.^[2]

Scripting DriveMod recipe

Crafting Shaped

Crafting Shaped

Empty slot	Scripting Disk	Empty slot
Scripting Disk	Variable Store	Scripting Disk
Empty slot	Jukebox	Empty slot

Recipe id: integratedscripting:crafting/scripting_drive

Last: the Scripting Terminal

Finally, craft the Part Terminal Scripting. This is how you get to the Scripting Terminal, where you write and edit your scripts.^[2][3]

Part Terminal ScriptingMod recipe

Crafting Shaped

Crafting Shaped

any redstone dust	Mendesite	any redstone dust
Output Variable Transformer	Part Display Panel	Input Variable Transformer
any redstone dust	Empty slot	any redstone dust

Recipe id: integratedscripting:crafting/part_terminal_scripting

What to do once it's built

1. Open the Scripting Terminal GUI.^[2]
2. Create a script and bind it to a Variable Card.^[2]
3. Show the scripted value in a Display Panel to check that it works.^[2]

If you can reach the files your game runs on, you can also edit scripts in an external editor. They live in the world/integratedscripting/ directory, with one folder per Scripting Disk. Changes you save outside the game are picked up automatically, even while the game is running.^[2]

IntegratedScripting has no machines with recipes, fluids or item throughput of its own. It is an add-on for Integrated Dynamics that lets you write JavaScript for complex logic instead of building long chains of variable cards. Everything works through three pieces that plug into your Integrated Dynamics network.^[4]

The three building blocks

Editing, storing and serving scripts takes a Scripting Terminal, a Scripting Disk and a Scripting Drive. Each one has a different job.^[4]

• Scripting Disk: stores the raw script contents but can't do anything on its own. It has no storage size limit, but the mod recommends splitting scripts across several disks to keep things manageable.^[4]
• Scripting Drive: a block connected to your network that accepts a single disk and exposes that disk's scripts to the network.^[4]
• Part Terminal Scripting: a part that must be connected to the same network. It lets you view, manage and edit every script exposed by the Scripting Drives on that network.^[4][5]

8× Scripting DiskMod recipe

Crafting Shaped

Crafting Shaped

Empty slot	Variable Card	Empty slot
Variable Card	Mendesite	Variable Card
Empty slot	Variable Card	Empty slot

Recipe id: integratedscripting:crafting/scripting_disk

Scripting DriveMod recipe

Crafting Shaped

Crafting Shaped

Empty slot	Scripting Disk	Empty slot
Scripting Disk	Variable Store	Scripting Disk
Empty slot	Jukebox	Empty slot

Recipe id: integratedscripting:crafting/scripting_drive

Part Terminal ScriptingMod recipe

Crafting Shaped

Crafting Shaped

any redstone dust	Mendesite	any redstone dust
Output Variable Transformer	Part Display Panel	Input Variable Transformer
any redstone dust	Empty slot	any redstone dust

Recipe id: integratedscripting:crafting/part_terminal_scripting

All three need Mendesite, which the mod describes as the basic resource for scripting. You make it in a Drying Basin.^[4][5]

Disk identifiers and moving disks

When a disk is first inserted into a drive, it gets a unique numerical identifier. The terminal uses this identifier to edit the disk's scripts, and it is also how script elements are linked to Variable Cards.^[4]

You can move a disk to a different network without losing its script data. Any Variable Card that refers to that disk's identifier will start throwing errors once it is no longer on the same network as the disk.^[4]

Binding scripts to Variable Cards

In the terminal, you bind a script member to a Variable Card by inserting the card into the slot on the right-hand side of the screen. You can then use that card elsewhere in the network. For example, you can show a variable member in a Display Panel, or use a function member as the operator in an item list filter.^[4]

Keeping state between calls

Integrated Dynamics is functional, so it normally can't remember state. JavaScript lets you work around that: a mutable variable declared outside your functions (for example with let) keeps its value across calls. You can use that to count calls or keep a running average.^[4]

Editing outside the game

If you can reach the file system the game runs on, you can edit scripts in any external editor. Script files live in the world/integratedscripting/ directory, with one folder per Scripting Disk, named by its identifier. Saving a file externally updates it in the game, and dependent variables update too, even while the game is running. If your editor supports it, changes made in the Scripting Terminal also show up in your editor.^[4]

The mod only supports pure JavaScript, not TypeScript. It does provide a typings file at world/integratedscripting/integratedscripting.d.ts that you can load into an external IDE. It is regenerated on every world restart, so don't edit it by hand.^[4]

Logging and debugging

Calling console.log() or console.error() in a script writes to files named after the script. For a script in myfile.js, output goes to myfile.js.stdout (and the matching .stderr file for errors). You can open these files in the Scripting Terminal or through external editing.^[4]

The pack caps these log files at 2,096 lines each through general.general.maxLogLines. Setting it to -1 removes the cap.^[6]

Limits and energy use in this pack

Scripts are sandboxed. general.general.graalStatementLimit is set to 16,384, which is the maximum number of statements one evaluation can run. It exists to stop infinite loops and very heavy programs, and -1 disables it, though that is not recommended.^[6]

The pack also keeps every guest-language permission switched off:^[6]

• general.general.graalAllowCreateProcess (creating processes)^[6]
• general.general.graalAllowCreateThread (creating threads)^[6]
• general.general.graalAllowEnvironment (environment variables)^[6]
• general.general.graalAllowExperimentalOptions (experimental options)^[6]
• general.general.graalAllowHostClassLoading (host class loading)^[6]
• general.general.graalAllowIo (IO)^[6]
• general.general.graalAllowNative (the native interface)^[6]

Both the drive and the terminal have a base energy usage setting. The pack sets general.general.scriptingDriveBaseConsumption to 2 and general.general.terminalScriptingBaseConsumption to 1. A third setting, general.general.terminalScriptingClientSyncTickInterval, is 20. It sets the minimum number of ticks between script-change packets sent from the client to the server.^[6]

Same as in the All the Mods 10 8.1 guide

IntegratedScripting has no formal tiers in this pack. What you get is a short crafting chain, and the drive builds directly on the disk. Here's the order I'd follow.^[3]

First: Scripting Disk

Everything starts with the Scripting Disk. The pack's recipe for it uses Mendesite, so Mendesite is the gate for this part of the mod.^[3]

8× Scripting DiskMod recipe

Crafting Shaped

Crafting Shaped

Empty slot	Variable Card	Empty slot
Variable Card	Mendesite	Variable Card
Empty slot	Variable Card	Empty slot

Recipe id: integratedscripting:crafting/scripting_disk

Next: Scripting Drive

After that comes the Scripting Drive. Its recipe uses a finished Scripting Disk, so you have to make the disk first.^[3]

Scripting DriveMod recipe

Crafting Shaped

Crafting Shaped

Empty slot	Scripting Disk	Empty slot
Scripting Disk	Variable Store	Scripting Disk
Empty slot	Jukebox	Empty slot

Recipe id: integratedscripting:crafting/scripting_drive

Last: Scripting Terminal

The Part Terminal Scripting is the other piece. Its recipe also uses Mendesite, but it does not use the disk or the drive, so you can craft it whenever you have the materials.^[3]

Part Terminal ScriptingMod recipe

Crafting Shaped

Crafting Shaped

any redstone dust	Mendesite	any redstone dust
Output Variable Transformer	Part Display Panel	Input Variable Transformer
any redstone dust	Empty slot	any redstone dust

Recipe id: integratedscripting:crafting/part_terminal_scripting

Unverified The sources here show no quests for this mod, so there is no quest-guided path to follow. Any further progression detail is not shown in the sources available for this section.

Same as in the All the Mods 10 8.1 guide

Everything this pack shows about how IntegratedScripting connects to other mods comes from recipes, and no quests involve it. The pattern is clear, though: IntegratedScripting is built on top of Integrated Dynamics. Its main items are crafted from Integrated Dynamics parts, and its Mendesite material is made in Integrated Dynamics machines.^[3]

Scripting Terminal part

The Part Terminal Scripting is crafted from Integrated Dynamics pieces such as the Part Display Panel and the input and output variable transformers (Input Variable Transformer and Output Variable Transformer). It also uses Mendesite and redstone dust from the common dusts tag.^[3]

Part Terminal ScriptingMod recipe

Crafting Shaped

Crafting Shaped

any redstone dust	Mendesite	any redstone dust
Output Variable Transformer	Part Display Panel	Input Variable Transformer
any redstone dust	Empty slot	any redstone dust

Recipe id: integratedscripting:crafting/part_terminal_scripting

Scripting Disk and Scripting Drive

The Scripting Disk is crafted from an Integrated Dynamics Variable Card and Mendesite. That ties your scripts directly to the variable system you already use in Integrated Dynamics.^[3]

8× Scripting DiskMod recipe

Crafting Shaped

Crafting Shaped

Empty slot	Variable Card	Empty slot
Variable Card	Mendesite	Variable Card
Empty slot	Variable Card	Empty slot

Recipe id: integratedscripting:crafting/scripting_disk

The Scripting Drive goes a step further. It builds on an Integrated Dynamics Variable Store, the Scripting Disk and a vanilla Jukebox.^[3]

Scripting DriveMod recipe

Crafting Shaped

Crafting Shaped

Empty slot	Scripting Disk	Empty slot
Scripting Disk	Variable Store	Scripting Disk
Empty slot	Jukebox	Empty slot

Recipe id: integratedscripting:crafting/scripting_drive

Mendesite and the Drying Basin

Mendesite is used in the recipes above, and the pack has Mendesite recipes that run in Integrated Dynamics machines: the Drying Basin and the Mechanical Drying Basin. They use Menril Resin and Andesite together with Mendesite.^[3]

IntegratedScripting has a single config file in this pack, and most of its options fall into three groups: how much sandboxing scripts get, how long a script can run, and how much energy the scripting blocks use. Here is how the pack sets each one.^[6]

Sandbox: what scripts can touch

Every option that gives guest-language scripts access to the outside world is switched off in this pack. That means scripts can't reach your files, processes or system, which is a good thing on a shared server.^[6]

• general.general.graalAllowCreateProcess is false, so scripts can't create new processes.^[6]
• general.general.graalAllowCreateThread is false, so scripts can't create new threads.^[6]
• general.general.graalAllowEnvironment is false, so scripts can't read environment variables.^[6]
• general.general.graalAllowExperimentalOptions is false, so experimental options can't be used in guest languages.^[6]
• general.general.graalAllowHostClassLoading is false, so host class loading is not allowed.^[6]
• general.general.graalAllowIo is false, so IO is not allowed.^[6]
• general.general.graalAllowNative is false, so the native interface can't be accessed.^[6]

Limits on scripts and logs

general.general.graalStatementLimit caps how many statements one evaluation can execute, which stops infinite loops and overly complex programs. The pack sets it to 16,384. The file notes that -1 disables the limit, but it also says that isn't recommended.^[6]

general.general.maxLogLines limits the number of lines in the stdout and stderr script log files. The pack sets it to 2,096, and -1 turns the limit off.^[6]

Energy use and syncing

• general.general.scriptingDriveBaseConsumption is the base energy usage of the scripting drive, set to 2 in this pack.^[6]
• general.general.terminalScriptingBaseConsumption is the base energy usage of the scripting terminal, set to 1 in this pack.^[6]
• general.general.terminalScriptingClientSyncTickInterval is the minimum number of ticks between script change packets sent from client to server. The pack sets it to 20.^[6]

There is also core.general.versionChecker, which enables the version checker and is true in this pack.^[6]

Unverified The sources only show the values this pack uses. They don't list the mod's own defaults, so I can't confirm which of these values the pack changed.