Tags
Creators
Details
Licensed MIT
Published 3 months ago
Updated 3 days ago
All versions
neoforge-1.21.1-1.0.0-c6
Release
Create: Transit Tickets neoforge-1.21.1-1.0.0-c63 days ago 14
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
Create: Transit Tickets 1.0.0-c6 for NEOFORGE 1.21.1
Added
- Added support for Minecraft 1.21.1.
- Added support for NeoForge 21.1.
- Added compatibility with Create 6.0.8.
- Added support for Ponder 1.0.66 and Flywheel 1.0.5.
Changed
- Ported item registration, block registration, block entities, creative tabs, and recipe serializers to the NeoForge APIs.
- Migrated ticket and blueprint data to Minecraftโs new data-component system.
- Updated ticket blueprint and ticket gate configuration networking.
- Updated item tooltips and screens for Minecraft 1.21.1.
- Updated Ticket Gate interactions, wrench behavior, sounds, persistence, and rendering support.
- Updated deploying and pressing recipes for the Create 6.0 recipe API.
- Updated Ponder scenes for the latest registry APIs.
- Migrated recipe resources to the Minecraft 1.21.1 data-pack format.
- Updated mod metadata and resource-pack compatibility.
Fixed
- Fixed the Ticket Gate recipe incorrectly producing a Ticket Blueprint.
- Fixed custom recipe output fields for Minecraft 1.21.1.
- Fixed Ticket Blueprint data not being transferred through the ticket production process.
- Fixed ticket passage consumption and expiration data for the new item data system.
- Fixed client-to-server configuration packets.
- Fixed Ticket Gate block-entity data saving and synchronization.
- Fixed development builds failing because of outdated Gradle and dependency configuration.
Notes
- This release requires Minecraft 1.21.1, NeoForge 21.1.251 or newer, and Create 6.0.8.
- Forge 1.20.1 builds are not compatible with this release.
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:6BITJSVi:9XD67PSt"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:6BITJSVi:9XD67PSt"
}

