Why is this a problem?

In T160204#2224641, @BIS_fnc_KK wrote:

Why is this a problem?

I think it would ease the mental strain when developing a multiplayer mission if you could just keep joining ingame quickly when developing. Currently you have to restart your game/client every time you want to make the game to refresh/flush the edited mission file so that the server doesn't kick you off because of the error above when you attempt to join ingame after editing the mission files.

Do you exit the server all the way to the main screen before shutting down the server or just close server exe? Also why not create bat file which will launch both server and client, adding a line that will shut any if still running prior to relaunching?

I've just closed server exe, as I didn't think about that it could make a difference. When it comes to the bat file, my main motivation was to shorten the iteration cycle for editing multiplayer missions so having to close and restart the client kind of is the actual issue. When you have e.g. Tanoa as map, it takes a moment for the game to fire up even with the game on an ultra fast SSD drive.

In T160204#2224716, @Ezcoo wrote:

I've just closed server exe, as I didn't think about that it could make a difference. When it comes to the bat file, my main motivation was to shorten the iteration cycle for editing multiplayer missions so having to close and restart the client kind of is the actual issue. When you have e.g. Tanoa as map, it takes a moment for the game to fire up even with the game on an ultra fast SSD drive.

You shouldn't have those issues, if you pack the mission file as a PBO which can be atuomated via a bat script easily.
If the issue still remains, maybe modify your bat to rename your mission with a _1 or _2 at the end and use the server.cfg to cycle through them respectively

This ^^^ I forgot how I did it years ago, exactly that packing pbo then launching server, takes seconds

Would either of you happen to have an example batch file for the PBO packing?

:: path to pbo manager
set PBOManager=C:\Program Files\PBO Manager v.1.4 beta


:: replace paths with souce and target paths respectively
"%PBOManager%\PBOConsole.exe" -pack "C:\Source\Directory" "C:\Target\Directory\file.pbo"

I hope this helps you build something to your needs :)

Thanks @blackfisch!! :)

It gives me this error message now:

Flushing file C:\Users\Net_2\AppData\Local\Arma 3\MPMissionsCache\revolution.tanoa.pbo not possible - still open

I modified the batch file a bit. Here are the contents of it:

del "D:\Steam\steamapps\common\Arma 3 Server\mpmissions\revolution.tanoa.pbo"

:: path to pbo manager
set PBOManager=C:\Program Files\PBO Manager v.1.4 beta


:: replace paths with souce and target paths respectively
"%PBOManager%\PBOConsole.exe" -pack "C:\Users\Net_2\Documents\RevolutionRPG_Arma3" "D:\Steam\steamapps\common\Arma 3 Server\mpmissions\revolution.tanoa.pbo"

What do?

Nevermind. I had filePatching disabled on my client for some reason even though I enabled it last night while testing these things. Arma... Or maybe an user based error :P