Links
Tags
Creators
Details
Licensed LGPL-3.0-only
Published 4 months ago
Updated 3 months ago
All versions
personalspace-forge-1.20.1-0.3.0
Release
Personal Space Unofficial 0.3.04 months ago 33
Uploaded by
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client and server
Changes
Personal Space Unofficial 1.20.1 Forge 0.3.0
This update focuses on Personal Dimension stability, GTCEu / GregTech Odyssey compatibility, and safer dimension management.
Highlights
- Personal Dimensions now have improved GTCEu / GregTech Odyssey compatibility.
- Added support for deleting Personal Dimensions safely.
- Fixed server-side time handling for machines and blocks.
- Fixed weather/rain behavior inside Personal Dimensions.
- Added void-fall protection.
- Improved GTCEu fluid generation handling for Personal Dimensions.
- Reduced debug log spam.
New Features
- Added an option to delete Personal Dimensions.
- Added protection so players cannot delete dimensions owned by other players.
- Added void-fall death protection inside Personal Dimensions.
- Added GTCEu fluid regeneration support for Personal Dimensions.
- Added compatibility handling for GTO/GTCEu recipes and machines that require Overworld-like dimension checks.
Fixes
- Fixed Personal Dimension weather/rain issues.
- Fixed server-side time issues affecting blocks and machines.
- Fixed GTCEu/GTO Air Hatch compatibility.
- Fixed void fall handling.
- Fixed unsafe deletion behavior involving other players' Personal Dimensions.
- Fixed missing GTCEu fluid data cases in Personal Dimensions.
Changes
- Improved internal Personal Dimension time/weather handling.
- Removed debug console spam from time/weather compatibility code.
- Updated README/documentation for configuration menu changes.
Requirements
- Minecraft 1.20.1
- Forge 47.x
- Infiniverse
Optional Compatibility
- GTCEu
- GregTech Odyssey / GTOCore
- FTB Teams
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:Ko6Fwi37:VPyZF8qT"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Ko6Fwi37:VPyZF8qT"
}

