Hey @BiJay
Unfortunately it has been put on hold for a while as our team is focusing on bugfixing and new content (which you can check out in our recent Testlive patch notes).
Hey @BiJay
Unfortunately it has been put on hold for a while as our team is focusing on bugfixing and new content (which you can check out in our recent Testlive patch notes).
Hey there,
Thanks for all the info, sending it to our team so they can look into it
Hey @UnknowmMantra
This is intended. When choosing the shield, you opt out of hyper armor. That being said, we might look into more changes in the future.
Thanks for your feedback.
Hey @Milky
There’s some changes coming on how lava applies damage to players and NPCs, although it’s not on this Testlive build.
Thanks for your feedback.
It’s not in the code.
They’re watching us.
Shhh
Hey @OmegaGeneral
You mention this happening in a private server. Are there any mods installed?
Thanks for your feedback and welcome to our community
Hey @Ethernet
Thanks a lot for the detailed feedback. We’ve fixed some typos in our current Testlive build, but we’re sending your list to our #spellchekker team to keep improving.
Hey @Lagertha
Any parts of your building that are in locations that are now protected on Testlive will disappear once the patch goes live. We’d recommend preparing accordingly.
Thanks for your feedback and apologies for the frustration.
Hey @UnknowmMantra
Agility won’t do much if you’re wearing heavy armor and that’s by design. That being said, there’s further changes coming to heavy armor balance down the line.
Thanks for your feedback.
On Testlive there’s the part that could affect normal constructions, which is fence foundations in a cross.
Here are some screenshots that showcase what we mean by cross formation (excuse my fantastic Paint skills):
For what matters, this other formation will not be possible since it relies on the same socket. To the best of our knowledge, this placement rule is also on Testlive:
Thanks for bringing this up @Narelle. Small sample or not, it’s an interesting observation that shouldn’t take too much to give it a look and see if there’s something amiss. Forwarded it to the devs.
Hey everybody,
We have updated the original announcement with some important information and clarification. Please give us a few moments of your time and read it fully here:
Hey there,
We have updated the original announcement with some important information and clarification.
Hey everybody,
We have updated the original announcement with some important information and clarification. Please give us a few moments of your time and read it fully here:
Hey everybody,
We have updated the original announcement with some important information and clarification. Please give us a few moments of your time and read it fully here:
We’ve updated our original announcement and also opened a thread to direct all your feedback about your issue here:
Hey everybody,
Please take a moment to read the updated announcement about this upcoming fix:
Hey everybody,
We understand the frustrating situation and how the planned measures might take too long for some of you to take effect. For that reason, we’ve decided to take your suggestion into account and disable decay in server 1932 until the planned upgrades are finally installed into the server’s hardware and software.
This is an exceptional measure and we’ve spent the past few days debating it, but due to the amount of evidence we have and the time that has already passed without providing a satisfactory solution we deemed it necessary to make this situation a little more bearable for the legit players of server 1932.
This change is in effect as of the time of this message, and it will be reverted once we have a better solution in place.
Thanks for your patience.
Hey @Aragoniska
We’ve fixed it on Testlive. You can check the notes on that section where we’ve moved your report from.
Please post your feedback in the appropiate subforum