edivad99/dimstorage

DimStorage add a technologic version of ender chest system with owner, frequence selection and lock system

dimstorage's Issues

Reguest for DIM-Bag

mod is excellent, well done. Looking for a dim-bag or dim backpack so user can open it up, without having to place a block down.

[1.18.2] Stuck at joining world (caused by update check?)

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

Similar to #48

This is a new world with only DimStorage mod.
I got stuck on this screen for about 5 minutes, but it still hasn't changed anything.

After analysing latest.log I guess it caused by update checking. I hope you can fix it or at least let me toggle it in config.

How can I reproduce this bug or crash?

1. build a version with only DimStorage mod
2. create a new world

Configuration

- Mod version:1.18.2-6.1.0 (latest)
- Forge version:40.2.10
- Minecraft version:1.18.2

Relevant log output

[16Sep2023 03:21:21.217] [Render thread/ERROR] [net.minecraft.util.thread.BlockableEventLoop/FATAL]: Error executing task on Client
java.lang.NullPointerException: Cannot invoke "java.util.Map.get(Object)" because the return value of "net.minecraftforge.fml.VersionChecker$CheckResult.changes()" is null
	at edivad.dimstorage.setup.EventHandler.handlePlayerLoggedInEvent(EventHandler.java:26) ~[DimStorage-1.18.2-6.1.0.jar%2354!/:6.1.0]
	at net.minecraftforge.eventbus.ASMEventHandler_28_EventHandler_handlePlayerLoggedInEvent_LoggedInEvent.invoke(.dynamic) ~[?:?]
	at net.minecraftforge.eventbus.ASMEventHandler.invoke(ASMEventHandler.java:85) ~[eventbus-5.0.3.jar%2336!/:?]
	at net.minecraftforge.eventbus.EventBus.post(EventBus.java:302) ~[eventbus-5.0.3.jar%2336!/:?]
	at net.minecraftforge.eventbus.EventBus.post(EventBus.java:283) ~[eventbus-5.0.3.jar%2336!/:?]
	at net.minecraftforge.client.ForgeHooksClient.firePlayerLogin(ForgeHooksClient.java:969) ~[forge-1.18.2-40.2.10-universal.jar%2360!/:?]
	at net.minecraft.client.multiplayer.ClientPacketListener.m_5998_(ClientPacketListener.java:363) ~[client-1.18.2-20220404.173914-srg.jar%2355!/:?]
	at net.minecraft.network.protocol.game.ClientboundLoginPacket.m_5797_(ClientboundLoginPacket.java:83) ~[client-1.18.2-20220404.173914-srg.jar%2355!/:?]
	at net.minecraft.network.protocol.game.ClientboundLoginPacket.m_5797_(ClientboundLoginPacket.java:19) ~[client-1.18.2-20220404.173914-srg.jar%2355!/:?]
	at net.minecraft.network.protocol.PacketUtils.m_131356_(PacketUtils.java:22) ~[client-1.18.2-20220404.173914-srg.jar%2355!/:?]
	at net.minecraft.util.thread.BlockableEventLoop.m_6367_(BlockableEventLoop.java:157) ~[client-1.18.2-20220404.173914-srg.jar%2355!/:?]
	at net.minecraft.util.thread.ReentrantBlockableEventLoop.m_6367_(ReentrantBlockableEventLoop.java:23) ~[client-1.18.2-20220404.173914-srg.jar%2355!/:?]
	at net.minecraft.util.thread.BlockableEventLoop.m_7245_(BlockableEventLoop.java:131) ~[client-1.18.2-20220404.173914-srg.jar%2355!/:?]
	at net.minecraft.util.thread.BlockableEventLoop.m_18699_(BlockableEventLoop.java:116) ~[client-1.18.2-20220404.173914-srg.jar%2355!/:?]
	at net.minecraft.client.Minecraft.m_91383_(Minecraft.java:1015) ~[client-1.18.2-20220404.173914-srg.jar%2355!/:?]
	at net.minecraft.client.Minecraft.m_91374_(Minecraft.java:665) ~[client-1.18.2-20220404.173914-srg.jar%2355!/:?]
	at net.minecraft.client.main.Main.main(Main.java:205) ~[client-1.18.2-20220404.173914-srg.jar%2355!/:?]
	at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:?]
	at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) ~[?:?]
	at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?]
	at java.lang.reflect.Method.invoke(Method.java:568) ~[?:?]
	at net.minecraftforge.fml.loading.targets.CommonClientLaunchHandler.lambda$launchService$0(CommonClientLaunchHandler.java:31) ~[fmlloader-1.18.2-40.2.10.jar%2352!/:?]
	at cpw.mods.modlauncher.LaunchServiceHandlerDecorator.launch(LaunchServiceHandlerDecorator.java:37) [modlauncher-9.1.3.jar%2339!/:?]
	at cpw.mods.modlauncher.LaunchServiceHandler.launch(LaunchServiceHandler.java:53) [modlauncher-9.1.3.jar%2339!/:?]
	at cpw.mods.modlauncher.LaunchServiceHandler.launch(LaunchServiceHandler.java:71) [modlauncher-9.1.3.jar%2339!/:?]
	at cpw.mods.modlauncher.Launcher.run(Launcher.java:106) [modlauncher-9.1.3.jar%2339!/:?]
	at cpw.mods.modlauncher.Launcher.main(Launcher.java:77) [modlauncher-9.1.3.jar%2339!/:?]
	at cpw.mods.modlauncher.BootstrapLaunchConsumer.accept(BootstrapLaunchConsumer.java:26) [modlauncher-9.1.3.jar%2339!/:?]
	at cpw.mods.modlauncher.BootstrapLaunchConsumer.accept(BootstrapLaunchConsumer.java:23) [modlauncher-9.1.3.jar%2339!/:?]
	at cpw.mods.bootstraplauncher.BootstrapLauncher.main(BootstrapLauncher.java:149) [bootstraplauncher-1.0.0.jar:?]
	at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:?]
	at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) ~[?:?]
	at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?]
	at java.lang.reflect.Method.invoke(Method.java:568) ~[?:?]
	at oolloo.jlw.Wrapper.invokeMain(Wrapper.java:60) [JavaWrapper.jar:?]
	at oolloo.jlw.Wrapper.main(Wrapper.java:53) [JavaWrapper.jar:?]

Anything else?

No response

[Suggestion] Allowing other players to use your private chests/tanks

