Tags
Creators
Details
0.5.22.alpha
Compatibility
Changes
This should fix the crash on dedicated servers.
(0.5.22.alpha)
[Added]
-
Added a dedicated side-safe packet routing registry to handle network communications on the client. This protects server environments from loading client-only rendering classes and prevents dedicated server startup crashes.
-
Added the Program Disk utility item, enabling players to clone entire flowchart layouts and variables between different Machine Inventory Managers.
-
Added an interactive overwrite confirmation screen that queries the player before pasting configurations onto a Manager that already contains layout nodes.
-
Added a shaped crafting recipe and creative tab registration for the Program Disk.
-
Added a block ownership and access control system for Machine Inventory Managers. When placed, blocks are registered to the placer as the owner.
-
Added an Access Settings button and permission modal to the Manager screen, enabling owners to toggle between Owner-only, Team-only (utilizing scoreboard teams), and Public access modes.
-
Added localization keys and red floating warning prompts shown to unauthorized players attempting to access private Managers.
-
Added a secondary-use override for server operators with level 2+ permissions, permitting administrative bypass of locked nodes.
[Changed]
-
Standardized all inventories list variables (Item, Fluid, Energy, Redstone, and Sign Updater) to resolve their block targets polymorphically.
-
Re-routed all clientbound network packet processing securely through the client-only bootstrapping phase.
-
Updated the Machine Inventory Manager block's interaction handler to support copying and pasting with the Program Disk.
-
Block interaction is now restricted according to the assigned access level.
-
Adjusted the vertical text coordinate offset of the sliding drawer label slightly to improve layout alignment.
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| sfmflow-0.5.22.alpha-sources.jar | Sources jar | 577.59 KiB |
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:LTva5BWN:QkVpD9mU"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:LTva5BWN:QkVpD9mU"
}

