Applied Energistics 2

Applied Energistics 2

156M Downloads

Spatial Storage issue

slink7 opened this issue · 11 comments

commented

Describe the bug

Powering a Spatial IO Port with redstone won't do anything, there's enough energy and Spatial pylons are toggled.
Using an 'Unformatted' 16^3 Spatial Storage Cell.

To Reproduce

Use the Spatial IO Port casualy

Expected behavior

I was expecting the structure in the SCS to get stocked in the Cell

Environment

  • Environment:
    Using Forge 35.0.18 and AE2 8.1.0 on minecraft 1.16.4
commented

@yueh I have the exact same problem with the exact same symptoms mentioned.

The log shows nothing when applying the redstone signal with biomes o plenty loaded. debug.log and latest.log included.

When BoP is not loaded, the normal behavior is:

[04Jan2021 12:01:45.686] [Server thread/INFO] [AE2:S/]: Block Copy Scale: 1, 1, 1
[04Jan2021 12:01:45.686] [Server thread/INFO] [AE2:S/]: Block Copy Time: 7600
[04Jan2021 12:01:45.689] [Server thread/INFO] [AE2:S/]: Update Time: 2520400

Reproducible using only:

Minecraft: 1.16.4
Forge: 35.1.29
Biomes O' Plenty: 1.16.4-13.0.0.426
Applied Energistics 2: 8.2.0-beta.2

Procedure:

  • Use biomes o plenty
  • Create a single player world (server world requires a minor configuration step to enable BoP world gen)
  • Setup the Spatial Containment Structure
  • Observe it fail to store a block with no logs.
  • Remove biomes o plenty.
  • Relaunch minecraft
  • Load the same world
  • Observe it succeed to store the block with the above "normal" logs in debug.
commented

As far as I can tell this is purely an BOP problem. With their custom worldtype they only add their custom overworld + nether + end, but no other world (BOPDimensionType.java#L59-L65).

So any mod adding new worlds can probably fail.

commented

If I'm understanding you correctly, AE2 isn't able to create/use extra dimensions because BoP doesn't allow the creation of extra dimensions.
So BoP is incompatible with mods like Twilight Forest (when/if updated), AE2 and more. Sad.
At the very least, I can get around this by temporarily turning on BoP world gen, pregenerating the world and turning it off. Alternate dimensions (multithreading) are too important to me to not go through this work. Thank you very much!

commented

We could potentially change our approach to always just add the spatial world, but currently it is rather that we don't support any but the normal world type for spatial, since we add our dimension to the default world type, rather than globally. In essence we do this to avoid the annoying "experimental features used" warning screen when loading into the world. If we were to use a JSON file for the dimension_type, that's what you'd get.

commented

I do not think that would actually help. When looking at the BOP tracker there are a bunch of reports with other mods not being able to add dimensions, biomes, etc.

As far as I can tell, BOP replaces the whole SimpleRegistry used to populate every dimension but the overworld without taking other mods into account. I would even guess that registering new dimension with a datapack has a good chance of not working at all.

Further while forge seems to add an event to replace the world type completely (which provides the simple registry), there seems to be no event to register custom dimensions at all. Only the dimension type usable as template. Or something which would indicate that Forge merges the vanilla one with whatever is provide by any mod replacing the world type.

So for now I assume it either forge needs to provide a way to register dimensions to any DimensionGeneratorSettings globally or BOP needs some sort of API to register them, but that would be a mess for any other mod as it needs explicit BOP support and support for every similar mod. Or each BOP like mod has to add support for every other mod adding dimensions to itself.

commented

I think the datapack dimensions are added later, the method they override is the "default dimension registry" as far as I know.

edit: We have to check if Forge actually brought back some of it's dimension abstractions or not. I doubt it, but we should still check.

commented

Mabe I'm just stupid and I'm using it wrong, but i have same problem. I'm using forge 35.1.29 and ae2 8.2.0

commented

I also had this issue. I was using ATM6 (1.3.1)

I did some testing and it seems to be related to an integration with biomes of plenty; as the issue only occurred when using the biomes of plenty level generator.

More Testing: Modified world originally generated as BoP to default generator. To do so, I edited level.dat and changed the GeneratorSetting for the overworld from minecraft:biomesofplenty_overworld to minecraft:overworld. I then loaded the world and tried the spatial IO port again and it functioned correctly.

commented
commented

Does it produce an error logged in the server log once applying the redstone signal? That might help to identify the issue.