Adding a command to allow others to access/break your DimStorage chests/tanks.
Something like this, /dimstorage trust/ally/WhateverYouThinkFitsHere (name)

Player keep being disconnected, console spam and eventually server crash when Dim Chest is set to private

Describe the bug
A player player crafted some dimensional chest, put one down, set it private and has been disconneted from server, being then disconnected every time he tryied to log back in, until I destroyed the dimensional chest for him on op level 4.
We tested that again at that point to be sure, with the same result

Configuration
Mod version: DimStorage-1.12.2-1.3.0
Forge version: 1.12.2 - 14.23.5.2854
Minecraft version: 1.12.2
Are you playing on server?: yes

To Reproduce
Steps to reproduce the behavior: the same of the description I guess

Expected behavior
the player not getting dc? lol

Additional context
the relevant part in the pastebin is the
at net.minecraft.nbt.NBTTagCompound.writeEntry(NBTTagCompound.java:475) ~[fy.class:?]
console spam at the bottom, I guess

https://pastebin.com/

Well... I just hope 1.12.2 is still supported, we've switched to Ender Storage in the meanwhile

[1.16.1] Tanks/Chests get 'locked' after server restart.

Describe the bug
Whenever a server restarts, the tanks/chests get 'locked'. All pipes and importers and such can't connect to them unless you either break and place them down again or lock and unlock them.

Configuration
Mod version: DimStorage-1.16.1-4.0.2
Forge version: 32.0.108
Minecraft version: 1.16.1
Are you playing on server?: Yes

To Reproduce
Steps to reproduce the behavior:

1. Place down a dim tank/chest
2. Connect a pipe to it or an importer/exporter
3. Restart server
4. Notice that the pipe is not connected nor can you import/export items from/to it

Expected behavior
For the chests/tanks to not 'lock' after a restart

Screenshots

Add new configuration

Allow collection to be disabled from dim storage to stop duping and griefing.
Dim storage will not be added to the next ATM pack if not fixed and may be removed from current active packs

Enhancement: Allow The Chest To Be Partitioned

One of the big problems with the EnderStorage mod is that you have little control over what gets inserted and extracted. For instance, using it to feed a Wither Builder means you have to load it with thousands of items, and then there's a potential of extracting all of one item, and you have to manually reset it.

If the DimStorage chest could allow you to fix the content filter for each slot, that would allow a guaranteed stack of just the items you want to transmit without excess and without the risk of emptying the slot.

Having to reset the tanks an chests everytime u log in

Everytime i log in i have to go into the nether an reset the tank to get it to accept fluid an the same thing happens with the chests dunno if this is the way it was coded or if its a bug

Version 1.16.1 -4.0.2
Forge version 32.0.1.08
Minecraft version 1.16.1
Single player

Configuration
Mod version:
Forge version:
Minecraft version:
Are you playing on server?:

Was expecting to not have to reset the auto eject idle feature to get the tanks/chests to accept items again does it everytime i relog or log in

The "Fourth Option" for collecting/idle button isn't present.

I'm on an ATM8 1.19.2 server, V1.0.6b and the fourth button enabling 3x3 pickup of items simply isn't there. there is nothing in the config file about enabling/disabling it, so I'm just sending in this report. Thanks!

Dimensional Chest destroyed when breaking with pickaxe

Describe the bug
Dimensional Chests are destroyed when breaking them. This did not happen on previous mod versions. I am using the same pickaxes, and one even has Silk Touch. The chest is destroyed regardless.

Configuration
Mod version: DimStorage-1.15.2-3.1.4
Forge version: forge-31.2.0
Minecraft version: 1.15.2
Are you playing on server?: Yes, running modpack ATM5 v1.25

To Reproduce
Steps to reproduce the behavior:

1. Place Dimensional Chest
2. Break Dimensional Chest using appropriate tool (pickaxe)

Expected behavior
Upon breaking, the chest should drop to the ground to be picked up.

NPE when using /setblock to create dimstorage:dimensional_tank

Describe the bug
A clear and concise description of what the bug is.

Configuration
Mod version: 6.0.0
Forge version: 39.0.64
Minecraft version: 1.18.1
Are you playing on server?: No

To Reproduce
Steps to reproduce the behavior:

1. execute command /setblock ~1 ~ ~ dimstorage:dimensional_tank destroy
2. game crashes with:

