Tags
Creators
Details
Licensed MIT
Published 6 months ago
Updated 4 months ago
All versions
1.1.0
Release
ReSync 1.1.05 months ago 24
Compatibility
Minecraft: Java Edition
26.1.x
1.21.x
Platforms
Paper
Purpur
Changes
Added
- Added packet-based ReSync connections for Remotely and RemotelyMod, including plugin message bridging, chunked envelopes, session tracking, and frame sending.
- Added packet-based GUI and scoreboard subscriptions so Remotely can receive live ReSync UI state more reliably.
- Added the beta ReSync Extension API with extension registration, extension storage, option catalog providers, node definitions, extension data, and extension manager support.
- Added the ReQuest example extension as a working API example with quest profiles, quest state, commands, handlers, modules, and custom node definitions.
- Added player facet metadata/state tracking and player tracking services for richer live project context.
- Added option catalog and node registry packet handling so Remotely can load extension and built-in node data dynamically.
- Added custom content metadata and compatibility support for ReSync custom content projects.
- Added GUI item command actions.
- Added an improved Leap To Location node.
- Added built-in generator registration support through the ReSync world generation path.
Changed
- Restructured ReSync file and content management across flow storage, custom content storage, world generation storage, metadata, and packet handlers.
- Improved Flow runtime reliability through stronger mutations, execution context handling, type adaptation, JSON family behavior, and migrated node definitions.
- Improved custom content graph compatibility and listener behavior.
- Improved connection management around sessions, channel registration, chunk modules, world modules, player tracking, and ReSync server startup.
- Improved Flow registry and plugin loading so extensions can contribute nodes and option catalogs through the new API.
- Improved Remotely integration for GUI, scoreboard, player, node registry, option catalog, and custom content synchronization.
Fixed
- Fixed broken ReSync file storage paths for flows, custom content, and world generation projects.
- Fixed flow reliability issues in custom content, ability effects, entity actions, player actions, JSON handling, and migrated node catalogs.
- Fixed invisible player messages when multiple text formatting operations are used.
- Fixed double log prefixing.
- Fixed numeric logic comparisons so
0,"0", and0.0are handled consistently. - Fixed ReSync connection issues in the packet-based Remotely bridge.
- Fixed GUI and scoreboard subscription behavior over packet-based connections.
Optional dependencies
Any compatible version
Any compatible version
Any compatible version
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:VCNzymgL:vOaxHSr3"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:VCNzymgL:vOaxHSr3"
}

