We are aware of this issue, Host the game as a LAN server and it will not be one.

Oprindeligt skrevet af Meerkat:

We are aware of this issue, Host the game as a LAN server and it will not be one.

Just like the original Antistasi mission, this one can't be open in a self-hosted server because of a known bug by the A3 community with some specific missions. Resuming: When you hit the "host" button, the game freezes.

One question, if I do host the LAN server, when and if the issue is fixed again, il I be able to use the same save when I come back to SP and vice versa?

Oprindeligt skrevet af Raf's:

One question, if I do host the LAN server, when and if the issue is fixed again, il I be able to use the same save when I come back to SP and vice versa?

usually but there are cases where ur save gets corrupted with the update transfer .... but i would say perosnal experiences with this map over the last 2 years is that 9/10 times it carries

You absolutely can self host Antistasi. I do it for every run of testing I do. I have never had issues with it, other than those I create.

Your singleplayer save and MP hosted save share the same file. thus you will be able to continue from where you left off swapping between. We do recommend always using LAN host instead of singleplayer as the mission has several issues when run in the SP environment due to different ways in which the game runs.

Oprindeligt skrevet af Meerkat:

You absolutely can self host Antistasi. I do it for every run of testing I do. I have never had issues with it, other than those I create.

Your singleplayer save and MP hosted save share the same file. thus you will be able to continue from where you left off swapping between. We do recommend always using LAN host instead of singleplayer as the mission has several issues when run in the SP environment due to different ways in which the game runs.

Aye, but the issue of doing that is just the fact that the commander role cannot use medikit/toolkit/eod items, and the fact that theres 2 seperate pool of cash.

A minor issue, truly, but its these small annoying things that can bother you the most.

I'm not sure if this changed along with the SP commander bug, but in MP you don't need to pick the top role to be a commander, unlike with Liberation. We always played medic + engineer in 2-player hosted. You can also give everyone the medic/engineer/etc traits with the debug console (see setUnitTrait).

Separate cash pools are a bit of a pain, although not a blocking issue as long as you don't care about the ranks.

"We do recommend always using LAN host instead of singleplayer as the mission has several issues when run in the SP environment due to different ways in which the game runs."

Sounds like an excuse not to fix bugs. But that's just me.
Up until now I've never ran into anything that ruined the gameplay and I never host with LAN.
This update made it unplayable in SP due to the membership arsenal access feature.

Most people play Antistasi in SP anyway, so the best course is to revert or make an option in Game Options to disable the member feature.

I assure you that it is NOT an excuse to not fix the bugs, merely advice to allow you to play until we can release a fix.
As soon as this issue was reported we started looking into the cause and finding solutions to it. One such solution has been picked and now just needs one short run of testing to make sure it transferred in the Github Repo correctly before we release it.

I, on behalf of the Official Antistasi Community Dev Team, sincerely apologise for the inconvenience caused by this bug.

To give a little insight into how this occurred, There was a clause in one of the main Initialisation scripts that, when it was loaded in SP, told the other scripts that membership was to be disabled. During a major rewrite of said initialisation script this line was lost, thus causing the issue.

This also highlighted a problem in our own testing cycle as we were assuming that if it worked in MP it would also work in SP with no further issues. This is due, in part, to the way we have to install the unpacked mission. As said installation method does not allow us to load it into SP, only hosted MP.