java.lang.NullPointerException: Cannot invoke "edivad.dimstorage.api.Frequency.copy()" because "freq" is null
	at edivad.dimstorage.api.AbstractDimStorage.<init>(AbstractDimStorage.java:15) ~[DimStorage-1.18.1-6.0.0.jar%23170!/:6.0.0] {re:classloading}
	at edivad.dimstorage.storage.DimTankStorage.<init>(DimTankStorage.java:29) ~[DimStorage-1.18.1-6.0.0.jar%23170!/:6.0.0] {re:classloading}
	at edivad.dimstorage.plugin.DimTankPlugin.createDimStorage(DimTankPlugin.java:16) ~[DimStorage-1.18.1-6.0.0.jar%23170!/:6.0.0] {re:classloading}
	at edivad.dimstorage.manager.DimStorageManager.getStorage(DimStorageManager.java:174) ~[DimStorage-1.18.1-6.0.0.jar%23170!/:6.0.0] {re:classloading}
	at edivad.dimstorage.network.TankState.getFluidStorageServer(TankState.java:48) ~[DimStorage-1.18.1-6.0.0.jar%23170!/:6.0.0] {re:classloading}
	at edivad.dimstorage.network.TankState.update(TankState.java:27) ~[DimStorage-1.18.1-6.0.0.jar%23170!/:6.0.0] {re:classloading}
	at edivad.dimstorage.blockentities.BlockEntityDimTank.onServerTick(BlockEntityDimTank.java:68) ~[DimStorage-1.18.1-6.0.0.jar%23170!/:6.0.0] {re:classloading}
	at edivad.dimstorage.blockentities.BlockEntityFrequencyOwner.serverTick(BlockEntityFrequencyOwner.java:72) ~[DimStorage-1.18.1-6.0.0.jar%23170!/:6.0.0] {re:classloading}
	at net.minecraft.world.level.chunk.LevelChunk$BoundTickingBlockEntity.m_142224_(LevelChunk.java:673) ~[client-1.18.1-20211210.034407-srg.jar%23448!/:?] {re:classloading,pl:accesstransformer:B}
	at net.minecraft.world.level.chunk.LevelChunk$RebindableTickingBlockEntityWrapper.m_142224_(LevelChunk.java:768) ~[client-1.18.1-20211210.034407-srg.jar%23448!/:?] {re:classloading,pl:accesstransformer:B}
	at net.minecraft.world.level.Level.redirect$bdg000$redirectTick(Level.java:2082) ~[client-1.18.1-20211210.034407-srg.jar%23448!/:?] {re:mixin,pl:accesstransformer:B,re:classloading,pl:accesstransformer:B,pl:mixi
	at net.minecraft.world.level.Level.m_46463_(Level.java:476) ~[client-1.18.1-20211210.034407-srg.jar%23448!/:?] {re:mixin,pl:accesstransformer:B,re:classloading,pl:accesstransformer:B,pl:mixin:APP:kubejs-common.m
	at net.minecraft.server.level.ServerLevel.m_8793_(ServerLevel.java:324) ~[client-1.18.1-20211210.034407-srg.jar%23448!/:?] {re:mixin,pl:accesstransformer:B,re:classloading,pl:accesstransformer:B,pl:mixin:APP:blu
	at net.minecraft.server.MinecraftServer.m_5703_(MinecraftServer.java:868) ~[client-1.18.1-20211210.034407-srg.jar%23448!/:?] {re:mixin,pl:accesstransformer:B,re:classloading,pl:accesstransformer:B,pl:mixin:A}
	at net.minecraft.server.MinecraftServer.m_5705_(MinecraftServer.java:808) ~[client-1.18.1-20211210.034407-srg.jar%23448!/:?] {re:mixin,pl:accesstransformer:B,re:classloading,pl:accesstransformer:B,pl:mixin:A}
	at net.minecraft.client.server.IntegratedServer.m_5705_(IntegratedServer.java:86) ~[client-1.18.1-20211210.034407-srg.jar%23448!/:?] {re:classloading,pl:runtimedistcleaner:A}
	at net.minecraft.server.MinecraftServer.m_130011_(MinecraftServer.java:668) ~[client-1.18.1-20211210.034407-srg.jar%23448!/:?] {re:mixin,pl:accesstransformer:B,re:classloading,pl:accesstransformer:B,pl:mixin:A}
	at net.minecraft.server.MinecraftServer.m_177918_(MinecraftServer.java:258) ~[client-1.18.1-20211210.034407-srg.jar%23448!/:?] {re:mixin,pl:accesstransformer:B,re:classloading,pl:accesstransformer:B,pl:mixin:A}

Expected behavior
the game not to crash

DimStorage owner breaks with colors

When setting owner on the chest it seems to be including any name color with the name, so if a players name color changes they will no longer have access to the chest.
https://i.imgur.com/gzwx8zc.gifv

Dimchest cannot be dismantled after the update, not even as admin

Describe the bug
A clear and concise description of what the bug is.

Configuration
Mod version: DimStorage-1.14.4-2.3.2.jar
Forge version: 1.14.4-forge-28.2.0
Minecraft version: 1.14.4
Are you playing on server?: i am server hoster ! and yes i play on my server

The Dimchest was placed before the update, and now it cannot be dismantled.

Modid dimstorage fires events every second and saturates console.

Describe the bug
I have no idea why, but ever since the first time I have installed this mod in our server, we are getting these same messages in less than a second in console:

[16Jun2020 02:42:38.942] [Thread-1/DEBUG] [net.minecraftforge.fml.config.ConfigFileTypeHandler/CONFIG]: Config file dimstorage-common.toml changed, sending notifies
[16Jun2020 02:42:38.945] [Thread-1/DEBUG] [net.minecraftforge.fml.config.ConfigFileTypeHandler/CONFIG]: Config file forge-server.toml changed, sending notifies
[16Jun2020 02:42:38.945] [Thread-1/FATAL] [net.minecraftforge.common.ForgeConfig/CORE]: Forge config just got changed on the file system!  

The mod works well, however. It's just the console that gets filled all the time with the same message every second.

Configuration
Mod version: DimStorage-1.14.4-2.4.5
Forge version: 28.2.0
Minecraft version: 1.14.4
Are you playing on server?: Yes.

To Reproduce
Upload the mod using the version above.

Expected behavior
No fatal or log messages at every second

If anything, I got the log to help with searching the problem!

Thank you for the time taken to read all this!

[1.16.3] Server crashes when world is loaded

Describe the bug
Server crashes when world is loaded

Configuration
Mod version: 4.2.0
Forge version: 34.1.1
Minecraft version: 1.16.3
Are you playing on server?: Yes

To Reproduce
Steps to reproduce the behavior:
No clue, tried to restart server, got this error
Edit: after figuring some stuff out from the log, seems to need an AE2 system importing from a dim chest

Expected behavior
Able to see server load without crashing

Log

[1.15.2] Server crash on startup

Describe the bug
As title.

Configuration
Mod version: 3.1.1
Forge version: 31.1.47
Minecraft version: 1.15.2
Are you playing on server?: Yes

Additional context
Latest log: https://gist.github.com/ocram9/cb9f43b44ea7a3de37b70617a3a88d64
Crash log: https://gist.github.com/ocram9/c1966136c3c8013f8d83aa88884fabb6

Can I turn off update detection？

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

When I enter the game, the update prompt and changelog are displayed in the chat box, but there is no new version, and my game is stuck here. It's not that the window doesn't respond. I can't do anything just in that screen,that I had to force the game to restart...
But it's strange that this won't happen the second time I enter the game........

How can I reproduce this bug or crash?

Open the game and enter the world

Configuration

- Mod version:DimStorage-1.18.2-6.1.0
- Forge version:40.1.25
- Minecraft version:1.18.2

Relevant log output

No response

Anything else?

No response

dimstorage-server.toml is not correct

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

currently running an ATM 8 server and am constantly spammed with this in the console. How can I configure the file to repair it?

[Thread-0/WARN] [net.minecraftforge.fml.config.ConfigFileTypeHandler/CONFIG]: Configuration file C:\Users\black\OneDrive\Desktop\The one true server.\Boi\serverconfig\dimstorage-server.toml is not correct. Correcting

How can I reproduce this bug or crash?

happens every time I launch my server

Configuration

- Mod version:7.2.0
- Forge version:43.1.25
- Minecraft version:1.19.2

Relevant log output

No response

Anything else?

No response

Item names and tooltips missing from Dimensional Tablet

Item names and tooltips do not show on any of the items in the dimensional tablet gui in both the dimensional storage and the player inventory. I assume this isn't intentional as they appear to show fine in the dimensional storage chest.

https://uberi.fi/x/EpsilonIantheOeO

https://uberi.fi/x/OmicronMemnonY3S

Interaction with refined storage causes voided drives!!! :(

Describe the bug
this is an "unexpected interaction" bug between this mod and popular mods https://github.com/refinedmods/refinedstorage.

I'm also using https://github.com/Edivad99/ExtraStorage and https://github.com/MelanX/ExtraDisks but i believe this can be reproduced without those mods. that said, there's a possibility the interactions comes from either the Importer from @ExtraStorage, or the drive from @extradisks, so i'm noting it for completeness.

to produce the bug, one would basically make a "compact" ME setup with a dimensional chest, being within the 3x3 of the refined storage "disk drive" and an importer pointing from the Dimensional chest to the ME system, results in drive being pulled form the dimensional storage without a block update on the "disk drive" and the drive(s) that was/were placed in the into the ME systems "storage" even though that drive is no longer in the "disk drive". what happens is it causes the drive to be stored "within itself".

(I used @ExtraStorage "advanced importer" but I'm guessing a @RefinedStorage importer would do the same)

if noticed the drive can be retrieved from a "crafting grid" but only if done quickly. if not noticed, then the system will void the drive. which could lead to loss of millions of items. like in in my case .

I'm going to open a related issue on the other mods involved in the interaction, hopefully you guys can figure out what the best fix is, but current behavior is certainly a harrowing experience as you could be like me, where i just lost 100k and several weeks of progression, on a public server where I'm not OP and can't give myself back the important items. :(

ultimately I it would be a good idea to black list the "disk drive" block on the collecting if possible, as I very very very much doubt this is going to be the intended functionality for the majority of people.

alternatively i think the dimensional chest would need to preform a "block update" when it pulls the items, as the disk drive block doesn't realize the drive has been pulled from it.

Configuration
Mod version: 4.4.0
Forge version: 36.1.2
Minecraft version: 1.16
Are you playing on server?: yes. public server for TNP Limitless 3 mod pack

To Reproduce
here are the Steps to reproduce the behavior and what i see as the "bugs" in the interaction:

1. set up a simple refined storage ME system with an advanced importer pointing to the dimensional chest and a "disk drive" from refined storage within the 3x3 of the dimensional chest.
2. insert a single drive into the "disk drive"
3. click the "collecting" button on the dimensional chest within a 3x3 of the "disk drive" of the
4. watch the drive get pulled from the "disk drive" from refined storage. (this is not expected behavior, the "disk drive" could/should be black listed on the collecting config)
   but still get imported into the the crafting storage.
5. watch the advanced importer still pull the drive out of the dimensional chest and push it into the ME. (this is not expected behavior, the "disk drive" no longer has any disks, how is the importer still importing the items?)
6. after closing the dimensional chest UI, notice the block of the "disk drive" hasn't been updated, and it still "visually" looks like the disk is there. (likely bug caused by dimensional chest not updating the "disk drive" block when it does the collecting)
7. right click the "disk drive" block, to confirm the drive isn't there. (even though the block "visually" has it in the world, just not in the UI.
8. click the crafting grid, notice that the drive is there and at this point so are all the items. and if you hover over the drive, it, it will have the count of all items in it, but now +1 as its "stored within itself" (likely bug caused by dimensional chest not updating the "disk drive" block when it does the collecting)
9. if smart, pull the drive out of the ME, and put it back in the "disk drive" which will force a block update on the disk drive.

Expected behavior
the dimensional chest shouldn't be "collecting" the drive from the disk drive. I very much doubt any player will ever have this as "expected" behavior, and so it would be good to black list that block. may also want to look into what other blocks it "collects" from that maybe could be added to a black list. if you do decide to keep updating form that block, then the block needs to be updated, so that it can tell the rest of the ME, that it no longer has storage. so it can turn the importer OFF.

Screenshots

here you can see a "compact" setup of an ME system, where the Dimensional Chest is being used as a "send it to the ME system" such as for long exploring adventure.

here you can see the drive with it stored within itself

Additional context
no problem occurs unless the "collecting" button is pressed. I assume there also wouldn't be a problem if the disk drive was outside the 3x3 radius, but since this just voided all my items including my cable... i don't really have the time to test before opening the issue.

[1.19.2] Server configuration file dimstorage-server.toml keeps reverting DimTablet.allow_list to default on load / sometimes on edit.

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

The world I am using here only has the following mods: DimStorage, edivadlib, and configured - configured is solely for data collection simplicity and has no effect on the results.
It is being run only on singleplayer and launched offline.

Whenever loading server configs, the key DimTablet.allow_list in server configuration file dimstorage-server.toml is reverted to its default with the following error; done here via configured for log simplicity, but it worked the exact same in-world.
[21:39:34] [Render thread/WARN] [ne.mi.co.ForgeConfigSpec/CORE]: Configuration file /home/silvally/.var/app/org.prismlauncher.PrismLauncher/data/PrismLauncher/instances/1.19.2/.minecraft/saves/New World (3)/serverconfig/dimstorage-server.toml is not correct. Correcting
[21:39:34] [Render thread/WARN] [ne.mi.co.ForgeConfigSpec/CORE]: Incorrect key DimTablet.allow_list was corrected from [minecraft:dirt, minecraft:gravel, minecraft:cobblestone, minecraft:granite, minecraft:diorite, minecraft:andesite, minecraft:sand, minecraft:sandstone, minecraft:netherrack, minecraft:end_stone] to its default, [minecraft:dirt, minecraft:gravel, minecraft:cobblestone, minecraft:granite, minecraft:diorite, minecraft:andesite, minecraft:sand, minecraft:sandstone, minecraft:netherrack, minecraft:end_stone].
[21:39:34] [Thread-0/WARN] [ne.mi.fm.co.ConfigFileTypeHandler/CONFIG]: Configuration file /home/silvally/.var/app/org.prismlauncher.PrismLauncher/data/PrismLauncher/instances/1.19.2/.minecraft/saves/New World (3)/serverconfig/dimstorage-server.toml is not correct. Correcting
[21:39:34] [Render thread/INFO] [configured/]: Started editing 'dimstorage-server.toml'
[21:39:35] [Render thread/INFO] [configured/]: Stopped editing 'dimstorage-server.toml'
[21:39:40] [Render thread/WARN] [ne.mi.co.ForgeConfigSpec/CORE]: Configuration file /home/silvally/.var/app/org.prismlauncher.PrismLauncher/data/PrismLauncher/instances/1.19.2/.minecraft/saves/New World (3)/serverconfig/dimstorage-server.toml is not correct. Correcting
[21:39:40] [Render thread/WARN] [ne.mi.co.ForgeConfigSpec/CORE]: Incorrect key DimTablet.allow_list was corrected from [minecraft:dirt, minecraft:gravel, minecraft:cobblestone, minecraft:granite, minecraft:diorite, minecraft:andesite, minecraft:sand, minecraft:sandstone, minecraft:netherrack, minecraft:end_stone] to its default, [minecraft:dirt, minecraft:gravel, minecraft:cobblestone, minecraft:granite, minecraft:diorite, minecraft:andesite, minecraft:sand, minecraft:sandstone, minecraft:netherrack, minecraft:end_stone].
[21:39:40] [Thread-0/WARN] [ne.mi.fm.co.ConfigFileTypeHandler/CONFIG]: Configuration file /home/silvally/.var/app/org.prismlauncher.PrismLauncher/data/PrismLauncher/instances/1.19.2/.minecraft/saves/New World (3)/serverconfig/dimstorage-server.toml is not correct. Correcting
[21:39:40] [Render thread/INFO] [configured/]: Started editing 'dimstorage-server.toml'
[21:39:41] [Render thread/INFO] [configured/]: Stopped editing 'dimstorage-server.toml'
I show it duplicated here because it happens every time - even if the config has not been changed. As you can see, the 'corrected' version and the default are exactly the same.

When checking the allow list in configured, the following occurs:

Here I just clicked edit on an existing entry, and it implies that it's invalid with being red and unable to apply changes (of which i made none).

When i have a tablet properly linked to a chest and with auto-pickup enabled, any item in DimTablet.allow_list is picked up by it as expected. To me (a python user, so i may be wrong), this implies that the function is expecting the wrong type of variable, but is working as expected when given a list - but because the list isn't what the function expects, it reverts to the default, which is also a list and works as expected to the user.

Another interesting note is that using /dimtablet add is immediately triggering the correction:
[21:54:38] [Thread-0/WARN] [ne.mi.fm.co.ConfigFileTypeHandler/CONFIG]: Configuration file /home/silvally/.var/app/org.prismlauncher.PrismLauncher/data/PrismLauncher/instances/1.19.2/.minecraft/saves/New World (4)/serverconfig/dimstorage-server.toml is not correct. Correcting
[21:54:38] [Render thread/INFO] [minecraft/ChatComponent]: [System] [CHAT] Item added to the list
[21:54:44] [Render thread/INFO] [minecraft/ChatComponent]: [System] [CHAT] Disabled autocollect
[21:54:44] [Render thread/INFO] [minecraft/ChatComponent]: [System] [CHAT] Enabled autocollect
[21:54:50] [Render thread/INFO] [minecraft/ChatComponent]: [System] [CHAT] These are the items that the DimTablet will move:
[21:54:50] [Render thread/INFO] [minecraft/ChatComponent]: [System] [CHAT] minecraft:dirt
[21:54:50] [Render thread/INFO] [minecraft/ChatComponent]: [System] [CHAT] minecraft:gravel
[21:54:50] [Render thread/INFO] [minecraft/ChatComponent]: [System] [CHAT] minecraft:cobblestone
[21:54:50] [Render thread/INFO] [minecraft/ChatComponent]: [System] [CHAT] minecraft:granite
[21:54:50] [Render thread/INFO] [minecraft/ChatComponent]: [System] [CHAT] minecraft:diorite
[21:54:50] [Render thread/INFO] [minecraft/ChatComponent]: [System] [CHAT] minecraft:andesite
[21:54:50] [Render thread/INFO] [minecraft/ChatComponent]: [System] [CHAT] minecraft:sand
[21:54:50] [Render thread/INFO] [minecraft/ChatComponent]: [System] [CHAT] minecraft:sandstone
[21:54:50] [Render thread/INFO] [minecraft/ChatComponent]: [System] [CHAT] minecraft:netherrack
[21:54:50] [Render thread/INFO] [minecraft/ChatComponent]: [System] [CHAT] minecraft:end_stone
(The world number changed because i forgot to allow commands on New World 3 and made a new one with no changes besides allowing commands)
Here, I had a stick in my mainhand, and ran /dimtablet add - the stick did not go into the tablet. I then disabled and enabled the autocollect to show that it was on, and ran /dimtablet list to show that the list is still only the defaults.
(One interesting note i don't understand - something in my main world is preventing the [Thread-0/WARN] messages throughout the whole log, and if i add something to the list it persists and thus works until the config is reloaded in some way. So I think both the Thread-0 and the Render thread 'correcting' messages are making the actual correction.)

I hope this is enough/good information to help with the problem, and thank you for your time :)

How can I reproduce this bug or crash?

1. Run an instance of 1.19.2 with DimStorage and EdivadLib. Configured is helpful but not necessary.
2. Open the world and check the logs - even if the config is already default, it will have been 'corrected' to default.
3. If you don't have a dimensional tablet linked to a dimensional chest already, either make them or use /give, creative, or some other form of cheating for testing purpose. Make sure the tablet has autocollect on.
4. Hold any item that isn't on the defaults list in your mainhand. Run /dimtablet add.
5. If the item remains in your mainhand - check the log again and/or /dimtablet list, you'll see that the item you attempted to add is not on the list, even as the mod outputs to chat saying it was added.
6. If the item is put into the tablet - log out of the world and back in, and get another of that same item. As the config will have been reset again, it now won't go into the tablet with autocollect on unless you add it agani.

Configuration

- Mod version: 7.2.0
- Lib version: 1.2.0
- Forge version: 43.2.14
- Minecraft version: 1.19.2

Relevant log output

[21:39:34] [Render thread/WARN] [ne.mi.co.ForgeConfigSpec/CORE]: Configuration file /home/silvally/.var/app/org.prismlauncher.PrismLauncher/data/PrismLauncher/instances/1.19.2/.minecraft/saves/New World (3)/serverconfig/dimstorage-server.toml is not correct. Correcting
[21:39:34] [Render thread/WARN] [ne.mi.co.ForgeConfigSpec/CORE]: Incorrect key DimTablet.allow_list was corrected from [minecraft:dirt, minecraft:gravel, minecraft:cobblestone, minecraft:granite, minecraft:diorite, minecraft:andesite, minecraft:sand, minecraft:sandstone, minecraft:netherrack, minecraft:end_stone] to its default, [minecraft:dirt, minecraft:gravel, minecraft:cobblestone, minecraft:granite, minecraft:diorite, minecraft:andesite, minecraft:sand, minecraft:sandstone, minecraft:netherrack, minecraft:end_stone].
[21:39:34] [Thread-0/WARN] [ne.mi.fm.co.ConfigFileTypeHandler/CONFIG]: Configuration file /home/silvally/.var/app/org.prismlauncher.PrismLauncher/data/PrismLauncher/instances/1.19.2/.minecraft/saves/New World (3)/serverconfig/dimstorage-server.toml is not correct. Correcting
[21:39:34] [Render thread/INFO] [configured/]: Started editing 'dimstorage-server.toml'
[21:39:35] [Render thread/INFO] [configured/]: Stopped editing 'dimstorage-server.toml'
[21:39:40] [Render thread/WARN] [ne.mi.co.ForgeConfigSpec/CORE]: Configuration file /home/silvally/.var/app/org.prismlauncher.PrismLauncher/data/PrismLauncher/instances/1.19.2/.minecraft/saves/New World (3)/serverconfig/dimstorage-server.toml is not correct. Correcting
[21:39:40] [Render thread/WARN] [ne.mi.co.ForgeConfigSpec/CORE]: Incorrect key DimTablet.allow_list was corrected from [minecraft:dirt, minecraft:gravel, minecraft:cobblestone, minecraft:granite, minecraft:diorite, minecraft:andesite, minecraft:sand, minecraft:sandstone, minecraft:netherrack, minecraft:end_stone] to its default, [minecraft:dirt, minecraft:gravel, minecraft:cobblestone, minecraft:granite, minecraft:diorite, minecraft:andesite, minecraft:sand, minecraft:sandstone, minecraft:netherrack, minecraft:end_stone].
[21:39:40] [Thread-0/WARN] [ne.mi.fm.co.ConfigFileTypeHandler/CONFIG]: Configuration file /home/silvally/.var/app/org.prismlauncher.PrismLauncher/data/PrismLauncher/instances/1.19.2/.minecraft/saves/New World (3)/serverconfig/dimstorage-server.toml is not correct. Correcting
[21:39:40] [Render thread/INFO] [configured/]: Started editing 'dimstorage-server.toml'
[21:39:41] [Render thread/INFO] [configured/]: Stopped editing 'dimstorage-server.toml'

[21:54:38] [Thread-0/WARN] [ne.mi.fm.co.ConfigFileTypeHandler/CONFIG]: Configuration file /home/silvally/.var/app/org.prismlauncher.PrismLauncher/data/PrismLauncher/instances/1.19.2/.minecraft/saves/New World (4)/serverconfig/dimstorage-server.toml is not correct. Correcting
[21:54:38] [Render thread/INFO] [minecraft/ChatComponent]: [System] [CHAT] Item added to the list
[21:54:44] [Render thread/INFO] [minecraft/ChatComponent]: [System] [CHAT] Disabled autocollect
[21:54:44] [Render thread/INFO] [minecraft/ChatComponent]: [System] [CHAT] Enabled autocollect
[21:54:50] [Render thread/INFO] [minecraft/ChatComponent]: [System] [CHAT] These are the items that the DimTablet will move:
[21:54:50] [Render thread/INFO] [minecraft/ChatComponent]: [System] [CHAT] minecraft:dirt
[21:54:50] [Render thread/INFO] [minecraft/ChatComponent]: [System] [CHAT] minecraft:gravel
[21:54:50] [Render thread/INFO] [minecraft/ChatComponent]: [System] [CHAT] minecraft:cobblestone
[21:54:50] [Render thread/INFO] [minecraft/ChatComponent]: [System] [CHAT] minecraft:granite
[21:54:50] [Render thread/INFO] [minecraft/ChatComponent]: [System] [CHAT] minecraft:diorite
[21:54:50] [Render thread/INFO] [minecraft/ChatComponent]: [System] [CHAT] minecraft:andesite
[21:54:50] [Render thread/INFO] [minecraft/ChatComponent]: [System] [CHAT] minecraft:sand
[21:54:50] [Render thread/INFO] [minecraft/ChatComponent]: [System] [CHAT] minecraft:sandstone
[21:54:50] [Render thread/INFO] [minecraft/ChatComponent]: [System] [CHAT] minecraft:netherrack
[21:54:50] [Render thread/INFO] [minecraft/ChatComponent]: [System] [CHAT] minecraft:end_stone

Anything else?

No response

Edit is because i forgot to finish a sentence (re: running offline) after rewriting it. apologies

Storage chest, Mekanism logistical pipe interaction

I am unable to pull items out of the dimensional chest with mekanism logistical pipes, I've tried a few other pipes from other mods, and they seem to work fine. Mekanism devs say they use the normal item handler api, so it should work.

Pack for reference is skybees - 3.3.3
Dimstorage 4.4.0 (updated to 4.4.1, still no joy)
Mekanism-1.16.5-10.0.21.448

Steps to reproduce?

1. Make dim. chest, place
2. Attach and configure mekanism logistical pipe (any of them, I checked them all)
3. Sadness

DimChest locks after going through nether portal

I set up a guardian farm using a dimchest to collect with the hope of being able to then have a linked chest deposit into my storage system. Unfortunately, after setting up the chest, when I return the overworld I see no items flowing in, even while I'm at my farm and see guardians making their way through the system. Is this intended, or is there some way to override this and prevent the locking from occurring? If not, is there a plan to address this moving forward?

[1.12.2] OpenComputers is marked as an optional dependency

Describe the bug
On Curseforge, OpenComputers is listed as an optional dependency. Without OC, the game will crash because it can't find an OC class.

Configuration
Mod version: DimStorage-1.12.2-1.3.0
Forge version: N/A
Minecraft version: 1.12.2
Are you playing on server?: N/A

To Reproduce
Steps to reproduce the behavior:

1. Put DimStorage in mods folder
2. Start game
3. Crash -> https://pastebin.com/LdtgcjQC

Expected behavior
OC needs to be marked as a required dependency so that when this mod is downloaded with a launcher it automatically downloads OC as well, preventing a crash.

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

After Last Upate chest owner error

original:
dopo l'ultimo aggiornamento non riesco più ad accedere alle mie chest, risultano intestate a "Owner: "
translated:
after the last update I can't access my chest anymore, they are registered to "Owner:"

[1.15.2] Can't remove items from RS grid when connected to DimStorage chest

Describe the bug
When I connect an external storage to a Dimensional Storage chest I can't use the Refined Storage grid anymore (as in I can't remove any items). I'm not sure if this is an issue with this mod or Refined Storage but I decided to report it here first. The chest is set to public and not locked.

Configuration
Mod version: 3.1.5
Forge version: 31.2.5
Minecraft version: 1.15.2
Are you playing on server?: Yes

To Reproduce
Steps to reproduce the behavior:

1. Place a DimStorage chest
2. Connect a Refined Storage external storage to the chest
3. Open the Refined Storage grid and try to remove items (if you click fast enough you can remove an item once but after that it doesn't work anymore).

Expected behavior
Being able to connect a Refined Storage external storage and still being able to access the Refined Storage grid.

Crash when trying to connect mekanism pipes in dim tank

Describe the bug
Crash when trying to connect mekanism pipes in dim tank.

Configuration
Mod version: 4.0.3
Forge version: 32.0.108
Minecraft version: 1.16.1
Are you playing on server?: No

To Reproduce
Steps to reproduce the behavior:

1. Create a Dim Tank
2. Try to connect a Mekanism Pipe into it.

If I revert to the previous version of dimstorage (4.0.2) the pipe doesn't connect, but the game opens at least.

[DimStorage 1.15.2-3.1.1] Crash on loading client and server

SERVER CRASH on load :
net.minecraftforge.fml.LoadingFailedException: Loading errors encountered: [
DimStorage (dimstorage) has failed to load correctly
java.lang.IllegalAccessError: no such constructor: edivad.dimstorage.blocks.DimTank.()void/newInvokeSpecial
]
at net.minecraftforge.fml.ModLoader.dispatchAndHandleError(ModLoader.java:201) ~[?:?] {re:classloading}
at net.minecraftforge.fml.ModLoader.gatherAndInitializeMods(ModLoader.java:183) ~[?:?] {re:classloading}
at net.minecraftforge.fml.server.ServerModLoader.begin(ServerModLoader.java:45) ~[?:?] {re:classloading}
at net.minecraft.server.dedicated.DedicatedServer.func_71197_b(DedicatedServer.java:122) ~[?:?] {re:classloading,pl:accesstransformer:B}
at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:613) [?:?] {re:classloading,pl:accesstransformer:B,pl:runtimedistcleaner:A}
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_202] {}

---

CLIENT CRASH :
it doesnt seems to be DimStorage related but my modpack works well with previous version
---- Minecraft Crash Report ----
// I'm sorry, Dave.

Time: 4/21/20 3:30 PM
Description: Initializing game

java.lang.NullPointerException: Registry Object not present: mekanism:basic_fluid_tank
at java.util.Objects.requireNonNull(Objects.java:290) ~[?:1.8.0_51] {}
at net.minecraftforge.fml.RegistryObject.get(RegistryObject.java:91) ~[?:?] {re:classloading}
at mekanism.common.registration.DoubleWrappedRegistryObject.getPrimary(DoubleWrappedRegistryObject.java:23) ~[?:?] {re:classloading}
at mekanism.common.registration.impl.BlockRegistryObject.getBlock(BlockRegistryObject.java:19) ~[?:?] {re:classloading}
at mekanism.client.ClientRegistrationUtil.registerBlockColorHandler(ClientRegistrationUtil.java:112) ~[?:?] {re:classloading}
at mekanism.client.ClientRegistration.registerItemColorHandlers(ClientRegistration.java:352) ~[?:?] {re:classloading}
at net.minecraftforge.eventbus.ASMEventHandler_484_ClientRegistration_registerItemColorHandlers_Item.invoke(.dynamic) ~[?:?] {}
at net.minecraftforge.eventbus.ASMEventHandler.invoke(ASMEventHandler.java:80) ~[eventbus-2.0.0-milestone.1-service.jar:?] {}
at net.minecraftforge.eventbus.EventBus.post(EventBus.java:258) ~[eventbus-2.0.0-milestone.1-service.jar:?] {}
at net.minecraftforge.fml.javafmlmod.FMLModContainer.acceptEvent(FMLModContainer.java:168) ~[?:31.1] {re:classloading}
at net.minecraftforge.fml.ModLoader.lambda$postEvent$30(ModLoader.java:243) ~[?:?] {re:classloading}
at net.minecraftforge.fml.ModLoader$$Lambda$5120/843325140.accept(Unknown Source) ~[?:?] {}
at java.util.HashMap.forEach(HashMap.java:1280) ~[?:1.8.0_51] {}
at net.minecraftforge.fml.ModList.forEachModContainer(ModList.java:217) ~[?:?] {re:classloading}
at net.minecraftforge.fml.ModLoader.postEvent(ModLoader.java:243) ~[?:?] {re:classloading}
at net.minecraftforge.client.ForgeHooksClient.onItemColorsInit(ForgeHooksClient.java:212) ~[?:?] {re:classloading}
at net.minecraft.client.renderer.color.ItemColors.func_186729_a(ItemColors.java:84) ~[?:?] {re:classloading,pl:runtimedistcleaner:A}
at net.minecraft.client.Minecraft.(Minecraft.java:421) [?:?] {re:classloading,pl:accesstransformer:B,pl:runtimedistcleaner:A}
at net.minecraft.client.main.Main.main(SourceFile:166) [?:?] {re:classloading}
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_51] {}
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_51] {}
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_51] {}
at java.lang.reflect.Method.invoke(Method.java:497) ~[?:1.8.0_51] {}
at net.minecraftforge.fml.loading.FMLClientLaunchProvider.lambda$launchService$0(FMLClientLaunchProvider.java:56) [forge-1.15.2-31.1.47.jar:31.1] {}
at net.minecraftforge.fml.loading.FMLClientLaunchProvider$$Lambda$461/1760443245.call(Unknown Source) [forge-1.15.2-31.1.47.jar:31.1] {}
at cpw.mods.modlauncher.LaunchServiceHandlerDecorator.launch(LaunchServiceHandlerDecorator.java:37) [modlauncher-5.0.0-milestone.4.jar:?] {}
at cpw.mods.modlauncher.LaunchServiceHandler.launch(LaunchServiceHandler.java:54) [modlauncher-5.0.0-milestone.4.jar:?] {}
at cpw.mods.modlauncher.LaunchServiceHandler.launch(LaunchServiceHandler.java:72) [modlauncher-5.0.0-milestone.4.jar:?] {}
at cpw.mods.modlauncher.Launcher.run(Launcher.java:81) [modlauncher-5.0.0-milestone.4.jar:?] {}
at cpw.mods.modlauncher.Launcher.main(Launcher.java:65) [modlauncher-5.0.0-milestone.4.jar:?] {}

