Tags
Creators
Details
All versions
1.1.0+mc26.1-26.2
Release
Panorama Mod Recreated 1.1.0+mc26.1-26.22 months ago 482
Compatibility
Minecraft: Java Edition
26.2
26.1.x
Platform
Fabric
Supported environments
Client-side
Required content
Any compatible version
Changes
Changelog
All notable changes to Panorama Mod Recreated will be documented in this file.
1.1.0 - 2026-06-22
Added
- Added configurable keybinds in Minecraft's Controls menu:
F6opens the panorama naming prompt and starts screenshot capture after a name is entered.F7opens the dedicated Panorama Settings menu.
- Added a dedicated Panorama Settings menu, available through Mod Menu or the
F7keybind. - Added a
Panoramasbutton to the Panorama Settings menu. - Added a panorama management screen with preview tiles for saved panoramas.
- Added per-panorama actions:
- Export
- Rename
- Delete
- Added display text under panorama preview tiles so similar-looking captures are easier to tell apart.
- Added universal build outputs for:
- Minecraft
1.21through1.21.11 - Minecraft
26.1,26.1.1,26.1.2, and26.2
- Minecraft
Changed
- Panorama captures are now stored in
mods/.panoramainstead ofmods/panorama. - The panorama storage folder is marked hidden on Windows when created, opened, or loaded.
- Exported resource packs are now
.zipfiles. - Exported resource pack filenames now use the panorama name.
- Clicking a panorama preview now opens management options instead of immediately exporting.
- Universal wrapper mods are marked as Mod Menu library entries so only the main
Panorama Mod Recreatedentry appears by default. - Universal wrapper display names now stay as
Panorama Mod Recreated. - Bumped mod version to
1.1.0.
Fixed
- Fixed the capture keybind skipping the panorama naming prompt.
- Fixed the universal
26.xbuild coverage to include26.1,26.1.1,26.1.2, and26.2. - Fixed duplicate-looking Mod Menu entries caused by the universal wrapper showing alongside the real mod.
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:4RL7T78E:NLGK8tRh"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:4RL7T78E:NLGK8tRh"
}

