You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using the latest versions, maybe not forge however this problem was before and after updating it. In dimensional doors, you can have a personal pocket. Something from the extended mod is causing my pocket to be wiped/disconnected, causing my doors to lead to new pockets at random times. Supposedly, something is generating on some blocks and causing the disconnections. ("Something from that mod generated over a rift during worldgen, and broke the rift registry somehow.") Here are the logs from another discussion I created regarding this issue:
2019-03-22-7.log.gz
2019-03-23-1.log.gz
2019-03-23-2.log.gz
I had sent more than one because I didn't know which one to send.
Here is the link to the issue on the dimensional doors page, if it is any help. DimensionalDevelopment/DimDoors#109
I'm uploading this on both this one and extended because I don't know if you use both or one or.. yeah.
The text was updated successfully, but these errors were encountered:
I'm using the latest versions, maybe not forge however this problem was before and after updating it. In dimensional doors, you can have a personal pocket. Something from the extended mod is causing my pocket to be wiped/disconnected, causing my doors to lead to new pockets at random times. Supposedly, something is generating on some blocks and causing the disconnections. ("Something from that mod generated over a rift during worldgen, and broke the rift registry somehow.") Here are the logs from another discussion I created regarding this issue:
2019-03-22-7.log.gz
2019-03-23-1.log.gz
2019-03-23-2.log.gz
I had sent more than one because I didn't know which one to send.
Here is the link to the issue on the dimensional doors page, if it is any help.
DimensionalDevelopment/DimDoors#109
I'm uploading this on both this one and extended because I don't know if you use both or one or.. yeah.
The text was updated successfully, but these errors were encountered: