=VG= SemlerPDX

There was another area with permissions for chat specifically that I forget about often. It's fixed now.

I am not certain I'd know what to look for, but I'm happy to make those files public for anyone to look at if they would like: BMS Server Autosave Files Feb2017

I've restarted the campaign to Day 1. I didn't change anything. If one of you wants to reactivate an AI Squadron we've disabled, that is okay (I'm thinking A-10's would be smart). I don't want to alter the base save file at this time, until we are certain of what to fix here to make it better, since you all can still "fix it on the fly" and see how your fixes play out while you fly.

Again, just let me know if you don't want to continue this overly challenging campaign and want me to restart it from Day 1 with some sort of modifications. Those notes that on Day 7 is when it gets rough makes me think on how there is a trigger to bring Carrier Vinson into the campaign on Day 7 (but in our file, we've modified it so it's present on Day 1). I wonder if this could be the issue, but it hasn't been one for the many months we've been doing it this way. Just more speculation and theory.

Yea, that's whats weird -- I didn't change anything and all of a sudden, OPFOR is OP. Maybe someone messed with the frag-o near day 1 after I launched it. I'm not sure what to change, as I had a look over the Day 1 save, and things actually look normal. Squadrons we grounded to add to the challenge are still grounded, and unless the campaign itself changed with the last update, I am at a loss for what to change to fix this. Maybe I should activate the A-10's and a few of the F-18 squadrons we grounded on the next Campaign restart... Just let me know if it becomes uplayable before that time, and I'll start it over on Day 1 with a few extra BLUFOR Squadrons active. If you want me to do this now, just tell me.

Done. Callsigns cleared and campaign restarted from last autosave.

I was wondering as much. I think the base mission save needs to be modified a bit, I'll have a look at things later today and will let you all know when I have something to swap out.

Restarted (sorry for the delay, I've been away )

banned

But that does not explain why you were on our server during the 30 Day Period in which you were banned -- only because of a server error were you able to rejoin VG PR COOP due to technical difficulties we were having with our banlist, but you did not rejoin the server using the name we had banned you with, you used subversive means to sneak back onto our server via the use of an alternate name in an obvious attempt to go unnoticed and bypass the ruling of the Administration here. How are you going to explain that? You cannot. ^ I fully agree and support this decision, as I'm sure all Admins here will once they read the facts presented by TEDF. We do not need players who do not respect the rules, and we certainly do not need players who intentionally bypass the judgement of the Admins by attempting to rejoin the server during a ban period with a different name -- be sure you understand: taking advantage of a technical error with our banlist is no excuse and you knew full well that you were not welcome here for 30 days from December 18th, which is why you used an alternate name to hide.

If we're gonna compare Apples to Oranges here, the only point I want to make is that we'd like to offer Apples AND Oranges. Some people really like Liberation -- and Insurgency is a great game mode as well. Public servers are always going to have the element of Blueberries running amok and doing things at times that have to be undone. My solution to that was always scripting. If a mission has elements that need adjustment, it should be scripted into the mission the way PITN added SOAR elements on a menu for select individuals in A2 Insurgency because Blueberries would not do good things with access to the special heavy aircraft he added to his SOAR menu. AI Squads could have a script that allows them to be dissolved if their "master" has disconnected for longer than 10 minutes, for example. Perhaps there can be another script to deactivate AO's that have been activated but are not actively being attacked by a human player for a set period of time. This is the power of Arma scripting - it's not hard to do most anything, and for the harder tasks, there are resources and communities devoted to making things like this. I'd prefer this route to shutting down a popular server and using it to clone one of our other servers. If Insurgency Tanoa is getting old, we could swap it out for the Insurgency Altis, but I'm not prepared to shut down the Liberation server because it has a few dedicated regulars as well as a small public crowd that enjoys it. Just look at the GT list of players, I recognize several names on that list. I don't want to shut down their game to duplicate one of our others. In all reality, if Savage and Poff weren't so busy lately, they'd set aside a week to upgrade this VG Master Server running everything - it's still on an Intel Haswell setup, and the latest chipset servers are the same cost per month - meaning that we could nearly double the number of servers we are currently running negating the need to remove a server such as Liberation in order to add an Insurgency Altis server - eventually, we'll be able to add another Arma 3 server if we want. But for now, I think we should continue to offer the variety that we do.

Server is back up, I modified the current save file so no progress was lost. I was able to use Mission Commander to find the problem - you were correct about the callsigns, many had been used Max number of times (255). They're reset now, should be good to go. Please report if any other issues are still present.

The BMS Server will be down this morning as I fix this. Will post up here when it's done. Thanks for the report -- including a solution for me is above and beyond. It will take me much less time now. Thank you very much.

But A3 Liberation server is twice as popular as the BMR Insurgency server is... and it sounds like the only issue is with people being able to build too much or request too many units, but it's the first time the issue has come up here in the forums. The A3 Liberation server has had a higher population count than any other Arma server here for a long time. Just sayin.

I went ahead and made a save, shut down the server, and restarted the campaign from the save. Hopefully it was just some bugs - not sure if players can mess with the global clock, particularly when there are other human players on the server. Could be that someone did try to change the game speed but because you were in flight, all that happened was a small blip on your screen before it forced itself back to 1X -- pure speculation on my part, but not much else I can do. Thanks for the report!

Just tried to restart Mumble again - hoping that worked...

Throwing this up here so this thread will be about the fixing of the server after this new patch, and so Admins can refer to it here. I've emailed Poff, and Melon, TEDF have been messaged as well regarding these issues. We appreciate patience while this is worked out. Thanks!

banned.

Okay - it's all my fault. I realize that now. It wasn't intentional, I literally thought the PR Update was a TEDF/Melon thing and it's a Poffadder thing. I should have emailed him the day I first saw one of you post about it. I deserve any rotten tomatoes thrown at me from you lot. Sorry about that. (TLDNR; I emailed Poff, waiting for reply)

Roger that. Restarted to Day 1.

Is this even playable anymore? I saw Cobalt on just now while checking the server, clock was frozen... shortly after committing (I assume) Cobalt left... then the clock started up again. If it's still a fight, I'm more than happy to leave it be - if you all think it should be called a "loss", I'm happy to restart it. Just let me know.