Jump to content

Rseding91

Members
  • Posts

    4
  • Joined

  • Last visited

Everything posted by Rseding91

  1. Did you manage to fix the bug when moving AE systems where it says "Controller conflict"? Using the 1.5 version it never had this issue but in 1.6 with the same version (but for 1.6) it bugs out.
  2. I have a computercraft turtle with the wrench upgrade move the energy tesseract instead of the frames. The tesseract has the shiny dust upgrade so it saves its settings when picked up by the wrench turtle.
  3. I already found a way around the issue but the issue still exists. I just wanted to let him know it was broken.
  4. I'm experiencing an issue with Energy Tesseracts in MC 1.5.2 using the latest version of RIM when they're moved with your mod. They get moved correctly and they still work as intended but "ghost" versions are left behind. Something still thinks each of the "ghost" tesseracts still exist at each location the moved tesseract visits. Every other sending tesseract in the game thinks each of the "ghost" tesseracts are their and try to send energy to them. They obviously don't exist so it doesn't send energy but the game still spends a considerable amount of time trying to send energy. Restarting the game (server) fixes all "ghost" tesseract issues. "ghost" being they exist according to the tesseract logic but the physical block does not. Other blocks can be placed in the location the "ghost" ones exist without any issues. No errors are generated in any logs at any point. The issue can be replicated as follows (Thermal expansion, chicken chunks chunkloaders and RIM need to be installed for this example): 1. Put 1 energy tesseract on send-only next to some infinite power source 2. In a different area (500 blocks +): put 1 energy tesseract on receive-only on a frame somewhere else 3. Move that tesseract several chunks in one direction 4. Move away from the frame-moved tesseract 5. Open the /chunkloaders viewer to see that the chunks the frame machine moved the tesseract through are being force loaded due to the "ghost" tesseracts 6. Disable the send-only tesseract and watch the previously force loaded chunks unload. Re-enable to see them load up again 7. Restart the game to see everything goes back to a normal working state
×
×
  • Create New...