idk, but but but, he made this and it worked before. So, this bug came recentlyI'm by no means an expert, or even considered mediocre at AE2, but is it possible that there's not enough channels for a q-link?
I don't think it would be that... If he placed the block in the spot twice and it didn't crash first, it could have been related to how long it was placed and how the quantum link chamber is chunkloaded etc. It could also be on a chunk border, messing it up. Also, I wouldn't think they would enable the break block to prevent a crash feature. Isn't that still in development?Wtf? Could be the new Forge "break block if it's going to crash" thing tho
i can put the vid he made it too if you likeI don't think it would be that... If he placed the block in the spot twice and it didn't crash first, it could have been related to how long it was placed and how the quantum link chamber is chunkloaded etc. It could also be on a chunk border, messing it up. Also, I wouldn't think they would enable the break block to prevent a crash feature. Isn't that still in development?
I don't think it would be that... If he placed the block in the spot twice and it didn't crash first, it could have been related to how long it was placed and how the quantum link chamber is chunkloaded etc. It could also be on a chunk border, messing it up. Also, I wouldn't think they would enable the break block to prevent a crash feature. Isn't that still in development?
What do you mean by forge thinks it crashing.?It's not actually crashing, forge just thinks it's is...
Not chunk borders, blocks pop off directly above ones that are fine, chunks don't separate vertically
Yes it is in development(probably why it's messing up) but could've been activated by mistake...
What do you mean by forge thinks it crashing.?
That is true, chunks don't load vertically... I thought of that because some issues with crashing are because of chunk borders.
If the feature was activated by accident, you would think they would realize it and push an update to disable it...
OhIt is a config setting, no need to push an update for that
What do you mean by forge thinks it crashing.?
That is true, chunks don't load vertically... I thought of that because some issues with crashing are because of chunk borders.
If the feature was activated by accident, you would think they would realize it and push an update to disable it...
But how come sometimes it pops off and sometimes, at the same spot and same block, it doesn't pop off?Forge thinks that particular block is going to crash the game(who knows if it actually will, in this case it's unlikely) and pops it off. However it's still in development so probably overreacts.
Maybe they activated the config for whatever reason, is not my server so just guessing here....
But how come sometimes it pops off and sometimes, at the same spot and same block, it doesn't pop off?
Oh, yeah. That makes senseCos it's under development and doesn't know what it's doing yet... It may not even be the issue but it's the only one I can think of.