Minecraft Username: Imabankthing Brief Description: Magic axe does not work on chorus in replant or tree feller mode. I have since tested in main and it’s works as it should. Instructions: 1. Activate replant/tree teller with magic axe 2. Attempt to chop chorus 3. Nothing happens How many times did you recreate this? 5 Result: Nothing, unable to farm in these modes.
Have you tested this on Main @Imabankthing If not please do so and let us know if it's a problem only with MainNorth. @ClarinetPhoenix please test as well, may be easier for you.
@ClarinetPhoenix please test this. There is no difference between Main and MainNorth code wise. There is no way this should ever be happening.
I'm going to boil it down to something on your end perhaps. Who knows lol. If it happens again let us know.
It’s just started happening again on MN only. Let me farm for a good 5 minutes and then back to not working. Main still fine though
Found a potential cause. Our developer will have a look at fixing this soon and I'll tag you once we push it to the live servers.
@Imabankthing Please let me know if this is still happening. Test both Main and MainNorth. As well continue your normal farming on MainNorth and let me know if after a while (15 or so minutes) it happens.
So I managed to farm for half an hour in main without issue. Will test main north again today. Thanks again for looking into it. On main north I can farm for 5 minutes at most before the issue arises again.
Thanks for the information and communication in game. We are getting closer to the cause of this. Will continue investigating. This is something to do with world height. You are significantly higher in the MainNorth server than on Main.
Should be fixed, however if it's not, we will now get far more information from the logs once it breaks. Please continue to farm on MainNorth at those high Y levels and let us know how it goes. @Imabankthing
I’ve just had this happen again on main while farming at y58. I’m glitched again and can’t farm. Seems it was lag, but it behaved the exact same way as yesterday in MN.
This one was unrelated, it was a player abusing a crash/lag exploit which we already fixed. Checked against your time stamps and they corelate. The crash/lag exploit happened 4 minutes prior to your forum post. Should be completely fine and fixed now.
