82ndAB_Bravo17

If you select build first, and then approach the plot pole, then it works.
 
And no issues building after a server restart.

Can confirm that it works for me.

If you mean a vanilla epoch.altis.pbo then that would be in the distribution zip file, if you mean a blank database that the server will start afresh from then you can either rename the current dump.rdb file (Redis will create a new file next time it starts up) or just  change the number on the DB = line in EpochServer.ini. Stop both the server and redis before doing either option.
The first way is probably preferable since it will lead to less memory usage.

You need to replace the old epoch.altis file with the new one, along with the client files and the pbo files in @epochhive\addons, the battleye .txt files and update any changes in the epochconfig.hpp file.
That error most likely means that you have missed a file or two, look in the .rpt file and see what the error is.
 

From the screenshot it looks like the radiation effect, you have probably spend too much time near a radiation source.
Check your radiation level on the debug monitor.

You don't need mods in both the -servermod and -mod sections of the command line.
Mods that are needed by both the client and the server go in the -mod section. All clients that join will need these mods, and it is these mods that show up in the server browser as being needed to join.
Mods that are only needed by the server go in the -servermod section. Clients do not need these mods in order to join the server. You can also put optional mods in this section if the server needs to have them as well - clients will not need them to be able to join, but will be able to use them if they have them loaded.

You don't need mods in both the -servermod and -mod sections of the command line.
Mods that are needed by both the client and the server go in the -mod section. All clients that join will need these mods, and it is these mods that show up in the server browser as being needed to join.
Mods that are only needed by the server go in the -servermod section. Clients do not need these mods in order to join the server. You can also put optional mods in this section if the server needs to have them as well - clients will not need them to be able to join, but will be able to use them if they have them loaded.

It should work - did you change the port in both the battleye config file (the active one) and the BEC config?

Its actually in sitrep 205
https://dev.arma3.com/post/sitrep-00205
 
Good job!

Its actually in sitrep 205
https://dev.arma3.com/post/sitrep-00205
 
Good job!

Its actually in sitrep 205
https://dev.arma3.com/post/sitrep-00205
 
Good job!

Its actually in sitrep 205
https://dev.arma3.com/post/sitrep-00205
 
Good job!

As far as I know we don't have a custom InventoryOpened handler - it would only be if it is in one of the addons that we use - SEM 0.8.3, A3EAI and Blackeagles Missions.
If we did have one I would expect to get more errors than just those 3, and we don't seem to be doing so.
 
 

Having been able to follow along with the Devs private Discord I have been able to get an idea of just how much time and effort has been put into this latest release, especially in the last few weeks leading up to the release.
And they are still at it, tweaking settings and so on with the feedback that has come since the release.
So, as the title says THANK YOU for all your hard work.

I've noticed an issue with scope sights placed in the fav bar.
If you have a scope already fitted to the weapon and don't have enough space in your kit to store the scope then when selecting a different scope from the fav bar it gets attached to the weapon, you get a message that there wasn't enough space, and the previously attached scope vanishes into thin air.
Is there a setting that would stop this from happening?
 

Having been able to follow along with the Devs private Discord I have been able to get an idea of just how much time and effort has been put into this latest release, especially in the last few weeks leading up to the release.
And they are still at it, tweaking settings and so on with the feedback that has come since the release.
So, as the title says THANK YOU for all your hard work.

Having been able to follow along with the Devs private Discord I have been able to get an idea of just how much time and effort has been put into this latest release, especially in the last few weeks leading up to the release.
And they are still at it, tweaking settings and so on with the feedback that has come since the release.
So, as the title says THANK YOU for all your hard work.

Having been able to follow along with the Devs private Discord I have been able to get an idea of just how much time and effort has been put into this latest release, especially in the last few weeks leading up to the release.
And they are still at it, tweaking settings and so on with the feedback that has come since the release.
So, as the title says THANK YOU for all your hard work.

Having been able to follow along with the Devs private Discord I have been able to get an idea of just how much time and effort has been put into this latest release, especially in the last few weeks leading up to the release.
And they are still at it, tweaking settings and so on with the feedback that has come since the release.
So, as the title says THANK YOU for all your hard work.

Having been able to follow along with the Devs private Discord I have been able to get an idea of just how much time and effort has been put into this latest release, especially in the last few weeks leading up to the release.
And they are still at it, tweaking settings and so on with the feedback that has come since the release.
So, as the title says THANK YOU for all your hard work.

Having been able to follow along with the Devs private Discord I have been able to get an idea of just how much time and effort has been put into this latest release, especially in the last few weeks leading up to the release.
And they are still at it, tweaking settings and so on with the feedback that has come since the release.
So, as the title says THANK YOU for all your hard work.

With that option set it does indeed drop it on the floor, but gives no warning that it has done so.
Pull request added with fix suggestion for both situations.

With that option set it does indeed drop it on the floor, but gives no warning that it has done so.
Pull request added with fix suggestion for both situations.

Working correctly now in latest experimental.

Thanks!
 
Not sure what happened to the line numbers, should have been 213 -216!
Since it is set unconditionally to false in line 219