Tags
Creators
Details
Published 5 months ago
Updated yesterday
All versions
0.5.5fix2
Release
Starfield Pastoral 0.5.5fix23 months ago 1,544
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
Update Log (English)
Pierre Event, Schedule And Mail
- Added Pierre's original six-heart event with the supplied exterior and interior cameras, mapped actor routes, original dialogue pacing, source friendship requirements and the original
+70/-500choice consequences. - Extracted and registered the original
ragtimemusic used by the event instead of substituting another track. Pierre's three-heart Blueberry Tart letter and all new event and schedule text use the original localized source across all 12 supported languages. - Rebuilt Pierre's regular, Friday, rain and Green Rain schedules from the original schedule data while preserving the existing Desert Festival route and supplied festival coordinates.
Cutscene And Asset Reliability
- Cutscene actors using authored navigation now recognize closed wooden doors as valid route cells, open them while approaching and close them after passing. The presentation remains local to the player watching the private cutscene, so multiplayer players do not alter one another's doors.
- Corrected inclusive block-corner handling for cutscene trigger regions, allowing single-block and narrow doorway triggers to detect the player's actual block-centered position reliably.
- Renamed the mixed-case
textBox.pngGUI resource and its reference to a consistently lowercase path, preventing crashes on case-sensitive filesystems. - Extended the actor-map generation data for Pierre's event and schedule, and updated the public mod version to
0.5.5fix2.
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:i54Drdq8:goSQHNx6"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:i54Drdq8:goSQHNx6"
}

