search

ReikaKalseki / Reika_Mods_Issues

The issue tracker for all of my mods - RotaryCraft, its addons, ChromatiCraft, and everything else.
46 stars 14 forks source link

Pylons don't always shut down when broken. #4

Closed madolinn closed 9 years ago

madolinn commented 9 years ago

Removing blocks from a pylon structure should cause it to shutdown. Occasionally pylons don't abide by these rules and stay powered forever.

Figure 1: Pylon has Rune removed and a Structural Block Figure 2: Caused some more damage. Removed Stabilizer and more runes.

As you can see from Figure 2, even after the events of Figure 1 I was still killed from the pylon.

ReikaKalseki commented 9 years ago

Is it only when breaking runes?

madolinn commented 9 years ago

Oh, picture ALT text doesn't show.

No that pylon is completely immune to shutting down. I can remove every single block and it will last forever. Removed Stabilizers, more runes, some random structural elements. It remains active.

This happens quite often as well. On my previous world about 1 in 4 would stay alive which made gathering our first few rune sets difficult (since we opted to not craft them).

ReikaKalseki commented 9 years ago

Is it tied to specific pylons or colors? Does restarting fix it?

madolinn commented 9 years ago

Since the time of posting I've been flying around breaking them trying various things. It seems to be an issue with pylons that generate on uneven grounds so that their base is extended downwards. Immortality Restarting does not remedy it. Something also to note is that the previous pylon I completely destroyed, which was supposed to be immortal, did end up dying after removing nearly every block. The only difference is from these two, is the pseudo-immortal one was generated "broken" from a world gen ravine going through it, however it was still actively shooting things.

madolinn commented 9 years ago

Artificially extending the base downwards on pylons causes them to be unable to reactivate. Removing the placed blocks allows them to reactive. Safe to say this is the issue.

ReikaKalseki commented 9 years ago

I have an idea.

ReikaKalseki commented 9 years ago

This is probably fixed.