Ignasis

Hey @Narelle

Thanks for the heads-up. This seems to be an intended change that was pending QA confirmation. We’re waiting for full confirmation and if granted we’ll retroactively add it to the release changelog.

Alright people, let’s take it down a notch or two. This whole situation has brought unneeded confrontation between us all. So let’s take it step by step.
For now, the topic that started this thread. It’s been addressed in the newest Testlive build, which also has a few extra fixes.
You can give a look and its changelog, on this link:

Hey there,

By the looks of it, this might look like foul play. Please report any infractions following the guidelines here:

Moving this to its appropriate section.

We’ve added the status about this in our latest build changelog, as a known issue:

Hey there,

Unfortunately there’s been no developments since our last update, as the team is now focusing on stabilizing the current Testlive build. Once that build is ready, they’ll be able to tackle new tasks. We’ll try to inform about any new developments then. If we don’t do so, please feel free to poke again to check on the status next week.

Hey @Moirior

Thanks for the heads-up. We’ve received similar reports about this on Testlive. We’ll send note to the team so they can look (not so directly) into it.

Hey there,

Balance changes to this effect have been reverted in the newest Testlive version until we evaluate better ways to balance it:

Hey there,

We fixed this issue, or a similar related one, in our latest Testlive version.

There’s no way to check it as far as I’m aware.

BattlEye shouldn’t...

Quick update:
This has now been fixed in the latest Testlive hotfix:

Hey @Kadeka

We’re aware of this issue. It can happen if the game runs above 60fps. It is being looked into, but as a workaround we’d recommend capping the framerate to 60 until a fix for this problem is released.
Apologies for the frustration and thanks for the feedback.

Hey there,

This issue has been fixed in the current iteration of our Testlive update.
Thanks for the feedback.

Let’s stop derailing the topic even more. Whoever was trolling has received their suspension already. They already got more attention than they deserve.
Please. Let’s focus on the feedback about the patch.

Thanks for the confirmation and the video. We’ve sent it to the team.

Thanks for the information, @fito
Anyone affected with this issue can confirm this addresses the problem?

We’ve made sure to have the IP change be functional on our end, but it may take a bit of time for that to propagate.

We’ll proceed to close the thread. Not because of the feedback or criticism. It has been heard loud and clear, and we have been working to address it in a future update.
But this situation seems to have been allowing unnecessary confrontation between you guys that is not okay.
Please, do read our community guidelines, and be excellent to each other.

Hey there,

We’re aware of this. It seems there’s been a change in the BattlEye master server IP in the last 24h.
We’re looking into how to resolve this issue.
Apologies for the frustration and thanks for the feedback.

Hey @Bevalier

Thanks for the provided feedback. It’s been sent to the team so they can look into it.

Hey @Bevalier

Thanks for the heads-up. We’re aware of this fight still presenting some issues. We’ll send note again to the team to revise it and fix any remaining problems, along with the Abyssal Remnant.