Links
Tags
Creators
Details
All versions
0.22.0
Release
Create: Pocket Sized 0.22.06 days ago 4,682
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Any compatible version
Any compatible version
Any compatible version
Any compatible version
Changes
Create: Pocket Sized Alpha v0.22.0 w/ Pym 0.4.0
REQUIREMENTS
- Pehkui 3.8.3 or newer is required.
- Pym 0.4.0 is bundled inside the Pocket jar. No separate download needed.
- Client and server must both be on 0.22.0.
COMMANDS
- /pocket sethandscale <scale> sets the held Creative Shrinkray or Personal Subspace Compressor scale, takes 0.0625 or 1/16
PYM
- Step-up finally follows the sublevel's block size
- All scales of players stand up and change pose properly under low ceilings on scaled sublevels
- Fixed near-plane clipping getting doubly scaled with Pehkui
- Physics Staff hold distance follows the larger scale between player &sublevel
- Block breaking particles on scaled crafts reworked, more to come on this.
MISC
- Compression Cannon & Personal Subspace Compressor use up their levitite blend internally first, and only then try to use durability
- Punchy compat
- Reset the player to the size saved relative to their bed upon death.
- a few more tiny fixes.
SAVE GAMES
- Back up your world before updating please.
- Resized sublevels keep their scale when you update.
KNOWN ISSUES
- Collision can still lag when a large entity stands on a much smaller sublevel
- Pressure plates and similar blocks on 1/32 crafts don't react to 1x players. This is as an attempt to fix the lag mentioned previously...
- Scaled Contraptions (native Create ones, like the Mechanical Bearing) have no collision.
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:KbwNRCY7:Wi98MbF9"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:KbwNRCY7:Wi98MbF9"
}

