Jump to content
View in the app

A better way to browse. Learn more.

Forge Forums

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

irtimaled

Members
  • Joined

  • Last visited

  1. Created issue on GitHub repo... https://github.com/MinecraftForge/MinecraftForge/issues/1747
  2. I've dug into the Forge source and it looks like the WorldSpecificSaveHandler is trying to load the fortress.dat file from ./saves/world/DIM-1/data rather than ./saves/world/data Since the file wouldn't be there (cos that's not where it's stored) it would be regenerated!
  3. Nether fortress bounding boxes in 1.8 vanilla and latest Forge for 1.8 are not the same - the structure data that forge is showing is different than in the fortress.dat file. In this particular example it's a fortress that was generated in 1.6.2, then the world was updated to 1.7.2 so the fortress.dat file contains the 1.7.x bounding boxes and don't line up with the blocks. In 1.8 Vanilla it shows the correct bounding boxes:- https://pbs.twimg.com/media/B_-ykjVVEAEX0W4.png[/img] However in Forge 11.14.1.1337 (and several earlier versions) the bounding boxes look like they were generated fresh in 1.8. https://pbs.twimg.com/media/B_-ykb6VAAARz9e.png[/img]

Important Information

By using this site, you agree to our Terms of Use.

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.