Feature Request: >>Auto move items from player inventory to Tablet

Feature Request: Such good work, one other feature would literally make this the GO TO MOD.....like IRON BACKPACKS (well i think its tht mod) back for 1.12, have an option for all items to go directly into the tablet via config and hotkey to turn on off !

Tablet's not working on servers

Configuration
Mod version: DimStorage-1.15.2-3.0.2.jar
Forge version: 31.1.27
Minecraft version:1.15.2
Are you playing on server?:yes

To Reproduce
Steps to reproduce the behavior:
open tablet on server

Additional context

java.lang.RuntimeException: Attempted to load class net/minecraft/client/gui/screen/Screen for invalid dist DEDICATED_SERVER
	at net.minecraftforge.fml.loading.RuntimeDistCleaner.processClass(RuntimeDistCleaner.java:71) ~[forge-1.15.2-31.1.27.jar:31.1]
	at cpw.mods.modlauncher.serviceapi.ILaunchPluginService.processClass(ILaunchPluginService.java:103) ~[modlauncher-5.0.0-milestone.4.jar:5.0.0-milestone.4+67+b1a340b]
	at cpw.mods.modlauncher.LaunchPluginHandler.offerClassNodeToPlugins(LaunchPluginHandler.java:85) ~[modlauncher-5.0.0-milestone.4.jar:?]
	at cpw.mods.modlauncher.ClassTransformer.transform(ClassTransformer.java:115) ~[modlauncher-5.0.0-milestone.4.jar:?]
	at cpw.mods.modlauncher.TransformingClassLoader$DelegatedClassLoader.findClass(TransformingClassLoader.java:239) ~[modlauncher-5.0.0-milestone.4.jar:?]
	at cpw.mods.modlauncher.TransformingClassLoader.loadClass(TransformingClassLoader.java:126) ~[modlauncher-5.0.0-milestone.4.jar:?]
	at cpw.mods.modlauncher.TransformingClassLoader.loadClass(TransformingClassLoader.java:96) ~[modlauncher-5.0.0-milestone.4.jar:?]
	at java.lang.ClassLoader.loadClass(ClassLoader.java:357) ~[?:1.8.0_181]
	at edivad.dimstorage.items.DimTablet.func_77659_a(DimTablet.java:94) ~[?:3.0.2]
	at net.minecraft.item.ItemStack.func_77957_a(ItemStack.java:197) ~[?:?]
	at net.minecraft.server.management.PlayerInteractionManager.func_187250_a(PlayerInteractionManager.java:284) ~[?:?]
	at net.minecraft.network.play.ServerPlayNetHandler.func_147346_a(ServerPlayNetHandler.java:874) ~[?:?]
	at net.minecraft.network.play.client.CPlayerTryUseItemPacket.func_148833_a(SourceFile:31) ~[?:?]
	at net.minecraft.network.play.client.CPlayerTryUseItemPacket.func_148833_a(SourceFile:9) ~[?:?]
	at net.minecraft.network.PacketThreadUtil.func_225383_a(SourceFile:21) ~[?:?]
	at net.minecraft.util.concurrent.TickDelayedTask.run(SourceFile:18) ~[?:?]
	at net.minecraft.util.concurrent.ThreadTaskExecutor.func_213166_h(SourceFile:144) [?:?]
	at net.minecraft.util.concurrent.RecursiveEventLoop.func_213166_h(SourceFile:23) [?:?]
	at net.minecraft.server.MinecraftServer.func_213166_h(MinecraftServer.java:731) [?:?]
	at net.minecraft.server.MinecraftServer.func_213166_h(MinecraftServer.java:141) [?:?]
	at net.minecraft.util.concurrent.ThreadTaskExecutor.func_213168_p(SourceFile:118) [?:?]
	at net.minecraft.server.MinecraftServer.func_213205_aW(MinecraftServer.java:714) [?:?]
	at net.minecraft.server.MinecraftServer.func_213168_p(MinecraftServer.java:708) [?:?]
	at net.minecraft.util.concurrent.ThreadTaskExecutor.func_213160_bf(SourceFile:103) [?:?]
	at net.minecraft.server.MinecraftServer.func_213202_o(MinecraftServer.java:693) [?:?]
	at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:641) [?:?]
	at java.lang.Thread.run(Thread.java:748) [?:1.8.0_181]```

Server crash when placing the chest

MineCraft Version : 1.14.4
Forge Version : 1.14.4-forge-28.1.117
Mod Version: DimStorage-1.14.4-2.2.0.jar

The server closes as soon as you place the chest.
CrashLog : https://pastebin.com/m8BPEhh0
Forge Log : https://pastebin.com/tvsC9Z2V

Support for ComputerCraft peripheral

OpenComputers is not available on Minecraft 1.14/1.15+, but versions of ComputerCraft are. (cc-tweaked-1.15.2-1.86.2 for example)

Support for ComputerCraft Peripherals, in the same manner as OpenComputer Components, would be most appreciated, and immediately usable on version 1.14+ worlds.

[1.15.2] /dimtablet Commands Server vs. Client

I noticed in the latest version that a dimstorage-server.toml file was created in the serverconfig folder, and this is where server settings are now instead of the common file, but even before this change there is a strange behavior with the /dimtablet commands where it affects the entire server's config, even before the recent change.

When an item is added to the auto-picking list using dimtablet /add, the configuration is changed for the entire server and all players. This part of the configuration should be moved to a dimstorage-client.toml file and only affect the current player's client, not the entire server.

Thank you.

Button missing on Dimensional Chest?

Videos and pictures for the chest show a button in the GUI below 'Locked?' for controlling input/output options for the chest as shown in this pic from 9minecraft.net

https://www.9minecraft.net/wp-content/uploads/2020/04/DimStorage-mod-for-minecraft-03.jpg

I am in All The Modes 8, which is 1.19.2 and the button isn't there on the chest I made, oddly. Pic here:

https://www.flickr.com/photos/197625247@N03/52668255667/

Wondering if I need a new version? The mod is using DimStorage-1.19.2-7.2.0.jar which Curseforge shows as the latest.